From: Andy Moreton <andrewjmoreton@gmail.com>
To: 35219@debbugs.gnu.org
Subject: bug#35219: 27.0.50; Problems with nnimap groups with non-ASCII characters
Date: Thu, 18 Apr 2019 21:42:57 +0100 [thread overview]
Message-ID: <vz1imvb59ke.fsf@gmail.com> (raw)
In-Reply-To: <m3sguqatmx.fsf@gnus.org>
On Thu 18 Apr 2019, Eric Abrahamsen wrote:
> Andy Moreton <andrewjmoreton@gmail.com> writes:
>> I see a similar symptom, but with a different recipe:
>> - start Gnus
>> - open the server buffer, select a server, and subscribe to a new group
>> - quit the server buffer
>> - in the group buffer, kill the group line for the new group
>> At this point, emacs is busy but unresponsive. Breaking in with ^G
>> results in emacs becoming responsive agin, but all of the group lines
>> disappear from the group buffer.
>>
>> Something is still not quite right.
>
> I'm not able to reproduce that, using a nntp group from gmane -- can you
> give me more detail about how you trigger it?
I used an nntp group from gmane to check this. After hitting ^g in the
recipe above, emacs shows the last 3 lines of the original group buffer,
and typing 'g' toudpate the group buffer restores the display to all of
the missing groups.
After more testing, it seems that this wrong display depends on using
topics in the group buffer. If I toggle topics off ('t' in the group
buffer) then killing the newly added group appears to work normally.
With topics enabled, adding a new group and then saving .newsrc.eld ('s'
in the group buffer) still results in the bad behaviour when killing the
new group.
Killing/yanking a group that was already in .newsrc.eld before gnus was
started works normally.
I've only checked this with my usual config though, rather than
something stripped down to produce a minimal test case.
> Unfortunately, the last round of changes might have left some cruft in
> your .newsrc.eld file, if you had groups with non-ascii names. If you've
> got some of that cruft in your group list, I suppose it's possible that
> trying to kill a group might enter some sort of loop...
All of the groups in my .newsrc.eld have ASCII names.
AndyM
next prev parent reply other threads:[~2019-04-18 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 13:15 bug#35219: 27.0.50; Problems with nnimap groups with non-ASCII characters Lars Ingebrigtsen
2019-04-10 17:14 ` Eric Abrahamsen
2019-04-15 2:19 ` Eric Abrahamsen
2019-04-18 15:55 ` Eric Abrahamsen
2019-04-18 17:43 ` Andy Moreton
2019-04-18 19:48 ` Eric Abrahamsen
2019-04-18 20:42 ` Andy Moreton [this message]
2019-04-18 23:53 ` Eric Abrahamsen
2019-04-19 5:48 ` Katsumi Yamaoka
2019-04-19 16:14 ` Eric Abrahamsen
2019-04-19 12:43 ` Andy Moreton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vz1imvb59ke.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=35219@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).