From: Karl Eichwalder <ke@gnu.franken.de>
Cc: ding@gnus.org
Subject: Re: \201s in Gnus buffers (Re: off topic alert: XEmacs vs Emacs?)
Date: 21 Jul 1999 21:19:47 +0200 [thread overview]
Message-ID: <shogh5lsj0.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "21 Jul 1999 12:06:21 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
| ,-----
| | (set-language-environment "Latin-1")
| | (setq default-input-method "german-prefix")
| `-----
Thanks for the hint. The explicit language environment setting isn't
needed; Emacs seems to recognize my environment.
I do see \201s only in header lines iff the article is cached -- but
before digging deeper, I'll update pgnus.
| I think I used to get \201 in the draft groups, but hitting `D e' made
| them go away, and I didn't try to investigate...
Isn't one \201 already too much?
| Is this From line better? I changed from "name <address>" to "address
| (name)" which seems to work better with non-ASCII characters in the
| name.
It's surely not your fault; your header line is and was valid. If the
error will occur after updating pgnus, I'll try to write an useful bug
report.
--
Karl Eichwalder
next prev parent reply other threads:[~1999-07-21 19:19 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 ` \201s in Gnus buffers (Re: off topic alert: XEmacs vs Emacs?) Karl Eichwalder
1999-07-21 10:06 ` Kai Großjohann
1999-07-21 19:19 ` Karl Eichwalder [this message]
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=shogh5lsj0.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).