all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Łukasz Stelmach" <stlman@poczta.fm>
Cc: Debbugs control <control@debbugs.gnu.org>, 41511@debbugs.gnu.org
Subject: bug#41511: [PATCH v2] Decode group name before matching against gnus-parameters
Date: Mon, 25 May 2020 07:43:08 -0700	[thread overview]
Message-ID: <87mu5wt6rn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <875zck4gn0.fsf%stlman@poczta.fm> ("Łukasz Stelmach"'s message of "Mon, 25 May 2020 09:29:07 +0200")

close 41511
thanks

Łukasz Stelmach <stlman@poczta.fm> writes:

> 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.

Good news! You had me very worried for a second there :)





      reply	other threads:[~2020-05-25 14:43 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
2020-05-25 14:43       ` Eric Abrahamsen [this message]

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=87mu5wt6rn.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=41511@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=stlman@poczta.fm \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.