From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: gnus-summary-edit-article vs. Unicode
Date: Thu, 23 Jul 2009 21:17:00 +0900 [thread overview]
Message-ID: <b4mocrbppab.fsf@jpl.org> (raw)
In-Reply-To: <87y6qgsalj.fsf@jidanni.org>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
>>>>> jidanni@jidanni.org wrote:
> Let's say you make a draft,
> To: zzz
> Subject: 測試
> X-Draft-From: ("nndraft:drafts")
> --text follows this line--
> 測試
> and save it with message-dont-send (C-c C-d). OK, now later one day
> reenter the *Drafts* group, and view that draft. Now put the cursor in
> that draft's buffer, and hit
>>> e runs the command gnus-summary-edit-article
RS> In a draft summary buffer, `e' runs `gnus-draft-edit-message'.
> I know. I'm talking about when you have already put the cursor into the
> Draft itself, and then you hit e.
>>> Chinese characters present become \333.
The cause is that the "e" key is bound to `gnus-summary-edit-article'
in the article buffer unconditionally. Here is a patch. Not tested
thoroughly, though.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 903 bytes --]
--- gnus-art.el~ 2009-06-01 11:45:19 +0000
+++ gnus-art.el 2009-07-23 12:15:49 +0000
@@ -4270,7 +4270,7 @@
"s" gnus-article-show-summary
"\C-c\C-m" gnus-article-mail
"?" gnus-article-describe-briefly
- "e" gnus-summary-edit-article
+ "e" gnus-article-read-summary-keys
"<" beginning-of-buffer
">" end-of-buffer
"\C-c\C-i" gnus-info-find-node
@@ -6374,8 +6374,13 @@
(select-window win))))
(setq in-buffer (current-buffer))
;; We disable the pick minor mode commands.
- (if (and (setq func (let (gnus-pick-mode)
- (lookup-key (current-local-map) keys)))
+ (if (and (let ((maps (current-minor-mode-maps))
+ gnus-pick-mode)
+ (while maps
+ (when (setq func (lookup-key (pop maps) keys))
+ (setq maps nil)))
+ (or func
+ (setq func (lookup-key (current-local-map) keys))))
(functionp func)
(condition-case code
(progn
next prev parent reply other threads:[~2009-07-23 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 8:17 jidanni
2009-07-22 18:54 ` Reiner Steib
2009-07-22 20:53 ` jidanni
2009-07-23 12:17 ` Katsumi Yamaoka [this message]
2009-07-24 0:01 ` Katsumi Yamaoka
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=b4mocrbppab.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/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).