From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: etags in tex files
Date: Sun, 18 Jul 2021 09:34:09 +0300 [thread overview]
Message-ID: <83v9582kri.fsf@gnu.org> (raw)
In-Reply-To: <87y2a4r91f.fsf@yandex.com> (message from Colin Baxter on Sat, 17 Jul 2021 21:15:56 +0100)
> From: Colin Baxter <m43cap@yandex.com>
> Cc: help-gnu-emacs@gnu.org
> Cc:
> Date: Sat, 17 Jul 2021 21:15:56 +0100
>
> > Is the problem in the TAGS file, or is the problem in etags.el
> > functions that search for the tags? I think it's the latter, but
> > if so, then...
>
> >> Is there any way in which I can configure etags to recognise
> >> everything with the curly brackets of a \label?
>
> > ...which "etags" do you want to configure and how?
>
> I don't really know at this stage
Look at the produced TAGS file: does it include the problematic
labels? If it does, then etags the program is not your problem.
> but I think part of the problem lies with
>
> defun find-tag-tag (string)
>
> which seems to reserve a significant use for the colon.
How do you see its "reserving a significant use for the colon"?
> as that file's commentary puts it, "The namespacing of this package
> is a mess:". I agree.
That comment is about the naming conventions, not about the code
itself.
next prev parent reply other threads:[~2021-07-18 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 18:05 etags in tex files Colin Baxter
2021-07-17 18:33 ` Óscar Fuentes
2021-07-17 20:18 ` Colin Baxter
2021-07-18 6:35 ` Eli Zaretskii
2021-07-17 18:38 ` Eli Zaretskii
2021-07-17 20:15 ` Colin Baxter
2021-07-18 6:34 ` Eli Zaretskii [this message]
2021-07-21 14:20 ` Colin Baxter
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=83v9582kri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).