unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Glenn Morris <rgm@gnu.org>, 26181@debbugs.gnu.org
Subject: bug#26181: Remove etags
Date: Tue, 21 Mar 2017 11:03:24 +0200	[thread overview]
Message-ID: <5a534b9a-14bf-ca3f-ae04-f37c6f66d399@yandex.ru> (raw)
In-Reply-To: <hbk27koo3d.fsf@fencepost.gnu.org>

On 20.03.2017 01:15, Glenn Morris wrote:

> I've never understood why Emacs includes a tags program.
> It's not part of the normal remit of a text editor.

FWIW, it has been handy when we introduced xref and started treating the 
tags a bit more strictly.

> The situation has changed since then in that etags no longer has a
> maintainer (IIUC).

AFAIK Eli is the maintainer now. And it's handy to have for now, at 
least until Universal Ctags is widely available across distributions, 
handles all languages as well as etags does, and outputs correct entries 
WRT implicit/explicit tag names (not 100% sure there is a problem, but 
it's something that we had to fix in etags recently, at least).

Having all these conditions satisfied seems to be a .

> Having our own tags program means we can tweak it to work better for our
> own code; but conversely it would be better if our code Just Worked with
> standard (ie external) tools.

The latter might mean learning to use the ctags output (Vim format).





  parent reply	other threads:[~2017-03-21  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 23:15 bug#26181: Remove etags Glenn Morris
2017-03-20 18:39 ` Eli Zaretskii
2017-03-20 20:35   ` Andreas Politz
2017-03-21  9:03 ` Dmitry Gutov [this message]
2017-03-21 10:34   ` Francesco Potortì
2017-03-21 15:42   ` Eli Zaretskii
2017-03-21 16:45     ` Dmitry Gutov
2017-03-29  5:14 ` John Wiegley
2017-04-03 20:54 ` Glenn Morris
2017-04-04 16:20   ` Richard Stallman
2022-02-08  6:27     ` Lars Ingebrigtsen

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=5a534b9a-14bf-ca3f-ae04-f37c6f66d399@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=26181@debbugs.gnu.org \
    --cc=rgm@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).