From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Takaaki.Ota@am.sony.com, pot@gnu.org, emacs-devel@gnu.org
Subject: Re: etags for C++
Date: Mon, 25 Feb 2002 08:40:47 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1020225083418.5689J@is> (raw)
In-Reply-To: <200202250008.g1P08vp15648@aztec.santafe.edu>
On Sun, 24 Feb 2002, Richard Stallman wrote:
> People usually write commands in Makefile to run etags.
> I don't see that it is very useful to have Lisp programs
> to run it.
Putting on my Emacs Apostle hat, I find in my work with my colleagues
that they have difficulties in running etags. For a complex project, a
command such as this:
find /project/root -name '*.[ch]' | xargs -n 2000 etags
let alone the complications with additional file-name extensions like
.cpp etc., is typically beyond many users' knowledge. Since they don't
know what the command is, they can't put it into their Makefiles,
either. Non-Unix platforms introduce an additional complication into
this (no `find' installed etc.)
So perhaps it could be a good idea to have an Emacs command that would
accept a few inputs, like the top-level directory and whether to recurse
into its subdirectories, and will then run etags as appropriate.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-25 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 19:41 etags for C++ Tak Ota
2002-02-20 22:13 ` Richard Stallman
2002-02-21 6:47 ` Eli Zaretskii
2002-02-21 7:34 ` Tak Ota
2002-02-21 7:45 ` Tak Ota
2002-02-21 10:59 ` Eli Zaretskii
2002-02-21 16:19 ` Tak Ota
2002-02-22 14:32 ` Francesco Potorti`
2002-02-22 14:53 ` Tak Ota
2002-02-22 15:31 ` Andreas Schwab
2002-02-23 20:19 ` Richard Stallman
2002-02-24 5:42 ` Tak Ota
2002-02-25 0:08 ` Richard Stallman
2002-02-25 6:40 ` Eli Zaretskii [this message]
2002-02-25 8:27 ` Francesco Potorti`
2002-02-25 16:30 ` Tak Ota
2002-02-26 20:15 ` Richard Stallman
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=Pine.SUN.3.91.1020225083418.5689J@is \
--to=eliz@is.elta.co.il \
--cc=Takaaki.Ota@am.sony.com \
--cc=emacs-devel@gnu.org \
--cc=pot@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.