From: William Case <billlinux@rogers.com>
To: EMACS List <help-gnu-emacs@gnu.org>
Subject: Re: Another dumb elisp query ?? -- SOLVED
Date: Sun, 29 Apr 2007 12:45:31 -0400 [thread overview]
Message-ID: <1177865132.3152.123.camel@CASE> (raw)
In-Reply-To: <1177697749.3152.84.camel@CASE>
On Fri, 2007-04-27 at 14:15 -0400, William Case wrote:
> Hi;
>
> In the tutorial I am using I have come to the TAGS file compilation
> part. Following the instructions in the Tutorial and the Info Manual as
> well as digesting the process has not been difficult.
>
> What I want to check is where to create the TAGS file. I know I would
> want to put a TAGS file in a directory were I am building a project in
> the future but.. where should I put the TAGS file for emacs itself. The
> Tutorial and Manual only ambiguously say: "in the appropriate directory"
> then give me suggestions for directories I and emacs don't use. Plus
> they make reference to source files which don't seem to exist
> separately. (I can download them if need be.)
>
> 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.
If someone has a better idea let me know please.
--
Regards Bill
next prev parent reply other threads:[~2007-04-29 16:45 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 ` William Case [this message]
2007-04-29 19:40 ` Another dumb elisp query ?? -- SOLVED Eli Zaretskii
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=1177865132.3152.123.camel@CASE \
--to=billlinux@rogers.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).