From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52295@debbugs.gnu.org
Subject: bug#52295: 28.0.90; Killing text results in coding system complaint
Date: Sun, 12 Dec 2021 18:58:22 +0800 [thread overview]
Message-ID: <87mtl6xf75.fsf@yahoo.com> (raw)
In-Reply-To: <83bl1szf1o.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Dec 2021 16:05:07 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> ??? It appears that coding_from_cp is actually returning nil in this
>> case.
>>
>> This must be a bug in intern, because I don't see how else it could
>> possibly return nil.
> It could also be some memory-related snafu, or some stupid omission
> during startup when we run on Windows 9X.
FWIW, the problem doesn't appear with an unexec build (though I did have
to fix the build process somewhat to get unexec to work on the build
system running MSYS).
I will build a pdumper build with all the usual debug options and see
what comes up.
next prev parent reply other threads:[~2021-12-12 10:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875ys3sgfv.fsf.ref@yahoo.com>
2021-12-05 6:40 ` bug#52295: 28.0.90; Killing text results in coding system complaint luangruo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 8:45 ` Eli Zaretskii
2021-12-05 8:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 9:12 ` Eli Zaretskii
2021-12-05 9:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-06 12:33 ` Eli Zaretskii
2021-12-07 3:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 5:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 7:33 ` Eli Zaretskii
2021-12-07 9:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 10:07 ` Eli Zaretskii
2021-12-07 10:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 10:50 ` Eli Zaretskii
2021-12-07 14:05 ` Eli Zaretskii
2021-12-12 10:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-12-12 11:22 ` Eli Zaretskii
2021-12-12 12:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 13:31 ` Eli Zaretskii
2021-12-13 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-13 3:23 ` Eli Zaretskii
2021-12-18 0:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-18 6:48 ` Eli Zaretskii
2021-12-18 18:30 ` Eli Zaretskii
2021-12-19 0:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 9:09 ` bug#52295: windows 98: " Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87mtl6xf75.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=52295@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).