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: Sat, 14 Nov 2020 18:13:49 +0200 [thread overview]
Message-ID: <83eekvvruq.fsf@gnu.org> (raw)
In-Reply-To: <jwvsg9cq8cc.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 14 Nov 2020 10:19:57 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org, thievol@posteo.net, handa@gnu.org,
> schwab@linux-m68k.org, 44486@debbugs.gnu.org
> Date: Sat, 14 Nov 2020 10:19:57 -0500
>
> >> Actually, for prefer-utf-8 files, I think we never want to automatically
> >> fallback to binary.
> > I think you are assuming prefer-utf-8 is something other than what it
> > is. It is not a variant of UTF-8, it is a variant of 'undecided'
> > (i.e. it starts by detecting the encoding), which prefers UTF-8 if
> > that can decode the text.
>
> My position is not based on principles but on pragmatic concerns.
> AFAIK `prefer-utf-8` is only ever used for files which are known to
> contain text and should almost always contain UTF-8 text.
For those, we should use utf-8, not prefer-utf-8.
> I believe if there's a NUL byte in such a files but it otherwise doesn't
> contain any invalid UTF-8 byte sequence, it will result in better
> behavior if we treat it as UFT-8 than as binary.
We treat null bytes as the _single_ telltale sign of a binary file.
If we disable that in coding-systems that are supposed to _detect_
encoding, we will never be able to detect binary files.
next prev parent reply other threads:[~2020-11-14 16:13 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eekvvruq.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.