From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 49926@debbugs.gnu.org
Cc: jan@stranik.org
Subject: bug#49926: [PATCH] Fix NNIMAP search command in the gnus
Date: Sat, 07 Aug 2021 16:06:08 -0700 [thread overview]
Message-ID: <87tuk097of.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <20210807045230.23998-1-jan@stranik.org> (Jan Stranik via's message of "Sat, 7 Aug 2021 00:52:30 -0400")
Jan Stranik via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> In the version 27.2 of emacs, the nnimap search commands stopped
> working in gnus.
>
> Good example is a command AT to find a referred
> thread in the summary buffer. The observed behaviour was that the
> search command returned no error.
>
> The problem turned out to be in the way how imap query is sent to the
> server. The function nnimap-make-thread-query used a format function
> with foramt specifier %S. For string values with formatting the string
> returned is in the format #("string" ....). The result was tha the
> query sent to the server looked like:
> 23:52:00 [stranik.org] 1980 UID SEARCH (OR HEADER REFERENCES #("<87pmurac3u.fsf@stranik.org>" 0 28 (ws-butler-chg chg)) HEADER Message-Id #("<87pmurac3u.fsf@stranik.org>" 0 28 (ws-butler-chg chg)))
>
> which is an invalid query.
>
> The change formats the string with %s specifier which discards text
> properties.
But that also removes the quoting around the message ids -- are we sure
that's still valid?
next prev parent reply other threads:[~2021-08-07 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 4:52 bug#49926: [PATCH] Fix NNIMAP search command in the gnus Jan Stranik via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-07 23:06 ` Eric Abrahamsen [this message]
[not found] ` <8735rjeqo5.fsf@stranik.org>
2021-08-08 19:26 ` Eric Abrahamsen
2021-11-06 2:39 ` Lars Ingebrigtsen
2021-11-06 14:55 ` Eric Abrahamsen
2021-11-06 18:26 ` Lars Ingebrigtsen
2021-11-06 19:14 ` 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=87tuk097of.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=49926@debbugs.gnu.org \
--cc=jan@stranik.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 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.