unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Van Dusen <cavandusen@gmail.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Location-aware tags?
Date: Tue, 10 Apr 2012 21:17:24 -0500	[thread overview]
Message-ID: <293790BD-7D7F-436D-B39C-F6E1897C1164@gmail.com> (raw)
In-Reply-To: <m3d37gzq3n.fsf@stories.gnus.org>

On Apr 9, 2012, at 2:01 PM, Lars Magne Ingebrigtsen wrote:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 
>> So I'm proposing to add a new variable `tags-use-auto-tags' or
>> something, that would make `M-.' always look for the nearest TAGS file
>> upwards in the directory structure, and then switch to that file before
>> looking up the symbol.
> 
> Even more super-magical would be if Emacs auto-generated the TAGS file,
> if none could be found.  That is, if you `M-.' in a directory, and no
> TAGS file can be found upwards, then it prompts you for where to
> generate the file "from", generate it to /tmp/tmpTAGS, switch to it, and
> delete the file.
> 
> That way Emacs would magically allow you to easily browse whatever
> source tree you're inspecting without you having to have any particular
> knowledge of the nitty-gritty going on behind the curtain.
> 
> (etags would be called with "find dir -type f | etags --output=/tmp/foo -"
> or something, I guess.)
> 

gtags.el included in GNU Global provides some (if not most) of this functionality.

Chris.


  reply	other threads:[~2012-04-11  2:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 16:53 Location-aware tags? Lars Magne Ingebrigtsen
2012-04-09 19:01 ` Lars Magne Ingebrigtsen
2012-04-11  2:17   ` Chris Van Dusen [this message]
2012-04-16  2:07     ` Jonathan Rockway
2012-04-09 19:46 ` Tom Tromey
2012-04-10  5:49 ` Stefan Reichör

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=293790BD-7D7F-436D-B39C-F6E1897C1164@gmail.com \
    --to=cavandusen@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).