unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: rpluim@gmail.com, 52554@debbugs.gnu.org
Subject: bug#52554: 28.0.90; mm-inline-media-tests customization breaks .emacs reading
Date: Thu, 16 Dec 2021 18:58:19 +0200	[thread overview]
Message-ID: <83tuf8fpw4.fsf@gnu.org> (raw)
In-Reply-To: <874k78o7cu.fsf@igel.home> (message from Andreas Schwab on Thu, 16 Dec 2021 17:13:53 +0100)

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Robert Pluim <rpluim@gmail.com>,  52554@debbugs.gnu.org
> Date: Thu, 16 Dec 2021 17:13:53 +0100
> 
> On Dez 16 2021, Eli Zaretskii wrote:
> 
> >> $ 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)
> >
> > Perhaps we should bind inhibit-null-byte-detection to a non-nil value
> > while loading the init file?
> 
> I'd rather think that custom-save-variable should bind
> print-escape-control-characters to t.

Maybe we should do both?





  reply	other threads:[~2021-12-16 16:58 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
2021-12-16 16:57     ` Eli Zaretskii
2021-12-16 16:13   ` Andreas Schwab
2021-12-16 16:58     ` Eli Zaretskii [this message]
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=83tuf8fpw4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52554@debbugs.gnu.org \
    --cc=rpluim@gmail.com \
    --cc=schwab@linux-m68k.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).