From: Karl Eichwalder <ke@gnu.franken.de>
Cc: "(ding)" <ding@gnus.org>
Subject: \201s in Gnus buffers (Re: off topic alert: XEmacs vs Emacs?)
Date: 21 Jul 1999 06:09:05 +0200 [thread overview]
Message-ID: <shr9m23aqm.fsf_-_@tux.gnu.franken.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "20 Jul 1999 19:39:54 -0400"
(That's not a bug report, but kind of)
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
| * Kai Gro johann <Kai.Grossjohann@CS.Uni-Dortmund.DE> on Tue, 20 Jul 1999
--->--->--->-^^^^
Do you see the \201 here? I do :-(((
| None of which I use; in fact, I compile XEmacs without any of them. I
| switched to XEmacs specifically because I can build it without the
| "features" for which I have no use.
I fear, I've to do the same. Even with Emacs 20.4 the \201 "problem"
isn't solved. Chaching an article which contains perfectly valid
encoded From lines will add spurious \201s. Starting with --unibyte
seems to "work". I'll update Pgnus and than do more tests.
One of the manuals (the Emacs or the Gnus manual) should have a concise
section about setting up Emacs if you want to use Gnus in the 8859
world. Emacs has a lengthy chapter about Mule but that's not what is
needed (sorry that I've to say this). I didn't find an section about
the modeline indicators. Often there are two dashes (= multibyte?),
sometimes there is "-1" (= 8859-1?) but in Gnus or Message buffers I'm
seeing "-=" before the ":".
Other \201 bits are obviously "fixed" with Emacs 20.4 (e.g., umlauts in
menue entries are valid).
I'm not able to say anything about XEmacs which I never used seriously.
--
Karl Eichwalder
next prev parent reply other threads:[~1999-07-21 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 21:34 off topic alert: XEmacs vs Emacs? Kai Großjohann
1999-07-20 23:39 ` Stainless Steel Rat
1999-07-21 4:09 ` Karl Eichwalder [this message]
1999-07-21 10:06 ` \201s in Gnus buffers (Re: off topic alert: XEmacs vs Emacs?) Kai Großjohann
1999-07-21 19:19 ` Karl Eichwalder
1999-07-22 11:01 ` Kai Großjohann
1999-07-22 20:04 ` Karl Eichwalder
1999-07-23 5:03 ` Neil Crellin
1999-08-27 21:14 ` Lars Magne Ingebrigtsen
1999-07-21 11:00 ` off topic alert: XEmacs vs Emacs? Hrvoje Niksic
1999-07-21 12:10 ` Jan Vroonhof
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=shr9m23aqm.fsf_-_@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=ding@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).