unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45246@debbugs.gnu.org, grfz@gmx.de
Subject: bug#45246: 28.0.50; etags assertion error
Date: Thu, 09 Jun 2022 20:43:04 +0200	[thread overview]
Message-ID: <874k0tznif.fsf@gnus.org> (raw)
In-Reply-To: <83zgil20oe.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Jun 2022 20:42:41 +0300")

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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-09 18:43 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 [this message]
2022-06-09 18:59             ` Eli Zaretskii
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

  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=874k0tznif.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45246@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=grfz@gmx.de \
    /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).