From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45246@debbugs.gnu.org, grfz@gmx.de
Subject: bug#45246: 28.0.50; etags assertion error
Date: Thu, 09 Jun 2022 21:59:55 +0300 [thread overview]
Message-ID: <83k09p1x3o.fsf@gnu.org> (raw)
In-Reply-To: <874k0tznif.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 09 Jun 2022 20:43:04 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: grfz@gmx.de, 45246@debbugs.gnu.org
> Date: Thu, 09 Jun 2022 20:43:04 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > "etags --help" says:
> >
> > -I, --ignore-indentation
> > In C and C++ do not assume that a closing brace in the first
> > column is the final brace of a function or structure definition.
> >
> > And indeed, invoking "etags -I" compiled with --enable-checking with
> > the original file avoids the assertion violation. And in a production
> > build, etags produces a valid TAGS file even if -I is omitted.
> >
> > So I think there's nothing to do here, and we should close this bug as
> > notabug. Does anyone disagree?
>
> I think that sounds correct.
Gregor, any objections to closing this bug?
next prev parent reply other threads:[~2022-06-09 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 23:38 bug#45246: 28.0.50; etags assertion error Gregor Zattler
2022-06-07 11:35 ` Lars Ingebrigtsen
2022-06-07 14:26 ` Gregor Zattler
2022-06-07 15:58 ` Eli Zaretskii
2022-06-07 16:38 ` Andreas Schwab
2022-06-07 17:15 ` Eli Zaretskii
2022-06-07 17:34 ` Andreas Schwab
2022-06-07 18:25 ` Eli Zaretskii
2022-06-07 17:08 ` Eli Zaretskii
2022-06-09 17:42 ` Eli Zaretskii
2022-06-09 18:43 ` Lars Ingebrigtsen
2022-06-09 18:59 ` Eli Zaretskii [this message]
2022-06-09 22:33 ` Gregor Zattler
2022-06-10 7:25 ` Eli Zaretskii
2022-06-10 7:26 ` Eli Zaretskii
2022-06-10 14:01 ` Francesco Potortì
2022-06-07 17:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k09p1x3o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45246@debbugs.gnu.org \
--cc=grfz@gmx.de \
--cc=larsi@gnus.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.