From: Chong Yidong <cyd@stupidchicken.com>
To: ding@gnus.org
Cc: 1677@emacsbugs.donarmstrong.com
Subject: bug#1677: 23.0.60; GNUS groups and non ascii characters: mails disappear
Date: Sat, 27 Dec 2008 09:27:30 -0500 [thread overview]
Message-ID: <87y6y1hewd.fsf@cyd.mit.edu> (raw)
Here is a bug against Gnus with Emacs CVS. Could you guys take a look?
Thanks.
Sebastian Rose <sebastian_rose@gmx.de> wrote:
I use a group name containing the german letter `ö'. My whole Debian
System is utf-8 based and I save all files (.emacs, .gnus.el....) in
utf-8 by default.
Here is the relevant part of an example .gnus.el:
(setq nnmail-split-methods
'(("list:monotone-devel" "Subject:.*\\[Monotone-devel\\]")
("list:emacs-devel" "To:.*emacs-devel@gnu.org")
("unmöglich" "\\(To\\|CC\\|Sender\\|From\\):.*@example.de")
("mail:eingang" "")
))
In the group buffer `unmöglich' is displayed as
nnml:unm\366glich
When I fetch new mails, the line in the group buffer changes as expected
to
6: nnml:unm\336glich
Moving point to that line and pressing SPACE, that is
(gnus-group-read-group &optional all no-article group select-articles),
makes all the mails disapear again, and the line looks like I have no
mails in that group anymore:
0: nnml:unm\336glich
The summarybuffer does not open up. If the summary buffer was opened
already, it's contents are not changed to reflect the contents of
`unmöglich'.
sh$ ls -l ~/emacs/gnus/Mail/
drwxr-xr-x 2 sebastian sebastian 4096 23. Dez 12:48 unmöglich
drwxr-xr-x 2 sebastian sebastian 4096 23. Dez 15:12 unm?glich
...revealsI have two directories for this group, both of which were
touched today:
`unmöglich' was touched when I started emacs/gnus.
This is, where I found 3 out of 6 mails (maybe the `6: ...'
was wrong in the group buffer?).
`unm?glich' was touched when I fetched Mail (or when I hit the spacebar
in the group buffer - not shure yet).
This one is empty.
reply other threads:[~2008-12-27 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y6y1hewd.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=1677@emacsbugs.donarmstrong.com \
--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).