all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug#54188: Crash when eval-ing font test elisp code
Date: Thu, 29 Aug 2024 09:02:28 +0300	[thread overview]
Message-ID: <86wmjzg93f.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4kyd+b0ugzBHJumOaYsvSAabzb-r2SUtO7XuUvNcdP_vQ@mail.gmail.com> (message from Anand Tamariya on Thu, 29 Aug 2024 10:24:56 +0530)

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Thu, 29 Aug 2024 10:24:56 +0530
> Cc: emacs-devel@gnu.org
> 
> On Wed, Aug 28, 2024 at 11:37 PM Eli Zaretskii <eliz@gnu.org> wrote:
> 
>  Thanks.  What version of Emacs is this?
> 
> This problem is not present in the latest version (tested with Emacs 29.4). To summarize, if you're facing the
> crash, do one of the following:
> - Remove the characters 180, 166 and 216.
> - Upgrade to the latest version of Emacs

OK, thanks.  This matches my experience: I couldn't reproduce with the
current release branch (which will soon become Emacs 30.1).



  parent reply	other threads:[~2024-08-29  6:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  8:47 bug#54188: Crash when eval-ing font test elisp code Anand Tamariya
2024-08-28 12:37 ` Eli Zaretskii
2024-08-28 15:04   ` Anand Tamariya
2024-08-28 15:29     ` Pip Cet
2024-08-28 15:54       ` Eli Zaretskii
2024-08-28 18:07     ` Eli Zaretskii
2024-08-29  4:54       ` Anand Tamariya
2024-08-29  5:11         ` Yuri Khan
2024-08-29  6:02         ` Eli Zaretskii [this message]
     [not found] <50f9bd97-02a4-4b0d-0eae-54e804293219.ref@yahoo.com>
2022-02-27 20:33 ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28  3:30   ` Eli Zaretskii
2022-02-28  7:09     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 12:19       ` Eli Zaretskii
2022-02-28 21:44         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 12:55           ` Eli Zaretskii
2022-03-01 15:23             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 17:38               ` Eli Zaretskii
2022-03-01 18:50                 ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 19:37                   ` Eli Zaretskii
2022-03-01 20:08                     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 20:33                       ` Eli Zaretskii
2022-03-01 21:51                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03  9:46                           ` Eli Zaretskii
2022-03-03 12:46                             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:05                               ` Eli Zaretskii
2022-03-03 14:16                                 ` Lars Ingebrigtsen
2022-03-03 14:25                                   ` Eli Zaretskii
2022-03-03 14:51                                     ` Lars Ingebrigtsen
2022-03-03 15:04                                       ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 15:22                                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:39                                   ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:49                                     ` jeff
2022-02-28  9:41   ` 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=86wmjzg93f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=atamariya@gmail.com \
    --cc=emacs-devel@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.
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.