Re: [ jEdit-devel ] feature: "BrowseToFile"

[Kenrick D. <kd...@ea...>]

Stefan,

Stefan Radig wrote:
> I downloaded the plugin and it mostly works great for me. Really good to 
> finally have this. Thanks.

Thanks for using it and thanks for the feedback.  I was starting to think that
Slava and I were the only ones using it.

> 1.) I am working in an environment with people using different editors. Thus > our make system generates tag files in the ctags and in the etags format named > tags and TAGS respectively. I am running jedit on a windows
> system. This has the funny effect that jedit cannot distinguish between those > two files and always picks the wrong one - the file names are used case > insensitive.
> It would be easy to change (or extend) the make system to rename the tags file > e.g. to "jtags" or whatsoever. Unfortunately then it won't be found be the > plugin...
> So could you please make the file name which is momentarily hardcoded > configurable?

Understandable.  This was somewhere on my todo list, but you have moved it to
the top.  I've added some UI to specify the tag filename when using the "Search
tag index file in current buffer's directory" option.  Just specify the file
name (e.g "tags" or "etags" or "jtags" or "foo" or "bar"... you get the idea).

> 2.) I configured several global tags files in the plugin's configuration > dialog. They are obviously searched because when the cursor is over htc_printf > (which is in a different directory in a file called htc_connection.c) it opens
> up a window for "htc_connection.c". Unfortunately the directory is wrong: It's > the same as the directory from which I started the search. But there is no such > file...

It sounds like the tag index file has listed the path to the defintion of
"htc_printf" as just "htc_connection.c" as opposed to
"/some/path/to/htc_connection.c".  Unfortunately the Tags plugin can only assume
that the path is correct.  Fortunately you can pass the correct path to the
ctags program when creating the tag index file.  The path you pass (or don't
pass) to the ctags program will be the path prepended to the defintion file
name.  This allows for relative paths to the defintion file name from the
directory that you are tagging from (the current file's directory).  If you want
the absolute path to the defintion file name pass $cwd or `pwd` to ctags:

   ctags [options] `pwd`
   ctags [options] $cwd

If this fails, and you see that the correct path to the defintion of the tag is
listed in the tag index file, and you can open file file from the current
buffer's directory with the supplied path, then this is a bug (please let me
know).

Hope this helps, and thanks for the feedback.  You can grap the new version
(0.7.2) either from the jedit CVS, or from:

   http://home.earthlink.net/~kdrew/Tags.jar

Let me know if you have any problems,

Ken

-- 
Ken Drew
kd...@ea...