From: "Łukasz Stelmach" <stlman@poczta.fm>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 41511@debbugs.gnu.org
Subject: bug#41511: [PATCH v2] Decode group name before matching against gnus-parameters
Date: Mon, 25 May 2020 09:29:07 +0200 [thread overview]
Message-ID: <875zck4gn0.fsf%stlman@poczta.fm> (raw)
In-Reply-To: <87blmduh0c.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 24 May 2020 15:04:19 -0700")
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Łukasz Stelmach <stlman@poczta.fm> writes:
>
>> Group names in Gnus are stored and processed as strings of bytes
>> (e.g. "Wiadomo\305\233ci-\305\233mieci") while regular expressions in
>> gnus-parameters are encoded as multibyte strings (e.g. "Wiadomości-śmieci")
>> and matching the latter aginst the former doesn't work. Parameters set
>> for groups with non-ascii characters in their names cannot be retrieved.
>
> Group names in Gnus have been fully decoded strings for six months or
> more -- are you seeing this bug in master?
Shame on me. I created the patch on 26.1, cherry-picked it to master,
tested and assumed it was still needed because it applied without issues
and worked as expected.
This bug can be closed then.
Kind regards,
--
Miłego dnia,
Łukasz Stelmach
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 617 bytes --]
next prev parent reply other threads:[~2020-05-25 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 16:59 bug#41511: [PATCH] Decode group name before matching against gnus-parameters Łukasz Stelmach
2020-05-24 17:16 ` bug#41511: [PATCH v2] " Łukasz Stelmach
2020-05-24 22:04 ` Eric Abrahamsen
2020-05-25 7:29 ` Łukasz Stelmach [this message]
2020-05-25 14:43 ` 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
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=875zck4gn0.fsf%stlman@poczta.fm \
--to=stlman@poczta.fm \
--cc=41511@debbugs.gnu.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.
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).