unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22818@debbugs.gnu.org
Subject: bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs
Date: Mon, 18 Apr 2022 07:44:15 -0400	[thread overview]
Message-ID: <CAFw1JJ4cvsQJsQC+JvaQEo3UcU75YNeEzr1M4FRreLZ+H=1phw@mail.gmail.com> (raw)
In-Reply-To: <871qxuiq4v.fsf@gnus.org>

> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> This was five years ago -- do you still see this issue on recent Emacs
> versions?

No, I do not see this issue any longer on recent versions of Emacs for
Macos either for the specific case for the bug report, but also
happily Emacs doesn't crash arbitrarily like it used to from this. The
issue can be closed.

Thanks for Emacs,
Aaron





  reply	other threads:[~2022-04-18 11:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 13:41 bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Aaron S. Hawley
2016-05-18 20:07 ` Alan Third
2016-05-18 21:09   ` Aaron S. Hawley
2016-11-18 21:31 ` bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs Josh Berdine
2016-11-19  7:07   ` Eli Zaretskii
2016-11-19 10:07     ` Alan Third
2016-11-19 10:27       ` Eli Zaretskii
2016-11-19 11:18         ` Alan Third
2016-11-19 11:43           ` Eli Zaretskii
2016-11-19 14:53             ` Alan Third
2016-11-19 15:09               ` Eli Zaretskii
2016-11-19 15:51                 ` Alan Third
2016-11-19 18:12                   ` Eli Zaretskii
2016-11-19 19:05                     ` Alan Third
2016-11-19 19:27                       ` Eli Zaretskii
2016-11-19 19:38                         ` Alan Third
2022-04-18 11:32 ` bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Lars Ingebrigtsen
2022-04-18 11:44   ` Aaron S. Hawley [this message]
2022-04-18 11:45     ` 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='CAFw1JJ4cvsQJsQC+JvaQEo3UcU75YNeEzr1M4FRreLZ+H=1phw@mail.gmail.com' \
    --to=aaron.s.hawley@gmail.com \
    --cc=22818@debbugs.gnu.org \
    --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 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).