From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: thievol@posteo.net, larsi@gnus.org, schwab@linux-m68k.org,
44486@debbugs.gnu.org
Subject: bug#44486: 27.1; C-@ chars corrupt elisp buffer
Date: Sun, 15 Nov 2020 17:14:05 +0200 [thread overview]
Message-ID: <83lff2tzya.fsf@gnu.org> (raw)
In-Reply-To: <jwvima7pn16.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 14 Nov 2020 17:56:36 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: thievol@posteo.net, larsi@gnus.org, schwab@linux-m68k.org,
> 44486@debbugs.gnu.org
> Date: Sat, 14 Nov 2020 17:56:36 -0500
>
> >> For .el files, we can always bind inhibit-null-byte-detection to t
> >> when we load or visit such files.
> > Alternatively, we could introduce a separate coding-system whose
> > :inhibit-null-byte-detection property is t, and use that for *.el
> > files.
>
> If you want to go that route, that's fine by me.
I actually think that we don't need to do anything. We've lived for 7
years with a reality that is worse than what is now on master, and no
one complained.
But if you are very unhappy about this, we _could_ introduce a new
coding-system for *.el files.
> (especially since we don't have any evidence that potential other
> users would favor the current behavior over the
> inhibit-null-byte-detection one).
The current behavior on master is to heed inhibit-null-byte-detection;
the current behavior in Emacs 27 is to ignore it, and always consider
a .el file with null bytes as binary. I hope you agree that the
behavior on master is slightly better, at least in that it won't
surprise users.
next prev parent reply other threads:[~2020-11-15 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:11 bug#44486: 27.1; C-@ chars corrupt elisp buffer Thierry Volpiatto
2020-11-06 15:33 ` Andreas Schwab
2020-11-06 15:40 ` Eli Zaretskii
2020-11-06 16:17 ` Eli Zaretskii
2020-11-06 20:07 ` Eli Zaretskii
2020-11-09 15:44 ` Lars Ingebrigtsen
2020-11-09 16:14 ` Eli Zaretskii
2020-11-09 16:27 ` Lars Ingebrigtsen
2020-11-09 16:57 ` Eli Zaretskii
2020-11-10 14:29 ` Lars Ingebrigtsen
2020-11-10 16:04 ` Eli Zaretskii
2020-11-14 14:02 ` Stefan Monnier
2020-11-14 15:09 ` Eli Zaretskii
2020-11-14 15:19 ` Stefan Monnier
2020-11-14 16:13 ` Eli Zaretskii
2020-11-14 17:55 ` Stefan Monnier
2020-11-14 18:08 ` Eli Zaretskii
2020-11-14 18:14 ` Eli Zaretskii
2020-11-14 22:56 ` Stefan Monnier
2020-11-15 15:14 ` Eli Zaretskii [this message]
2020-11-14 22:53 ` Stefan Monnier
2020-11-15 15:08 ` Eli Zaretskii
2020-11-15 18:31 ` Stefan Monnier
2020-11-14 12:43 ` Eli Zaretskii
2020-11-06 19:18 ` Thierry Volpiatto
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=83lff2tzya.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44486@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=thievol@posteo.net \
/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).