unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
	61962@debbugs.gnu.org
Subject: bug#61962: 30.0.50; New trouble with symbols with positions
Date: Sun, 05 Mar 2023 17:04:12 +0100	[thread overview]
Message-ID: <877cvvqj5v.fsf@web.de> (raw)
In-Reply-To: <A11D3F95-1071-4698-BAFC-D7C895BF0010@acm.org> ("Mattias Engdegård"'s message of "Sat, 4 Mar 2023 22:39:03 +0100")

Mattias Engdegård <mattiase@acm.org> writes:

> That would very likely be fcf2f7aead.

When this issue is not easy to fix, maybe consider to revert that commit
for now (inexact compiler warning positions are less problematic than
breaking Elisp code).

Michael.





  parent reply	other threads:[~2023-03-05 16:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 16:18 bug#61962: 30.0.50; New trouble with symbols with positions Michael Heerdegen
2023-03-04 16:34 ` Eli Zaretskii
2023-03-04 21:39   ` Mattias Engdegård
2023-03-04 21:53     ` Michael Heerdegen
2023-03-05 16:04     ` Michael Heerdegen [this message]
2023-03-05 18:39       ` Alan Mackenzie
2023-03-05 19:41         ` Michael Heerdegen
2023-03-06 13:22           ` Alan Mackenzie
2023-03-07  0:29             ` Michael Heerdegen
2023-03-07 10:24               ` Alan Mackenzie
2023-03-07 13:13                 ` Eli Zaretskii
2023-03-07 13:51                   ` Robert Pluim
2023-03-07 15:46                     ` Alan Mackenzie
2023-03-12 17:30                       ` Mattias Engdegård
2023-03-12 20:42                         ` Alan Mackenzie
2023-03-13 14:50                           ` Eli Zaretskii
2023-03-14 12:31                           ` Mattias Engdegård
2023-03-07 15:42                   ` Alan Mackenzie
2023-03-07 15:15                 ` Michael Heerdegen
2023-03-04 16:36 ` Eli Zaretskii
2023-03-04 16:47   ` Michael Heerdegen

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=877cvvqj5v.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=61962@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=mattiase@acm.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).