From: Pavel.Janik@inet.cz (Pavel Janik ml.)
Subject: Re: Editing drafts in the queue in ISO-8859-2
Date: 20 Apr 2000 23:01:25 +0200 [thread overview]
Message-ID: <m3u2gwo5ay.fsf@SnowWhite.inet.cz> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "20 Apr 2000 02:16:19 +0200"
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date: 20 Apr 2000 02:16:19 +0200
Hi,
> Hm. I wouldn't have been surprised if the charset was wrong, but
> \x948 would lead me to believe that `prin' or its friends have been
> involved at some point, which `D e' shouldn't be doing.
>
> Or perhaps you didn't mean a "x" after the backslash?
no. I dig deeply and here are the results.
1. I composed test message with ěščřžýáíé (ISO-8859-2) letters in the body.
2. C-c C-c and the message is stored in the queue.
3. I went to the queue group and saw the message in the summary. The message
itself looks OK in the message buffer. I tried to D e on it. I received
\357\251 in the body. The numbers are random (i.e. not exactly the same I've
got, but you got the point :-). When I press C-x k RET here, the message goes
into drafts folder from the queue.
BAD.
1. I composed another test message with ěščřžýáíé (ISO-8859-2) letters in the
body and sent it to queue.
2. I tried to press `e' in the summary. Everything is ok and the message _is_
readable with correct charset. I can add another ISO 8859-2 characters in
it and they are showed ok. Then I pressed C-c C-c to end the edits. The
message buffer is then switched into \357\251 chars like above. The I can
show another message and came back to my test message again and it is
showed in the message buffer correctly. And it is sent correctly.
Hmm, I accidentally pressed D e in the message buffer in the queue group and
got an error message. Hm, D is gnus-article-read-summary-keys in the message
buffer but when I'm in the message buffer in the queue group, Emacs is waiting
for another key and shows D- in the minibuffer... Maybe this will help you to
debug it.
Backtrace:
Signaling: (wrong-type-argument commandp 1)
call-interactively(1)
gnus-article-read-summary-keys(nil)
* call-interactively(gnus-article-read-summary-keys)
recursive-edit()
byte-code("Ć\b! \x11Č !pĘË\x1a^[\x1cĚ +eb `ÎĎ! y`| \r@Ň>N
debug(error (wrong-type-argument commandp 1))
call-interactively(1)
gnus-article-read-summary-keys(nil)
* call-interactively(gnus-article-read-summary-keys)
recursive-edit()
byte-code("Ć\b! \x11Č !pĘË\x1a^[\x1cĚ +eb `ÎĎ! y`| \r@Ň>N
debug(error (wrong-type-argument commandp 1))
call-interactively(1)
gnus-article-read-summary-keys(nil)
* call-interactively(gnus-article-read-summary-keys)
GNU Emacs 20.6/GNUS 5.8.4
--
Pavel Janík ml.
Pavel.Janik@inet.cz
next prev parent reply other threads:[~2000-04-20 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-10 6:58 Pavel Janik ml.
2000-04-20 0:16 ` Lars Magne Ingebrigtsen
2000-04-20 21:01 ` Pavel Janik ml. [this message]
2000-04-21 1:28 ` Shenghuo ZHU
2000-04-21 11:56 ` Lars Magne Ingebrigtsen
2000-04-21 18:32 ` Pavel Janik ml.
2000-04-21 19:15 ` Lars Magne Ingebrigtsen
2000-04-21 20:12 ` Shenghuo ZHU
2000-04-22 11:17 ` Lars Magne Ingebrigtsen
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=m3u2gwo5ay.fsf@SnowWhite.inet.cz \
--to=pavel.janik@inet.cz \
/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).