From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 75305@debbugs.gnu.org
Subject: bug#75305: 31.0.50; gnus-refer-thread-use-search isn't exact enough about how the current group is searched
Date: Fri, 03 Jan 2025 10:16:50 +0200 [thread overview]
Message-ID: <8634i0ia6l.fsf@gnu.org> (raw)
In-Reply-To: <87wmfclrf0.fsf@> (bug-gnu-emacs@gnu.org)
> Date: Fri, 03 Jan 2025 01:36:19 +0200
> From: Björn Bidar via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
>
> I noticed that as intended without adding the current group to the
> variable in addition to the current group.
> The manual states what happens what the variable does when set however I
> think the description is not exact enough.
>
> It is very easy to overlook that to add the current group in addition
> other groups it has to be added too.
Can you suggest the additions to the manual?
Thanks.
next parent reply other threads:[~2025-01-03 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wmfclrf0.fsf@>
2025-01-03 8:16 ` Eli Zaretskii [this message]
2025-01-03 20:33 ` bug#75305: 31.0.50; gnus-refer-thread-use-search isn't exact enough about how the current group is searched Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87o70nd4dd.fsf@>
2025-01-04 13:26 ` Eli Zaretskii
2025-01-04 21:34 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87bjwmw9f1.fsf@>
2025-01-05 6:29 ` Eli Zaretskii
2025-01-05 20:33 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87o70lt2yw.fsf@>
2025-01-05 20:36 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 23:36 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8634i0ia6l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75305@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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.