unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Scott Frazer <frazer.scott@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to use etags-select
Date: Mon, 10 Sep 2007 10:33:12 -0400	[thread overview]
Message-ID: <1189434792.450554@sj-nntpcache-3.cisco.com> (raw)
In-Reply-To: <1189269664.714541.247600@50g2000hsm.googlegroups.com>

Rafal Kurcz wrote:
>> Now it works very fast.
>> I did the same test as above on the same machine - now I get the list
>> of tags immediately.
>> Great thanks for help Scott.
> 
> etags-select is now awesome tool. I use it a lot to navigate 2.6.22.6
> kernel source.
> I also found 2 another problems. They don't seem to be big:
> 
> 1. Place the cursor on "__free_pages_ok" function declaration (mm/
> page_alloc.c:62) and invoke
> etags-select-find-tag-at-point. It will lead You to the same tag while
> it should lead You to the definition (mm/page_alloc.c:501)

An assumption is made that any taggable items are in fact tagged, otherwise
it becomes complicated trying to sort the two out.  In this case the function
prototype (declaration) wasn't tagged, and since it looks exactly like the
function definition etags-select stops at the first matching line.  If you
invoke etags like:

etags --declarations *.c

it works.  I can't remember off the top of my head what the equivalent in
exuberant ctags is.

> 2. Place the cursor on "page_map_count(page)" function invocation (mm/
> page_alloc.c:433) and invoke etags-select-find-tag-at-point.
> It will display among others the "reset_page_mapcount" as a candidate
> to jump. I think that it is not a good candidate.
> For me it looks rather like TAGS problem since C-u M-. leads You to
> that symbol as well.
> 

Although you say in a later message that this is OK, I'm not sure it is.
I think it might be confusing two function names with the same suffix.
It should be an easy enough fix ... I need to create a test case and sort
things out.

Scott

  parent reply	other threads:[~2007-09-10 14:33 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
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 [this message]
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=1189434792.450554@sj-nntpcache-3.cisco.com \
    --to=frazer.scott@gmail.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).