From: Rafal Kurcz <pawlaczus@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to use etags-select
Date: Sat, 01 Sep 2007 05:05:21 -0700 [thread overview]
Message-ID: <1188648321.765941.18960@y42g2000hsy.googlegroups.com> (raw)
In-Reply-To: <1185561317.788809@sj-nntpcache-2.cisco.com>
On 27 Lip, 20:35, Scott Frazer <scfra...@cisco.com> wrote:
> Rafal Kurcz wrote:
> > Now the numbering of tags is very, very useful. Below are my
> > conclusions about using etags-select:
> > 1. It is very nice that it takes advantage of searchable mini buffer -
> > especially in case of the long list of tags.
>
> Yes
>
> > 2. How to force etags-select to be case-sensitive.
> > I've setup (setq tags-case-fold-search nil) and it works for M-. but
> > unfortunately it does not work in etags-select.
> > It is very important when browsing C/C++ code.
>
> Fixed, see EmacsWiki.
>
>
>
> > 3. It would be very nice to show more information in the list of tags.
> > For example VIM uses the following format to show the list of tags
> > generated by "exuberent-ctags -R":
>
> > # pri kind tag file
> > 1 FSC m speed class.cpp
> > struct:Plane
> > int speed;
> > 2 FSC f speed class.cpp
> > class:Car
> > void speed () {return;}
> > 3 F C f speed class.cpp
> > struct:Bike
> > int speed () {return 10;}
> > 4 F C f speed class.cpp
> > char speed (char c) {return c;}
> > Choice number (<Enter> cancels):
>
> [snip]
>
> > I can see that it works partially for TAGS generated by etags from
> > emacs but does not work for TAGS generated by "exuberent-ctags -e -R".
> > I guess that for the sake of convinience it is better to have each tag
> > description in a single line.
>
> I can't really do much about this, I can only work with what etags and
> exuberant-ctags generates. etags adds namespace information for c++ code,
> which I show as part of the tag name. exuberant-ctags just puts in the
> unqualified tag. You can add the 'extra' option:
>
> ctags --extra=q -e -R
>
> which will include the namespace info, but it keeps the original tag also;
> i.e. you get double entries for most tags, both pointing to the same line
> of code. If it really bugs you, it would be pretty easy to post-process
> the TAGS file and remove the duplicates (left as an exercise for the
> student).
>
> Scott
Great thanks for help Scott.
Sorry for bothering you again but I think I found another weak point
of etags-select.
I started using it with the linux kernel's latest source tree.
I generated the TAGS file:
exuberant-ctags -R -e
The size of TAGS file is 54 MB.
Locating the tag with:
etags-select-find-tag-at-point
takes about 10s on Pentium 4 2.4 GHz.
It takes about 15s when loading the TAGS table for the first time.
Using the M-. takes about 0.5 s that is quite acceptable
I did the test with Vim.
I generated the tags table with:
exuberant-ctags -R
The size of tags file is 74 MB (37% larger than emacs TAGS table).
Vim is extremely fast when locating all the tags and showing the
choice list.
It takes much less than 0.5s.
Do you have any idea why etags-select works so slowly ?
Thank You for help.
next prev parent reply other threads:[~2007-09-01 12:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 9:57 How to use etags-select Rafal Kurcz
2007-07-23 13:23 ` Scott Frazer
2007-07-24 8:17 ` Rafal Kurcz
2007-07-24 16:55 ` Scott Frazer
2007-07-27 15:32 ` Rafal Kurcz
2007-07-27 18:35 ` Scott Frazer
2007-09-01 12:05 ` Rafal Kurcz [this message]
2007-09-04 13:31 ` Scott Frazer
2007-09-04 15:56 ` Scott Frazer
2007-09-04 16:16 ` Richard G Riley
2007-09-05 8:27 ` Rafal Kurcz
2007-09-08 16:41 ` Rafal Kurcz
2007-09-09 12:01 ` Rafal Kurcz
2007-09-10 14:33 ` Scott Frazer
2007-09-15 10:03 ` Rafal Kurcz
2007-09-18 13:08 ` Scott Frazer
2007-09-19 15:22 ` Rafal Kurcz
2007-09-25 15:41 ` Scott Frazer
2007-09-25 16:04 ` Gordon Beaton
2007-09-25 18:04 ` Scott Frazer
2007-09-25 23:36 ` Scott Frazer
2007-09-04 19:34 ` Vagn Johansen
2007-09-04 19:55 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1188648321.765941.18960@y42g2000hsy.googlegroups.com \
--to=pawlaczus@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).