From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: thievol@posteo.net, schwab@linux-m68k.org, 44486@debbugs.gnu.org
Subject: bug#44486: 27.1; C-@ chars corrupt elisp buffer
Date: Mon, 09 Nov 2020 18:57:07 +0200 [thread overview]
Message-ID: <83imae4gf0.fsf@gnu.org> (raw)
In-Reply-To: <875z6ejy1x.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 09 Nov 2020 17:27:06 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: handa@gnu.org, thievol@posteo.net, schwab@linux-m68k.org,
> 44486@debbugs.gnu.org
> Date: Mon, 09 Nov 2020 17:27:06 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 0 is different: it says to obey the value of
> > inhibit-null-byte-detection resp. inhibit-iso-escape-detection. t
> > means inhibit the detection unconditionally, which is not what we
> > want.
> >
> > (We could use any non-nil, non-t value, of course; I've chosen to use
> > zero for consistency with what we do for 'undecided', see coding.c.)
>
> I see. Perhaps the difference between the various non-nil values should
> be mentioned in the doc strings of the two variables? They only mention
> nil/non-nil now, as far as I can see.
The _variables_ are simple booleans; it's the value of the
:inhibit-null-byte-detection _property_ of a coding-system that is a
tri-state. And that fact is documented in the doc string of
define-coding-system.
next prev parent reply other threads:[~2020-11-09 16:57 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 [this message]
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
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=83imae4gf0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44486@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).