unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 41520@debbugs.gnu.org, stefan@marxist.se, pipcet@gmail.com
Subject: bug#41520: 28.0.50; Crash in character.h due to assertion error
Date: Sun, 27 Sep 2020 19:00:44 +0300	[thread overview]
Message-ID: <837dsfnr9v.fsf@gnu.org> (raw)
In-Reply-To: <878scv1b18.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  27 Sep 2020 17:42:27 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 41520@debbugs.gnu.org,  stefan@marxist.se,  pipcet@gmail.com
> Date: Sun, 27 Sep 2020 17:42:27 +0200
> 
> There was then some followup discussion about renaming some of these
> macros, since they have names that sometimes lead to some confusion, but
> I think it's perhaps too much churn for too little gain.

Yes.  In general, I'd prefer not to rename veteran macros
unnecessarily, as they are more or less burned into the muscle memory
of those who frequently work on the Emacs internals.  Into my memory,
definitely.  These two macros are from that group.

> So I think everything is fixed here now?

Yes.





      reply	other threads:[~2020-09-27 16:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  7:05 bug#41520: 28.0.50; Crash in character.h due to assertion error Stefan Kangas
2020-05-25  7:28 ` Pip Cet
2020-05-25  7:41   ` Pip Cet
2020-05-25 14:18   ` Eli Zaretskii
2020-05-25 14:30     ` Pip Cet
2020-05-25 15:07       ` Eli Zaretskii
2020-05-25 15:16         ` Pip Cet
2020-05-25 16:09           ` Eli Zaretskii
2020-05-25 17:54             ` Pip Cet
2020-05-25 19:30               ` Eli Zaretskii
2020-05-25 20:39                 ` Pip Cet
2020-05-26 16:17                   ` Eli Zaretskii
2020-09-27 14:36         ` Lars Ingebrigtsen
2020-09-27 15:15           ` Eli Zaretskii
2020-09-27 15:42             ` Lars Ingebrigtsen
2020-09-27 16:00               ` Eli Zaretskii [this message]

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=837dsfnr9v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41520@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=pipcet@gmail.com \
    --cc=stefan@marxist.se \
    /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).