From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: several issues with non ascii characters in group names
Date: Fri, 17 May 2013 14:16:51 +0200 [thread overview]
Message-ID: <874ne1243w.fsf@micropit.couberia.selfip.net> (raw)
In-Reply-To: <b4mvc6hri12.fsf@jpl.org>
On Fri, May 17 2013, Katsumi Yamaoka wrote:
> Anyway I'd like to know what happens after re-creating those groups.
Hi Katsumi,
I've tried to reproduce the issue by creating new groups the same way,
as I always do. But I can't.
Unfortunately, I've just updated from 真 Gnus v0.6 to 0.8. So I don't
know, if this issue has gone with the update, or if I have to wait some
time, before that strange behaviour happens again...
I've also removed all the duplicated lines in the active file, for each
group I kept the line with the highest number. Now I can see all
messages in the summary buffers for these groups.
Probably, the issue is really solved.
Thanks,
--
Peter
next prev parent reply other threads:[~2013-05-17 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 19:24 Peter Münster
2013-05-16 23:29 ` Katsumi Yamaoka
2013-05-17 7:12 ` Peter Münster
2013-05-17 10:56 ` Katsumi Yamaoka
2013-05-17 12:16 ` Peter Münster [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-16 19:17 Peter Münster
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=874ne1243w.fsf@micropit.couberia.selfip.net \
--to=pmlists@free.fr \
--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).