From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 29422@debbugs.gnu.org
Subject: bug#29422: 27.0.50; Symbol enable-multibyte-characters may not be buffer-local
Date: Sat, 25 Nov 2017 09:53:33 +0200 [thread overview]
Message-ID: <83h8ti94le.fsf@gnu.org> (raw)
In-Reply-To: <87y3mvxibw.fsf@web.de> (message from Michael Heerdegen on Sat, 25 Nov 2017 02:22:59 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Sat, 25 Nov 2017 02:22:59 +0100
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Debugger entered--Lisp error: (error "Symbol enable-multibyte-characters may not be buffer-local")
>
> Apparently has been fixed with d1000fb.
Yes, but signaling "Setting constant" when we actually mean a
read-only symbol is sub-optimal, IMO. That error is for setting stuff
like nil and t, which enable-multibyte-characters isn't. It will
confuse users to see this error in that case, I think.
And the ELisp manual clearly states that this error is for "symbols
that evaluate to themselves": nil, t, and keyword symbols. So now the
implementation contradicts the documentation.
How about inventing a new error symbol for these cases?
next prev parent reply other threads:[~2017-11-25 7:53 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 [this message]
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 ` bug#29422: [SUSPECTED SPAM] " Stefan Monnier
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=83h8ti94le.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29422@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).