all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
Subject: Re: [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags`
Date: Tue, 02 Jan 2007 15:26:08 +0100	[thread overview]
Message-ID: <m3k6057ben.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: E1H1i1U-00014h-00@tucano.isti.cnr.it

Francesco Potorti` <pot@gnu.org> writes:

> After checking the behaviour of Exuberant ctags, I decided to follow the
> same route and allow for duplicated tags in ctags mode.  I added an
> undocumented option --no-duplicates, just for emergency, that may be
> deleted in a future release of Etags.  I also undocumented the existing
> --no-warn option.
>
> If anyone wants to comment on this change, please let me know.
>
> On a related issue, the Exuberant ctags standard for an extended Vi tags
> format is described at <http://ctags.sourceforge.net/FORMAT>, and is
> currently implemented and supported at least by Vim.  I am willing to
> implement it in Etags, when it is working in ctags mode.  Again, if
> anyone wants to comment on this, please let me know.

Why shipping an own ctags/etags implementation at all? I mean Exuberant
ctags works really well (at least in my experience as a C++ coder much
better than the Emacs etags) and it's GPL software.

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.

  reply	other threads:[~2007-01-02 14:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24 20:01 [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags` Don Mullis
2006-12-25  5:41 ` Masatake YAMATO
2006-12-25 16:47   ` Don Mullis
2006-12-25 22:36     ` Francesco Potorti`
2006-12-26 14:13 ` Francesco Potorti`
2006-12-26 18:43   ` Don Mullis
2006-12-28  0:10     ` Francesco Potorti`
2006-12-28  5:48       ` Don Mullis
2006-12-28 10:21         ` Francesco Potorti`
2006-12-29 22:58         ` Richard Stallman
2006-12-30 20:36           ` Don Mullis
2006-12-31  1:46             ` Richard Stallman
2006-12-27  2:59   ` Richard Stallman
2006-12-30 12:15     ` Francesco Potorti`
2006-12-31  1:45       ` Richard Stallman
2007-01-02 11:41         ` Francesco Potorti`
2007-01-02 14:26           ` Frank Schmitt [this message]
2007-01-03  1:24             ` Francesco Potorti`
2007-01-03 12:06               ` Frank Schmitt
2007-01-03 14:33                 ` Frank Schmitt
     [not found]               ` <m38xgk47lc.fsf@mid.gehheimdienst.de>
2007-02-05  8:25                 ` Francesco Potorti`
2007-01-02 21:24           ` Richard Stallman
2007-01-03  0:40             ` Francesco Potorti`
2007-01-02 21:24           ` Eli Zaretskii
2007-01-03  0:42             ` Francesco Potorti`

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=m3k6057ben.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    /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.