From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Peter Münster" <pm@a16n.net>
Cc: ding@gnus.org
Subject: Re: problem with non-ascii group-names
Date: Thu, 03 Jun 2021 11:31:48 -0700 [thread overview]
Message-ID: <87h7iepzor.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877djayid0.fsf@a16n.net> ("Peter =?utf-8?Q?M=C3=BCnster=22's?= message of "Thu, 03 Jun 2021 19:21:15 +0200")
Peter Münster <pm@a16n.net> writes:
> On Thu, Jun 03 2021, Eric Abrahamsen wrote:
>
>> Can you tell us your Gnus version?
>
> It's in the headers:
> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
I don't think there will be a whole lot you can do -- in mid-2019 I made
some fairly large changes to Gnus to use decoded group names everywhere,
and in the process fixed several bugs related to non-ascii group name. I
don't think any of that is available in Emacs 27. It's possible if we
found the exact bug that the fix could be added to 27, but I don't even
think there will be any more releases of 27 anyway (?, not sure). Your
best bet may be to wait until Emacs 28 is released.
In the mean time, can you look at the active file for this server and
see how the group name is encoded there?
next prev parent reply other threads:[~2021-06-03 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 10:29 Peter Münster
2021-06-03 16:00 ` Eric Abrahamsen
2021-06-03 17:21 ` Peter Münster
2021-06-03 18:31 ` Eric Abrahamsen [this message]
2021-06-03 18:56 ` Peter Münster
2021-06-03 19:55 ` Eric Abrahamsen
2021-06-03 20:36 ` Peter Münster
2021-06-03 21:02 ` Eric Abrahamsen
2021-09-14 20:12 ` Peter Münster
2021-09-14 20:20 ` Peter Münster
2021-09-20 18:09 ` Eric Abrahamsen
2021-09-20 18:14 ` Eric Abrahamsen
2021-09-20 18:53 ` Eric Abrahamsen
2021-09-20 21:13 ` Peter Münster
2021-09-20 22:34 ` Eric Abrahamsen
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=87h7iepzor.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
--cc=pm@a16n.net \
/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).