From: "Peter Münster" <pm@a16n.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: problem with non-ascii group-names
Date: Tue, 14 Sep 2021 22:12:00 +0200 [thread overview]
Message-ID: <87o88udii7.fsf@a16n.net> (raw)
In-Reply-To: <87h7iepzor.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 03 Jun 2021 11:31:48 -0700")
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Thu, Jun 03 2021, Eric Abrahamsen wrote:
> 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.
Hello Eric,
Now I use Emacs from git-master. Still the same problem.
Here some details for the group "céline":
- There is this line in ~/Mail/active: "céline 153 1 y"
- Then I reply to a message in this group with "Gcc: céline"
- This appears in the *Messages*:
Sending...
Sending via mail...
Wrote /home/peter/Mail/c\303\251line/154 (2 non-printable characters)
Sending...done
- When entering the group "céline", the new message is hidden.
- There are now 2 lines in the active file:
céline 154 1 y
céline 153 1 y
I guess, that this should be reproducible with any nnml group with
accented characters in the group name.
TIA for any help,
--
Peter
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2021-09-14 20:12 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
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 [this message]
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=87o88udii7.fsf@a16n.net \
--to=pm@a16n.net \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.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).