From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Jose A. Ortega Ruiz" <mail@jao.io>
Cc: 39515@debbugs.gnu.org
Subject: bug#39515: 28.0.50; Gnus, nnir search (G G) on Topic doesn't look at its groups
Date: Mon, 10 Feb 2020 13:16:18 -0800 [thread overview]
Message-ID: <87o8u6jg7x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v9oef9a6.fsf@gnus.jao.io> (Jose A. Ortega Ruiz's message of "Mon, 10 Feb 2020 20:59:05 +0000")
"Jose A. Ortega Ruiz" <mail@jao.io> writes:
> On Mon, Feb 10 2020, Eric Abrahamsen wrote:
>
> [...]
>
>> It would be very easy to pass the ALL argument to
>> `gnus-topic-find-groups' in `gnus-group-make-nnir-group'.
>>
>> It's really a matter of preference, and what users might interpret as
>> "surprising behavior". Maybe we could take a straw poll on gnus.general?
>
> At any rate, if this is the expected behaviour, one should probably
> update the manual, which doesn't mention this. That contributes to the
> surprise, at least in my case.
>
> IMHO, requiring that all groups are permanently visible to be able to
> perform queries is not very practical (90% of my time in gnus is spent
> not doing queries), but of course a poll won't hurt.
Let me raise a quick query on gnus.general and see what people think.
Personally, I also feel it's less surprising to search all the topic's
groups -- it's usually preferable to search more widely than expected,
vs more narrowly than expected. But let's see if anyone has violent
objections.
> I guess another option is simply to make this customizable? Just a flag,
> and a note in the docs, and we can have both options, if it's not too
> complicated.
Meh, I'm sort of against proliferation of options here. But again, let's
see what people think.
prev parent reply other threads:[~2020-02-10 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 20:42 bug#39515: 28.0.50; Gnus, nnir search (G G) on Topic doesn't look at its groups Jose A. Ortega Ruiz
2020-02-10 19:35 ` Eric Abrahamsen
2020-02-10 20:59 ` Jose A. Ortega Ruiz
2020-02-10 21:16 ` 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=87o8u6jg7x.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=39515@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.