From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: several issues with non ascii characters in group names
Date: Fri, 17 May 2013 19:56:57 +0900 [thread overview]
Message-ID: <b4mvc6hri12.fsf@jpl.org> (raw)
In-Reply-To: <87obcayt92.fsf@micropit.couberia.selfip.net>
Peter Münster wrote:
>>> 2.) Several entries in server buffer for the same group
>>
>>> For the group "stéphane" for example, I have these lines in the server
>>> buffer:
>>
>> *Group* buffer?
> No. The *Gnus Browse Server* {nnml:Email} buffer. This never happens in
> the group buffer.
Ah, I see (I rarely see nnml's server, so I didn't think of it).
>>> U 8: stéphane
>>> U 1: stéphane
>>> U 1: stéphane
>>> U 10: stéphane
>>
>>> Not a big problem, just strange.
>>
>> I guess you have those four groups; in `active', the human-readable
>> names are the same but encodings differ.
> Yes. I have these lines in the active file:
> stéphane 10 1 y
> stéphane 1 1 y
> stéphane 1 1 y
> stéphane 8 1 y
> But encodings don't differ: everything is utf-8.
Hmm. I've ever faced it in the past, though I don't recall how
they were made. But this should be why the server buffer list
those four.
>> A possible solution would be to copy all the existing articles to a
>> temporary group, delete those non-ASCII groups, create the non-ASCII
>> group again, and move the saved articles there.
> How? Just "cp stéphane/* tmp" ?
It will do, but you'll need to run
`M-x nnml-generate-nov-databases-directory RET DIR_NAME RET'
after restoring the articles in the *new* stéphane group.
Instead, doing `B c' or `B m' in the summary buffer seems better.
As for deleting those duplicate groups, I'm not sure `G DEL' does
work as expected, though (you might have to edit manually active,
and .newsrc.eld :<).
> Some further information:
> - After restarting Gnus, I've seen all 10 messages in the summary
> buffer. But later, when creating the summary buffer once again, there
> were only 8 messages
> - It happens *always* with every group that has accented characters.
> Other examples from the *Gnus Browse Server* buffer:
> U 7: jérôme
> U 3: jérôme
> U 2: jérôme
> U 4: jérôme
> U 4: jérôme
> U 5: jérôme
> U 3: jürgen
> U 3: jürgen
> U 3: jürgen
> U 3: jürgen
> U 3: jürgen
> U 3: jürgen
> U 19: valérie
> U 12: valérie
> U 7: valérie
> U 13: valérie
> U 13: valérie
> U 18: valérie
Oh, that's too bad.
>>> 3.) Some messages are not displayed in summary buffer
>>
>>> For example in my group "stéphane" there are 10 messages. There are also
>>> 10 lines in the Mail/stéphane/.overview file, but only 8 are displayed
>>> in the summary buffer. How can I see the other 2 messages in Gnus?
>>
>> Does typing `10000 RET' on that group help?
> No... :(
Anyway I'd like to know what happens after re-creating those groups.
Good luck.
next prev parent reply other threads:[~2013-05-17 10:56 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 [this message]
2013-05-17 12:16 ` Peter Münster
-- 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=b4mvc6hri12.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).