From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Vegard Vesterheim <vegard.vesterheim@uninett.no>
Subject: Re: Searching in Gnus: gnus-group-make-nnir-group does not recurse into subtopics
Date: Fri, 27 Sep 2019 17:02:28 -0700 [thread overview]
Message-ID: <87wodtnv8r.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878sq9li1y.fsf@bobnewell.net> (Bob Newell's message of "Fri, 27 Sep 2019 08:18:01 -1000")
Bob Newell <bobnewell@bobnewell.net> writes:
>>>>> "When I initiate a search (gnus-group-make-nnir-group) with the
>>>>> cursor on a topic, only the immediate subtopics are searched,
>>>>> the topic hierarchy is not traversed recursively"
>>>
>>> Ah, there's a simple answer as it turns out. Position the
>>> cursor to the top of the hierarchy of interest (the topic
>>> line). Press # and every visible group in the topic hierarchy
>>> gets marked. A subsequent G G searches all the marked
>>> groups. Remove the marks with M U.
>>
>> Although it does not solve my problem completely, this is a useful
>> tip. Thanks.
>
> Where does it fall short? By the way, with a little more
> experimentation I found that non-visible groups in the
> hierarchy also get (non-visibly) marked and searched, so this
> may actually be much closer to what you wanted.
>
>> The function `gnus-topic-find-groups' looks promising. I did some
>
> I took a lot at that too and had to write a little function to
> parse the output. It returns rather too much information
> including many duplicate group records. And translating the
> de-duped list into a search is a problem I didn't take on,
> once I found out that marking was a better way.
Apparently Lars has put some sort of fix for this into master -- if
anyone's running master, give it a shot.
prev parent reply other threads:[~2019-09-28 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 13:33 Searching in Gnus: gnus-group-make-nnir-group does not recurse into subtopics Vegard Vesterheim
2019-09-26 17:59 ` Bob Newell
2019-09-26 19:34 ` Eric Abrahamsen
2019-09-27 0:22 ` Bob Newell
2019-09-27 6:15 ` Vegard Vesterheim
2019-09-27 18:18 ` Bob Newell
2019-09-28 0:02 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wodtnv8r.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=bobnewell@bobnewell.net \
--cc=help-gnu-emacs@gnu.org \
--cc=vegard.vesterheim@uninett.no \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).