From: filebat Mark <filebat.mark@gmail.com>
To: Oleksandr Gavenko <gavenko@bifit.com.ua>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Automating TAGS file usage
Date: Tue, 10 Aug 2010 22:53:59 +0800 [thread overview]
Message-ID: <AANLkTikNhGARQ3kWyOeFuYy9VmpzBOwxSmkxL=RhLns4@mail.gmail.com> (raw)
In-Reply-To: <4C611116.1000308@bifit.com.ua>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
The package of etags-table is quite handy. It automatically loads TAGS file,
which is located in the direct/indirect parent directory.
If we register crond jobs to rebuild TAGS periodically, we don't need to
worry about the feature of finding function's definition any more.
Regards,
Denny
On Tue, Aug 10, 2010 at 4:43 PM, Oleksandr Gavenko <gavenko@bifit.com.ua>wrote:
> On 10.08.2010 11:33, filebat Mark wrote:
>
>>
>> I am also extremely interested in this!
>>
>> On Tue, Aug 10, 2010 at 2:51 PM, Gary <help-gnu-emacs@garydjones.name
>> <mailto:help-gnu-emacs@garydjones.name>> wrote:
>>
>> I surely can't be the first to want to generate and visit my TAGS files
>> automagically, rather than having to go through the manual process of
>> etags *.foo or whatever, followed by visit-tags-table. Since there are
>> flyspell, flymake, and I don't know what other fly* modes, I don't see
>> why etags couldn't be run in that manner as well. Has anyone already
>> tried this?
>>
>> Read recent discussion about automatic TAGS visiting:
>
> http://article.gmane.org/gmane.emacs.help/74280
>
>
>
--
Thanks & Regards
Denny Zhang
[-- Attachment #2: Type: text/html, Size: 1981 bytes --]
next prev parent reply other threads:[~2010-08-10 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 6:51 Automating TAGS file usage Gary
2010-08-10 8:33 ` filebat Mark
2010-08-10 8:43 ` Oleksandr Gavenko
2010-08-10 14:53 ` filebat Mark [this message]
2010-08-12 9:16 ` Gary
[not found] <mailman.4.1281423114.31516.help-gnu-emacs@gnu.org>
2010-08-10 8:56 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikNhGARQ3kWyOeFuYy9VmpzBOwxSmkxL=RhLns4@mail.gmail.com' \
--to=filebat.mark@gmail.com \
--cc=gavenko@bifit.com.ua \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.