From: jao via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 71439@debbugs.gnu.org
Subject: bug#71439: Acknowledgement (30.0.50; gnus-summary-refer-thread doesn't work)
Date: Mon, 16 Sep 2024 19:43:05 +0000 [thread overview]
Message-ID: <87jzfbbd17.fsf@mail.jao.io> (raw)
In-Reply-To: <handler.71439.B.17178628967567.ack@debbugs.gnu.org>
Hi,
I've finally tracked down this problem to my use of a bespoke search
engine based on the 'recoll' indexer. gnus-summary-refer-thread
uses the search functionality of the configured engine, and mine wasn't
handling correctly serches for a "thread".
So, this is not a bug and can be closed. Sorry for the noise.
Cheers,
jao
--
"People sometimes ask me if it is a sin in the Church of Emacs to use vi.
Using a free version of vi is not a sin; it's a penance".
-Richard Stallman
next prev parent reply other threads:[~2024-09-16 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 16:07 bug#71439: 30.0.50; gnus-summary-refer-thread doesn't work Jose A. Ortega Ruiz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 16:26 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 17:16 ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 21:30 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 22:12 ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09 0:31 ` Jose A. Ortega Ruiz
[not found] ` <handler.71439.B.17178628967567.ack@debbugs.gnu.org>
2024-06-08 16:30 ` bug#71439: Acknowledgement (30.0.50; gnus-summary-refer-thread doesn't work) jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-16 19:43 ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-17 11:40 ` Eli Zaretskii
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=87jzfbbd17.fsf@mail.jao.io \
--to=bug-gnu-emacs@gnu.org \
--cc=71439@debbugs.gnu.org \
--cc=mail@jao.io \
/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.