Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: coding-system for drafts
Date: Wed, 13 Nov 2002 17:14:14 +0100	[thread overview]
Message-ID: <v9isz1e9bd.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <yotl4rasikv9.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 08 Nov 2002 16:25:14 +0900")

On Fri, Nov 08 2002, Katsumi Yamaoka wrote:

> If you have unfinished draft articles or delayed articles which
> has not been sent yet, I strongly recommend you send those
> articles before updating Gnus.
>
> I've restored the default value of `message-draft-coding-system'
> to the old state as before October 29.  It is `emacs-mule' for
> FSF Emacs or `escape-quoted' for XEmacs.  This is used for
> saving draft files.

I used the following to convert a bunch of drafts (from the
"iso-2022-7bit"-period) to the (restored) internal encoding.

(defun rs-gnus-draft-J-to-internal ()
  (interactive)
  (let* ((draft-coding message-draft-coding-system)
	 (message-draft-coding-system 'iso-2022-7bit))
    (gnus-draft-edit-message)
    (set-buffer-file-coding-system draft-coding)
    (setq message-draft-coding-system draft-coding)
    (message-dont-send)
    (gnus-summary-rescan-group t)))
(define-key gnus-draft-mode-map (kbd "D D") 'rs-gnus-draft-J-to-internal)

Just hit `D D' on each message you want to convert (don't use it on
drafts saved as `emacs-mule' or `escape-quoted'!). Please, feel free
to suggest a better solution.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



  reply	other threads:[~2002-11-13 16:14 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
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 [this message]
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=v9isz1e9bd.fsf@marauder.physik.uni-ulm.de \
    --to=4uce.02.r.steib@gmx.net \
    --cc=reiner.steib@gmx.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).