From: "JJ" <bug-gnu-emacs_gnu.org@sumou.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#5981: 24.0.50; Attempt to set a constant symbol: enable-multibyte-characters
Date: Sat, 24 Apr 2010 00:43:35 +0200 [thread overview]
Message-ID: <20100423224113.M38707@porzhiz.org> (raw)
In-Reply-To: <83hbn65x2v.fsf@gnu.org>
This bug persists for me with the current 100012 bzr Emacs
trunk. Problems arise in Gnus.
When trying to `S o m' forward a mail, it reports:
Attempt to set a constant symbol: enable-multibyte-characters
For Gnus in this way it was introduced with Emacs revision 99947. Revision
99946 doesn't elicit this behavior when forwarding an email.
--
JJ
next prev parent reply other threads:[~2010-04-23 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 8:48 bug#5981: 24.0.50; Attempt to set a constant symbol: enable-multibyte-characters Eli Zaretskii
2010-04-20 14:50 ` Stefan Monnier
2010-04-23 17:40 ` ShiroiKuma
2010-04-23 21:20 ` JJ
2010-04-23 22:43 ` JJ [this message]
2010-04-24 17:26 ` JJ
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=20100423224113.M38707@porzhiz.org \
--to=bug-gnu-emacs_gnu.org@sumou.com \
--cc=bug-gnu-emacs@gnu.org \
/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).