Hi,
I just noticed that running ctags-exuberant with the option
'--python-kinds=-i' improves the usefulness of the vi tag file for me a lot.
You can set this as the default for ctags in your home directory
($HOME/.ctags) but maybe it's a good idea to control this in the recipe.
Christian
--
On Fri, May 28, 2010 at 10:31:46AM +0300, Christian Theune wrote:
Hi,
I just noticed that running ctags-exuberant with the option
'--python-kinds=-i' improves the usefulness of the vi tag file for me a lot.
By more useful, do you mean that the results for a e.g. method
completion are more
On 05/28/2010 11:22 AM, Roman Joost wrote:
On Fri, May 28, 2010 at 10:31:46AM +0300, Christian Theune wrote:
Hi,
I just noticed that running ctags-exuberant with the option
'--python-kinds=-i' improves the usefulness of the vi tag file for me a lot.
By more useful, do you mean that the
Summary of messages to the zope-tests list.
Period Thu May 27 12:00:00 2010 UTC to Fri May 28 12:00:00 2010 UTC.
There were 19 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from ct
at gocept.com.
Test failures
-
Subject: FAILED: Repository policy check found errors in
On Fri, May 28, 2010 at 10:31:46AM +0300, Christian Theune wrote:
Hi,
I just noticed that running ctags-exuberant with the option
'--python-kinds=-i' improves the usefulness of the vi tag file for me a lot.
You can set this as the default for ctags in your home directory
($HOME/.ctags)
Good morning,
On 05/27/2010 03:30 PM, Christian Theune wrote:
Hi,
On 05/26/2010 08:55 AM, Christian Theune wrote:
Hi,
if you would like to participate in the next bug day, please go ahead
and add yourself to the Doodle so we can get the best availability.
Here's the link:
