unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: Best way to get a cross-reference listing...
Date: Wed, 23 Apr 2003 11:25:23 +0200	[thread overview]
Message-ID: <4839-Wed23Apr2003112522+0300-eliz@elta.co.il> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B2370F@penguin.adic.com> (brian.auld@adic.com)

> From: brian.auld@adic.com
> Date: Tue, 22 Apr 2003 07:38:45 -0700
> 
> Does anyone have any suggestions on (a) how to target a window with
> M-x grep-find, or an alternate way to cross-reference a code tree.

Download and install the GNU Id-utils package, and then use the 
"M-x gid" command instead.  Not only is it _much_ faster than
grep-find, but it also knows about the syntax of C (and other
programming languages, so it will never show you false hits due
to a substring that matched.  It will also automatically search
for the symbol at point as the default, and keep the results of
each search in a separate buffer, so you could consult them again
later.

As for the problem of the window that pops up in seemingly random
places, this is actually a feature, and my advice is to get used to
it: Emacs was not designed for rigid position of its windows.
However, you could make that window pop in a different frame (see
the variables `special-display-regexps' and
`special-display-buffer-names', for more about this feature).

> I find if I try to etag the entire linux kernel tree using for example:
> 
> find . -name "*.[chCH]" | xargs etags -o kernel-tags
> 
> the tags never seem to be complete.

That's wrong usage: you don't need xargs.  Try this instead:

  find . -name "*.[chCH]" | etags -o kernel-tags -

(and I'd also include *.y files in the pattern, btw).

  reply	other threads:[~2003-04-23  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 14:38 Best way to get a cross-reference listing brian.auld
2003-04-23  9:25 ` Eli Zaretskii [this message]
     [not found] <mailman.5071.1051023013.21513.help-gnu-emacs@gnu.org>
2003-04-23  6:20 ` Kai Großjohann
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 13:35 brian.auld
2003-04-23 19:53 ` Eli Zaretskii
     [not found] <mailman.5112.1051105181.21513.help-gnu-emacs@gnu.org>
2003-04-24 14:05 ` Zap Branigan
2003-04-24 20:28   ` Eli Zaretskii
     [not found]   ` <mailman.5175.1051216377.21513.help-gnu-emacs@gnu.org>
2003-04-25 17:04     ` Zap Branigan

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=4839-Wed23Apr2003112522+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    /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).