From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: drafts and infamous \202 :-(
Date: 05 May 2000 10:22:51 +0200 [thread overview]
Message-ID: <dpln1pflt0.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Shenghuo ZHU's message of "05 May 2000 02:30:54 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> It is not a bug. In drafts group, the messages are stored in a
> internal coding-system, emacs-mule for Emacs and escape-quoted for
> XEmacs, therefore, you may see \202 when you press `e'.
>
> To edit a draft, you should use `D e' instead.
That's crock! Either `e' should do proper conversion, or it should be
disabled altogether. (Or it should merely call `D e'.)
next prev parent reply other threads:[~2000-05-05 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 6:12 Pavel Janík ml.
2000-05-05 6:12 ` Pavel Janík ml.
2000-05-05 6:30 ` Shenghuo ZHU
2000-05-05 7:50 ` Pavel Janík ml.
2000-05-05 9:37 ` Kai Großjohann
2000-05-05 10:20 ` Pavel Janík ml.
2000-05-05 10:57 ` Kai Großjohann
2000-05-05 8:22 ` Hrvoje Niksic [this message]
2000-05-05 16:40 ` Shenghuo ZHU
2000-05-05 16:54 ` Hrvoje Niksic
2000-05-14 16:04 ` Mike Fabian
2000-05-14 18:07 ` Shenghuo ZHU
2000-05-14 21:05 ` Mike Fabian
2000-05-05 9:34 ` 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=dpln1pflt0.fsf@mraz.iskon.hr \
--to=hniksic@iskon.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).