From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: coding-system for drafts
Date: Wed, 30 Oct 2002 11:15:43 +0100 [thread overview]
Message-ID: <84ptts6xm8.fsf@crybaby.uni-duisburg.de> (raw)
In-Reply-To: <yotlsmyopv26.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> We have to read a draft file twice, however large a file may be.
> We should use a local-hook like write-contents-hooks for adding
> an extra header, though it isn't difficult. An extra header
> should be deleted before sending. Gnus can do it, don't other
> programs use the same draft?
Why do you have to read a draft twice? If you design the coding
cookie ingeniously, then you won't need to do that.
You can put
X-Gnus-Coding: -*- coding: frumple -*-
as the first header. Then the Emacs machinery will take care of
automatically selecting the frumple coding for reading the file.
However, the above MUST be the first line in the file.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-30 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 12:25 sending delayed articles bug Katsumi Yamaoka
2002-10-25 13:01 ` Kai Großjohann
2002-10-29 9:58 ` coding-system for drafts (was Re: sending delayed articles bug) Katsumi Yamaoka
2002-10-29 14:27 ` coding-system for drafts Kai Großjohann
2002-10-30 1:36 ` Katsumi Yamaoka
2002-10-30 10:15 ` Kai Großjohann [this message]
2002-10-30 12:28 ` Katsumi Yamaoka
2002-10-30 16:14 ` Kai Großjohann
2002-10-31 4:44 ` Katsumi Yamaoka
2002-10-31 7:35 ` Katsumi Yamaoka
2002-10-31 17:35 ` Kai Großjohann
2002-11-01 4:32 ` Katsumi Yamaoka
2002-11-05 12:36 ` Kai Großjohann
2002-10-31 17:30 ` Kai Großjohann
2002-11-01 17:49 ` Kai Großjohann
2002-11-05 9:23 ` Katsumi Yamaoka
2002-11-05 12:38 ` Kai Großjohann
2002-11-08 7:25 ` Katsumi Yamaoka
2002-11-13 16:14 ` Reiner Steib
2002-11-02 15:34 ` TSUCHIYA Masatoshi
2002-11-05 12:23 ` Kai Großjohann
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=84ptts6xm8.fsf@crybaby.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).