From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52554@debbugs.gnu.org
Subject: bug#52554: 28.0.90; mm-inline-media-tests customization breaks .emacs reading
Date: Thu, 16 Dec 2021 16:46:36 +0100 [thread overview]
Message-ID: <87mtl0o8mb.fsf@gmail.com> (raw)
In-Reply-To: <8335msh8j0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Dec 2021 17:30:27 +0200")
>>>>> On Thu, 16 Dec 2021 17:30:27 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Thu, 16 Dec 2021 16:18:13 +0100
>>
>> That has an embedded 'NUL' just before the \302 (Iʼve encoded it),
>> which causes 'buffer-file-coding-system' to be incorrect
>> ('no-conversion in this case) so any non-ascii character causes a read
>> error:
>>
>> $ HOME=/tmp emacs --debug-init
>>
>> Debugger entered--Lisp error: (invalid-read-syntax "?" 1 0)
>> read(#<buffer *load*>)
>> eval-buffer(#<buffer *load*> nil "/tmp/.emacs" nil t) ; Reading at buffer position 573
>> load-with-code-conversion("/tmp/.emacs" "/tmp/.emacs" t t)
>> load("~/.emacs" noerror nomessage)
Eli> Perhaps we should bind inhibit-null-byte-detection to a non-nil value
Eli> while loading the init file?
The init file and 'custom-file'? (anyone who manually puts byte-code
in their .emacs either knows what theyʼre doing or will soon learn :-) )
Robert
--
next prev parent reply other threads:[~2021-12-16 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:18 bug#52554: 28.0.90; mm-inline-media-tests customization breaks .emacs reading Robert Pluim
2021-12-16 15:30 ` Eli Zaretskii
2021-12-16 15:46 ` Robert Pluim [this message]
2021-12-16 16:57 ` Eli Zaretskii
2021-12-16 16:13 ` Andreas Schwab
2021-12-16 16:58 ` Eli Zaretskii
2021-12-17 8:23 ` Robert Pluim
2021-12-17 8:29 ` Eli Zaretskii
2021-12-17 8:45 ` Robert Pluim
2021-12-17 12:11 ` Eli Zaretskii
2022-03-16 18:02 ` Robert Pluim
2021-12-19 12:01 ` Lars Ingebrigtsen
[not found] ` <87h7b3ve9a.fsf@gmail.com>
2021-12-20 9:22 ` 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=87mtl0o8mb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=52554@debbugs.gnu.org \
--cc=eliz@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).