From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ding@gnus.org
Subject: Re: Look ma: RFÇ2047
Date: Sat, 20 Feb 1999 17:34:59 +0100 (MET) [thread overview]
Message-ID: <HBF.990220jpzw@bombur.uio.no> (raw)
[Sorry about breaking the threading; your message didn't reach the
emacs.ding newsgroup and I couldn't find the message-ID in the list
archive.]
>> Sure, but not getting it wrong is still better... If I have already
>> _told_ Emacs which charset I'm using, why should Gnus override that?
>
> Gnus shouldn't, and won't, once someone tells me how to do that. :-)
"ask on gnu.emacs.help"...
>>>> Instead we need a
>>>> recommended way for the user to tell Emacs to switch character set
>>>> (font) - which Gnus can notice.
>>>
>>> This variable is only used in non-Mule Emacsen, so this shouldn't occur.
>>
>> that's what I mean: Even non-Mule Emacsen need that recommended way to
>> switch character set.
>
> The assumption when using a non-Mule Emacs is that you're going to
> edit text using only a single charset.
"one charset at a time", please:-)
Well OK, a recomended way to tell Emacs or Gnus which character set is
in use, then.
--
Hallvard
next reply other threads:[~1999-02-20 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-20 16:34 Hallvard B Furuseth [this message]
1999-02-21 10:09 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1999-01-15 23:32 Lars Magne Ingebrigtsen
1999-01-16 2:01 ` Russ Allbery
1999-01-16 3:27 ` Lars Magne Ingebrigtsen
1999-01-20 21:26 ` Kai.Grossjohann
1999-01-20 21:26 ` Kai.Grossjohann
1999-01-21 15:55 ` Lars Balker Rasmussen
1999-02-01 23:33 ` Hallvard B Furuseth
1999-02-02 0:51 ` Russ Allbery
1999-02-02 9:12 ` Yair Friedman
1999-02-02 20:13 ` Lars Magne Ingebrigtsen
1999-02-15 2:19 ` Hallvard B Furuseth
1999-02-19 14:09 ` Lars Magne Ingebrigtsen
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=HBF.990220jpzw@bombur.uio.no \
--to=h.b.furuseth@usit.uio.no \
--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).