From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Message - which charset?
Date: 16 Mar 1999 08:23:01 +0100 [thread overview]
Message-ID: <87n21dq4oa.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Dmitry Yaitskov's message of "14 Mar 1999 12:49:22 -0500"
Dmitry Yaitskov <dimas@home.com> writes:
> select the coding system. And with some simple elisp, I can now
> determine which of the 2 coding systems is used in a particular
> incoming message. My only problem left is - I'd like to be able to
> specify the charset "of my choice" for the message that I compose (for
> the whole message or for the 1st part of a mime one), based on the
> headers/body of the (1st part of the 1st) message being replied
> to/followed up.
Try setting `message-default-charset', or making your simple elisp set
it for you.
next prev parent reply other threads:[~1999-03-16 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 7:49 Dmitry Yaitskov
1999-03-14 16:19 ` Lars Magne Ingebrigtsen
1999-03-14 17:49 ` Dmitry Yaitskov
1999-03-16 7:23 ` Hrvoje Niksic [this message]
1999-03-16 7:55 ` Dmitry Yaitskov
1999-03-16 8:09 ` 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=87n21dq4oa.fsf@pc-hrvoje.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).