unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:43:55 +0100	[thread overview]
Message-ID: <vz1o9535hus.fsf@gmail.com> (raw)
In-Reply-To: <m3sguqatmx.fsf@gnus.org>

On Thu 18 Apr 2019, Eric Abrahamsen wrote:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>>
>>>> This started showing up yesterday after recent changes in Gnus:
>>>>
>>>> To reproduce: Create an nnimap group called "Tést".  Restarting Gnus
>>>> will properly create the group "Tést", but Gnus will also say
>>>>
>>>> nnimap read 12k from quimby.gnus.org (initial sync of 3 groups; please wait)
>>>>
>>>> If you then quit Gnus and restart Gnus, this group will appear:
>>>>
>>>>        *: nnimap+quimby.gnus.org:T\351st
>>>>
>>>> If you try to kill it, all the groups in the buffer will disappear.
>>>>
>>>> So something went wrong during whatever the most recent group-related
>>>> changes were.  :-)
>>>
>>> Gaah... I've got a pile of tests in place for exactly this! Give me a
>>> bit and I'll try to reproduce.
>>
>> Lars, would you give this a shot? I should only have been messing with
>> encoding for group names that were coming from symbols.
>
> This may not be the full solution (though I think it is), but it's
> definitely a necessary part. I'm going to push this first so more people
> don't end up with corrupted .newsrc.eld files, and then see where we're at.

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.

    AndyM






  reply	other threads:[~2019-04-18 17:43 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 [this message]
2019-04-18 19:48         ` Eric Abrahamsen
2019-04-18 20:42           ` Andy Moreton
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=vz1o9535hus.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).