From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 29422@debbugs.gnu.org
Subject: bug#29422: [SUSPECTED SPAM] Re: bug#29422: 27.0.50; Symbol enable-multibyte-characters may not be buffer-local
Date: Sun, 26 Nov 2017 23:42:20 -0500 [thread overview]
Message-ID: <jwv1skkpcb4.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83po856opz.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 Nov 2017 17:31:36 +0200")
>> My patch did not touch `setq`. It just made `make-local-variable` and
>> `make-buffer-local-variable` signal the same error as `setq`.
> Which IMO is confusing because the doc string of
> enable-multibyte-characters says
> Automatically becomes permanently buffer-local when set.
Yes, it's a weird critter. Some versions ago, you could setq-default on
it, whereas you couldn't setq on it.
It'd arguably be cleaner if it were a function rather than a variable.
> Actually, Emacs 21 said something more reasonable:
>
> Variable enable-multibyte-characters is read-only
>
> which was different from the error signaled when trying to change the
> value of, say, t. Only Emacs 22.1 tossed the difference and started
> to signal the same error for both.
Oh, right, Gerd only added defvaralias in Emacs-22 (which is why/when
it get unified into the `constant` bit field, IIRC).
Stefan
prev parent reply other threads:[~2017-11-27 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 7:56 bug#29422: 27.0.50; Symbol enable-multibyte-characters may not be buffer-local Michael Heerdegen
2017-11-25 1:22 ` Michael Heerdegen
2017-11-25 7:53 ` Eli Zaretskii
2017-11-25 16:47 ` Stefan Monnier
2017-11-25 17:19 ` Eli Zaretskii
2017-11-26 2:07 ` Stefan Monnier
2017-11-26 3:39 ` Eli Zaretskii
2017-11-26 15:31 ` Eli Zaretskii
2017-11-27 4:42 ` Stefan Monnier [this message]
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=jwv1skkpcb4.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=29422@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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).