From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: I've got the \201 blues again, dammit
Date: 01 Oct 1998 16:15:22 +0200 [thread overview]
Message-ID: <m3vhm4mkqt.fsf@sparky.gnus.org> (raw)
In-Reply-To: Rolf Marvin B|e Lindgren's message of "Thu, 01 Oct 1998 07:08:21 GMT"
Rolf Marvin B|e Lindgren <roffe@morgoth.uio.no> writes:
> message-mode sets enable-multibyte-characters to t, even tho I _have_
> used custom to set enable-multibyte-characters and
> default-enable-multibyte-characters to nil, _and_ I way --unibyte when I
> start Emacs.
The dinosaur has only been thoroughly tested with
enable-multibyte-characters untouched (that is, t) and no --unibyte.
It should, of course, work in unibyte mode as well, but there are
certain things that I have yet to get to work right, involving copying
strings from one buffer to another, when one of the buffers are
multibyte and the other is not.
For now (until these glitches are stamped out), the only way to run
pgnus is in multibyte mode.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-10-01 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-01 7:08 Rolf Marvin B|e Lindgren
1998-10-01 14:15 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vhm4mkqt.fsf@sparky.gnus.org \
--to=larsi@gnus.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.
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 NNTP newsgroup(s).