ctags one more...

[Richard Dale]

In my opinion, a feature like this would not be 'built into' KDevelop 3.0, it
should be added by means of a python script creating a custom menu item or
similar. But it would be a good example to test out the scripting (the real
work would be adding any missing cabapilites to that) if you did ctags in that
way. 

This is a feature not everyone would want it - only if using a ctags
driven editor, one of these 'VIM' KParts perhaps.

As far as I know, having studied the code, it doesn't gather any more info
than the KDevelop class parser does already.

-- Richard

On Mon, 16 Apr 2001, Roland Krause wrote:
> PS: Ralf, I realize that this *should* have gone into KDevelop-3, but
> KDevelop-3 version is still unusable for actual work. If you think this
> addition is too risky w/ regard to the upcoming release of KDevelop-2
> please let me know and I will put defines around the respective code. 
> PPS: I believe this code can very easily be added to KDevelop-3 and I
> will even volunteer to do so if there is demand for it. Just let me get
> it working first. 

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«