From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 25071@debbugs.gnu.org
Subject: bug#25071: 26.0.50; Various Forth related improvements for etags
Date: Wed, 30 Nov 2016 19:47:45 +0200 [thread overview]
Message-ID: <83vav4q2pq.fsf@gnu.org> (raw)
In-Reply-To: <m2oa0wdi1l.fsf@gmail.com> (message from Helmut Eller on Wed, 30 Nov 2016 17:55:02 +0100)
> From: Helmut Eller <eller.helmut@gmail.com>
> Cc: 25071@debbugs.gnu.org
> Date: Wed, 30 Nov 2016 17:55:02 +0100
>
> On Wed, Nov 30 2016, Eli Zaretskii wrote:
>
> >> With the patch, etags creates explicit tag names. That works better in
> >> combination with tag-exact-match-p.
> >
> > Can you explain more about this? Explicit tag names bloat the TAGS
> > files, so other languages don't use that by default, except where
> > really needed.
>
> Yes, the TAGS file becomes at most twice as big. That's a minor
> disadvantage that I'm happy to trade for even tiny improvements in
> precision.
It clearly isn't a catastrophe, if doing that is necessary. I just
want to be sure that all Forth tags need to be explicit. Is there
perhaps some reasonably easy way to make only those tags explicit
which actually use the special characters that require it?
> > Also, it sounds like you send a patch wrt emacs-25 branch; if so,
> > please rebase on master, since that is where the patch will be pushed
> > eventually. The test files are in a different place on master.
>
> The patch is against master, but I wrote the wrong filenames in the
> changelog, because I copied part of it from an old commit message.
OK, thanks.
next prev parent reply other threads:[~2016-11-30 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 11:29 bug#25071: 26.0.50; Various Forth related improvements for etags Helmut Eller
2016-11-30 15:21 ` Eli Zaretskii
2016-11-30 16:55 ` Helmut Eller
2016-11-30 17:47 ` Eli Zaretskii [this message]
2016-11-30 19:32 ` Helmut Eller
2016-12-01 16:59 ` Eli Zaretskii
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=83vav4q2pq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25071@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
/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).