Re: Aha: vim trainer mode

2014-08-09 Thread Fidel N
Sorry again, but the shortcutfoo website also asks for money when you reach certain level :( Seems like best solution right now is vim-trainer mode :D -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receivi

Re: Weird autocompleter bug

2014-08-09 Thread Edward K. Ream
On Fri, Aug 8, 2014 at 10:00 AM, Fidel N wrote: > well ill wait till "c." completes well then try to find out the difference, > but I really trust when the other thing is fixed this also will. I'll attempt a fix today. Edward -- You received this message because you are subscribed to the Googl

Re: Weird autocompleter bug

2014-08-09 Thread Edward K. Ream
On Sat, Aug 9, 2014 at 8:24 AM, Edward K. Ream wrote: > I'll attempt a fix today. I inserted a trace in AutoCompleterClass.get_leo_namespace:: def get_leo_namespace (self,prefix): ''' Return an environment in which to evaluate prefix. Add some common standard library

Re: Weird autocompleter bug

2014-08-09 Thread Edward K. Ream
On Sat, Aug 9, 2014 at 11:10 AM, Edward K. Ream wrote: Ach. I see why the git bisect was so dashed confusing. The commit that caused the problems changed *two* files, leoAtFile.py and leoImport.py. Somehow, I didn't see the change to leoImport.py, but now, from first principles, it's clear tha

Re: Weird autocompleter bug

2014-08-09 Thread Edward K. Ream
On Sat, Aug 9, 2014 at 11:19 AM, Edward K. Ream wrote: > So the mystery of my rollback of leoAtFile.py didn't solve the problem > is completely explained. Still, some care will be required. I'll fix this > later today... Fixed. Maybe. Here is the checkin log for rev 90a0531... QQQ Revert to

Re: Weird autocompleter bug

2014-08-09 Thread Fidel N
The autocompleter works normally for me now. Thanks Edward. On Sat, Aug 9, 2014 at 11:00 PM, Edward K. Ream wrote: > On Sat, Aug 9, 2014 at 11:19 AM, Edward K. Ream > wrote: > > > So the mystery of my rollback of leoAtFile.py didn't solve the problem > > is completely explained. Still, some ca