From: Christopher Howard <christopher@librehacker.com>
To: 48843@debbugs.gnu.org
Subject: bug#48843: closed (Re: bug#48843: pos_visible_p segfault)
Date: Sat, 05 Jun 2021 05:49:48 -0800 [thread overview]
Message-ID: <60601981c3ccef19984a877bcef3d7a9a56394cf.camel@librehacker.com> (raw)
In-Reply-To: <handler.48843.D48843.162287677527510.notifdone@debbugs.gnu.org>
This is for certain?
The bug you referenced indicates the problem has been fixed in 27.2,
which is the version I am currently using.
Christopher
next prev parent reply other threads:[~2021-06-05 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 5:05 bug#48843: pos_visible_p segfault Christopher Howard
2021-06-05 7:05 ` Eli Zaretskii
[not found] ` <handler.48843.D48843.162287677527510.notifdone@debbugs.gnu.org>
2021-06-05 13:49 ` Christopher Howard [this message]
2021-06-05 13:54 ` bug#48843: closed (Re: bug#48843: pos_visible_p segfault) Christopher Howard
2021-06-05 14:28 ` Eli Zaretskii
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=60601981c3ccef19984a877bcef3d7a9a56394cf.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=48843@debbugs.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 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).