From: kiniry@acm.org (Joseph R. Kiniry)
Subject: Re: Unable to use TAGS in xemacs
Date: 8 Apr 2003 07:50:33 -0700 [thread overview]
Message-ID: <2b2e3261.0304080650.12741c8e@posting.google.com> (raw)
In-Reply-To: 877kb3vg28.fsf@tleepslib.sk.tsukuba.ac.jp
"Stephen J. Turnbull" <stephen@xemacs.org> wrote in message news:<877kb3vg28.fsf@tleepslib.sk.tsukuba.ac.jp>...
> >>>>> "Ganesan" == Ganesan Thiagarajan <gana@ti.com> writes:
>
> Ganesan> Thanks for your response. I downloaded the C-code from
> Ganesan> the web for etags and used it. Is it different from the
> Ganesan> emacs supplied one?
>
> There are perhaps four sources for etags: Exuberant ctags (I'm not
> absolutely sure they provide etags, but ISTR they do), Francisco
> Portorti's "canonical" Emacs etags, GNU Emacs (which tracks Portorti's
> version very closely), and XEmacs (which is synched to Portorti's
> version regularly, perhaps every 3 months or so). The last three are
> 99% interoperable, Exuberant ctags is a quite different file format.
A bit of clarification: exuberant ctags provides full support for all
tags-based mechanisms in (x)emacs. There are some issues with the
default settings for some customization, but it is easily tweaks. I
highly recomend exuberant ctags as it provides comprehensive support
for a vast number of languages. See the exuberant ctags FAQ for more
information on these (x)emacs-related issues:
http://ctags.sourceforge.net/faq.html
Joe Kiniry
next prev parent reply other threads:[~2003-04-08 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 14:18 Unable to use TAGS in xemacs Ganesan T
2003-03-12 16:38 ` Stephen J. Turnbull
2003-03-13 7:22 ` Ganesan Thiagarajan
2003-03-13 8:14 ` Stephen J. Turnbull
2003-04-08 14:50 ` Joseph R. Kiniry [this message]
2003-04-08 18:05 ` Shyamal Prasad
2003-04-09 9:12 ` Joseph Kiniry
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=2b2e3261.0304080650.12741c8e@posting.google.com \
--to=kiniry@acm.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.