Re: Awareness of python import semantics for [i, etc.?

2006-07-21 Thread Benji Fisher
On Thu, Jul 20, 2006 at 11:07:48AM -0700, John Reese wrote: Actually, you can't actually tell that from the import line. blag could also be a package (i.e. directory) containing a module Bok, defined in a file called Bok.py. That's what I had in mind. The following is an example of the

Re: Awareness of python import semantics for [i, etc.?

2006-07-19 Thread John Reese
On 7/13/06, Gary Johnson [EMAIL PROTECTED] wrote: A lot of this is already incorporated into the $VIMRUNTIME/ftplugin/python.vim plugin. For example, gf works fine with Python import statements. Actually, that's my point. gf does _not_ work for Python imports that have a from clause. The

Re: Awareness of python import semantics for [i, etc.?

2006-07-19 Thread Gary Johnson
On 2006-07-19, John Reese [EMAIL PROTECTED] wrote: On 7/13/06, Gary Johnson [EMAIL PROTECTED] wrote: A lot of this is already incorporated into the $VIMRUNTIME/ftplugin/python.vim plugin. For example, gf works fine with Python import statements. Actually, that's my point. gf does _not_

Re: Awareness of python import semantics for [i, etc.?

2006-07-13 Thread Benji Fisher
On Wed, Jul 12, 2006 at 03:48:22PM -0700, John Reese wrote: So there's this handy [i command that, when filetype=c, displays the first line mentioning the identifier under the cursor, which will often be its definition. The especially handy thing about it is that it knows about #include lines

Re: Awareness of python import semantics for [i, etc.?

2006-07-13 Thread Gary Johnson
On 2006-07-13, Benji Fisher [EMAIL PROTECTED] wrote: On Wed, Jul 12, 2006 at 03:48:22PM -0700, John Reese wrote: So there's this handy [i command that, when filetype=c, displays the first line mentioning the identifier under the cursor, which will often be its definition. The especially