From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Another dumb elisp query ?? -- SOLVED
Date: Sun, 29 Apr 2007 22:40:15 +0300 [thread overview]
Message-ID: <uejm3vujk.fsf@gnu.org> (raw)
In-Reply-To: <1177865132.3152.123.camel@CASE> (message from William Case on Sun, 29 Apr 2007 12:45:31 -0400)
> From: William Case <billlinux@rogers.com>
> Date: Sun, 29 Apr 2007 12:45:31 -0400
>
> > I do have '/usr/share/emacs/21.4/lisp/emacs-lisp/' and
> > '/usr/share/emacs/21.4/lisp/' that contain my *.el (text) files. Would
> > it be normal practice to compile TAGS files in those two directories?
> >
> Once I was shown by a friend that etags is a system command, or at least
> a command executed by the system, the question of TAGS placement became
> clear. I didn't matter; probably everyone has their emacs and lisp TAGS
> in a different place. I ended up putting it in a personal general emacs
> folder I use for practice and/or testing.
It indeed doesn't matter, since the command visit-tags-table asks you
for the directory in which to look for TAGS. If the file names in
TAGS are absolute, Emacs will find them no matter where you keep TAGS.
prev parent reply other threads:[~2007-04-29 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 18:15 Another dumb elisp query ?? William Case
2007-04-29 16:45 ` Another dumb elisp query ?? -- SOLVED William Case
2007-04-29 19:40 ` Eli Zaretskii [this message]
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=uejm3vujk.fsf@gnu.org \
--to=eliz@gnu.org \
--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).