From: Andreas Schwab <schwab@suse.de>
Cc: pot@gnu.org, eliz@is.elta.co.il, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: etags for C++
Date: Fri, 22 Feb 2002 16:31:38 +0100 [thread overview]
Message-ID: <jezo21zg6d.fsf@sykes.suse.de> (raw)
In-Reply-To: <20020222.065341.107713552.Takaaki.Ota@am.sony.com> (Tak Ota's message of "Fri, 22 Feb 2002 06:53:41 -0800 (PST)")
Tak Ota <Takaaki.Ota@am.sony.com> writes:
|> etags is OK. For practical use etags must run on all relevant source
|> files in the target project by something like this.
|>
|> find . -name "*.[chCH]" -print | etags -
|>
|> I am asking if we can provide easier way to perform above task. In
|> above syntax manipulating "*.[chCH]" to include .cc, .cpp and .cxx is
|> not trivial.
What's wrong with this:
find . \( -name "*.[chCH]" -o -name "*.cc" -o -name "*.cpp" -o -name "*.cxx" \) -print
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-22 15:31 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 [this message]
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
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
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=jezo21zg6d.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=pot@gnu.org \
--cc=rms@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 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).