I don't know if this is relevant or not, but the IPython autocompletion
capability is awesome.
If I'm investigating code I tend to do the following.
list the modules in a package:
In [1]: from fs import <tab>
this lists the modules, in a package so I pick one
In [1]: from fs import osfs
<the osfs entry is tab-completable>
now I can check the usage of fs.osfs
In [2]: osfs? <enter>
or the source:
In [2]: osfs?? <enter>
or the contents of the module
In [2]: osfs. <tab>
I can instantiate a class:
In [3]: myfs = osfs.OSFS('/')
and examine the ivars and methods:
In [4]: myfs. <tab>
It is such an efficient way to learn and remember the details of code.
I know a bunch of work was done on Leo/IPython integration, don't
know the current status, my wish of synchronized IPython and Leo
may well be one of the many granted wishes I have forgotten about.
I certainly think IPython autocompletion is the gold standard.
Thanks,
Kent
On Thu, Sep 29, 2011 at 6:29 PM, Edward K. Ream <[email protected]> wrote:
> On Sep 29, 9:57 am, Terry Brown <[email protected]> wrote:
>
>> > Terry, please let me know if this change seems dubious to you.
>>
>> Now selecting the About docs. for multiple plugins creates multiple
>> panes, whereas before the same pane was reused. Preference kind of
>> thing, I don't think it's that big a deal, although if you were
>> browsing plugin docs the new behavior could be annoying.
>
> Interesting. There is a relationship here with mouseless
> programming. It would seem that all visual elements, especially those
> that may exist in multiple versions, must have a name or other
> description suitable for generalized commands.
>
> At present, the most serious hole in Leo's commands is that there is
> no way to close or select a tab in the qttabs gui that represents an
> entire file: afaik, you have to use the mouse to change files. By
> extension, the user might want multiple rendering panes, especially if
> one or more are locked. Without a description, there is no way to
> specify exactly what show/hide-rendering pane does.
>
> I haven't forgotten the autocompleter docs. I'll get to them next.
> It looks like autocompletion would be the way to generalize the not-
> very-effect commands that switch focus from one ui element to
> another. A related benefit is one generalized command might be more
> convenient to use than the present flavors of (buggy) cycle-focus
> commands.
>
> In short, contemplating generalized windows leads us to generalized
> select/delete/show/hide commands, based on autocompletion, that work
> on various ui elements. This looks like the next project.
>
> Edward
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/leo-editor?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
