Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Non-MULE XEmacs default charset
Date: 16 Jan 1999 18:11:57 +0100	[thread overview]
Message-ID: <kig1zkv3zxe.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "16 Jan 1999 17:28:59 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I imagine that Message isn't the only package that would be
> interested in knowing what charset you're using.  Would it make
> sense to have a general non-Mule-XEmacs variable?
> `default-charset'?

Yes, I think it would make sense, but I'm not sure if it's worth the
trouble at this stage.  Also, the notion of "charset" is in collision
with Mule's coding systems (or whatever it is that Mule uses).


  reply	other threads:[~1999-01-16 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-15 22:17 Lars Magne Ingebrigtsen
1999-01-15 23:33 ` Hrvoje Niksic
1999-01-16 16:28   ` Lars Magne Ingebrigtsen
1999-01-16 17:11     ` Hrvoje Niksic [this message]
1999-01-16 22:47       ` Lars Magne Ingebrigtsen
1999-01-20 21:20   ` Kai.Grossjohann
1999-01-21 13:53     ` Hrvoje Niksic

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=kig1zkv3zxe.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).