From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: Gnus search
Date: Wed, 27 Oct 2010 07:36:42 -0400 [thread overview]
Message-ID: <87vd4n3m0l.fsf@andy.bu.edu> (raw)
In-Reply-To: <m3hbgf1r83.fsf@quimbies.gnus.org>
I am considering significant changes to nnir to improve the searching
experience. I have added gmane searching but this has exposed some
weaknesses in the current interface, so I would like to get some advice
on potential changes.
Currently nnir searches are initiated from the group buffer in one of
two ways:
1. If any groups are process-marked only these groups are searched.
2. If no groups are process marked then all opened servers are
searched. Some search engines (imap) are only capable of searching a
single group at a time so the search is restricted to the group on
the current line. Others (swish, freewais, namazu) can only search
the whole database, so that's what they do.
With only one search engine available (as has been the case for me
forever) I never noticed this, and assumed that nnir was just searching
the group on the current line. But I now have both imap and gmane
searching available, and without process-marking groups all searches now
search both backends. This is usually not what I want.
So---how about changing the behavior in case 2:
2. If no groups are process-marked search only the group on the current
line (using the appropriate backend).
and possibly adding
3. If no groups are process-marked and no group is on the current line,
search all opened servers (which might take awhile). The user can put
point on the last line of the group buffer for example.
This last addition might not be a great idea, and its only relevant if
anyone continues to use the relevant search engines. So is anyone using:
swish
wais
hyrex
namazu
Can any of these be removed?
Regards,
Andy
next prev parent reply other threads:[~2010-10-27 11:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 15:49 Lars Magne Ingebrigtsen
2010-10-21 16:04 ` Julien Danjou
2010-10-21 16:07 ` Lars Magne Ingebrigtsen
2010-10-21 16:24 ` Julien Danjou
2010-10-21 17:09 ` Andrew Cohen
2010-10-21 17:10 ` Tibor Simko
2010-10-21 17:12 ` Lars Magne Ingebrigtsen
2010-10-21 17:56 ` Andrew Cohen
2010-10-21 18:25 ` Andrew Cohen
2010-10-21 18:45 ` Ted Zlatanov
2010-10-21 19:00 ` Andrew Cohen
2010-10-22 14:24 ` Andrew Cohen
2010-10-23 7:01 ` Steinar Bang
2010-10-23 12:14 ` Andrew Cohen
2010-10-24 9:15 ` Steinar Bang
2010-10-25 18:34 ` Ted Zlatanov
2010-10-24 4:18 ` Lars Magne Ingebrigtsen
2010-10-21 18:00 ` Ted Zlatanov
2010-10-21 18:35 ` Andreas Seltenreich
2010-10-21 21:27 ` Steinar Bang
2010-10-27 11:36 ` Andrew Cohen [this message]
2010-10-27 12:32 ` Steinar Bang
2010-10-27 13:23 ` Dan Christensen
2010-10-27 13:25 ` Andrew Cohen
2010-10-27 17:41 ` Ted Zlatanov
2010-10-27 18:08 ` Andrew Cohen
2010-10-27 18:39 ` Ted Zlatanov
2010-10-28 10:27 ` Julien Danjou
2010-10-28 10:49 ` Andrew Cohen
2010-10-28 10:51 ` Julien Danjou
2010-10-29 6:34 ` nnir: Removing some search engines (was: Gnus search) Reiner Steib
2010-10-29 11:16 ` nnir: Removing some search engines Andrew Cohen
2010-10-29 12:57 ` Jose A. Ortega Ruiz
2010-10-27 20:15 ` Gnus search Jose A. Ortega Ruiz
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=87vd4n3m0l.fsf@andy.bu.edu \
--to=cohen@andy.bu.edu \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).