From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: michael_heerdegen@web.de, 29422@debbugs.gnu.org
Subject: bug#29422: 27.0.50; Symbol enable-multibyte-characters may not be buffer-local
Date: Sat, 25 Nov 2017 19:19:15 +0200 [thread overview]
Message-ID: <834lpi8eek.fsf@gnu.org> (raw)
In-Reply-To: <jwvtvxi9ukg.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Sat, 25 Nov 2017 11:47:25 -0500)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Michael Heerdegen <michael_heerdegen@web.de>, 29422@debbugs.gnu.org
> Date: Sat, 25 Nov 2017 11:47:25 -0500
>
> > Yes, but signaling "Setting constant" when we actually mean a
> > read-only symbol is sub-optimal, IMO.
>
> That's the error that we've been using for (setq
> enable-multibyte-characters ...) since Emacs-21.
??? The code you changed signaled a "Symbol %s may not be
buffer-local" error, not "Setting constant". What am I missing?
> > How about inventing a new error symbol for these cases?
>
> I haven't found a situation where I needed to distinguish those two
> error cases yet, so I don't see any need for that, but if you feel like
> it, that's fine (tho better make that new error be a sub-error of
> `setting-constant` so as not to break existing code).
I meant for you to do that, as part of fixing this problem, but if you
don't feel like it, we should at least change the ELisp manual, as it
now contradicts the code.
next prev parent reply other threads:[~2017-11-25 17:19 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834lpi8eek.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 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.