From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Apropos commands and regexps
Date: 17 May 2002 00:26:43 +0200 [thread overview]
Message-ID: <5xg00r4tlo.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <buoy9ekubkz.fsf@mcspd15.ucom.lsi.nec.co.jp>
Miles Bader <miles@lsi.nec.co.jp> writes:
> storm@cua.dk (Kim F. Storm) writes:
> > I don't like the "and" approach -- at least not as the default.
> > (see my previous posting for the rationale).
>
> `and' is the defautl for all search engines that I've used, and has the
> advantage of being simple and easy to understand.
A quick test shows that Google, Yahoo, Lycos uses AND
while Altavista, Excite, AskJeeves uses OR.
That's 50/50...
For WEB search engines, I think AND does make sense -- since there
are SOOOO many pages to match. But for a limited universe like
emacs -- which doesn't always use the most obvious terms --
using AND doesn't make a lot of sense to me.
>
> Perhaps your idea of `2 or more' would work better in practice, but
> it's hard to say without some real experience.
I think it is adequate in practice.
>
> > Comparing to WEB search engines, I don't think that separating
> > keywords with commas is common practice...
>
> No, but it's common practice in writing lists.
I don't see the relevance, sorry. But of course, we could ignore
commas in case people use them...
>
> > Consider searching for "grep" -- shouldn't that return "igrep" ?
>
> Good point; I guess maybe it shouldn't do any anchoring at all (bit
> annoying, that, since I often get lots of false hits when my apropos
> term unexpectedly happens to occur in the middle of a common english
> word...).
We could put a "button bar" at the top of the apropos output with
the following buttons:
[Match all words] [anchored match] [search documentation]
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-05-16 22:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 0:57 Apropos commands and regexps Kim F. Storm
2002-05-12 5:28 ` Eli Zaretskii
2002-05-12 5:38 ` Eli Zaretskii
2002-05-13 1:40 ` Miles Bader
2002-05-13 19:18 ` Kim F. Storm
2002-05-14 5:55 ` Miles Bader
2002-05-13 19:11 ` Kim F. Storm
2002-05-14 5:38 ` Miles Bader
2002-05-15 7:00 ` Richard Stallman
2002-05-15 11:23 ` Miles Bader
2002-05-15 21:59 ` Kim F. Storm
2002-05-16 1:26 ` Miles Bader
2002-05-16 22:26 ` Kim F. Storm [this message]
2002-05-16 21:38 ` Stefan Monnier
2002-05-17 11:59 ` Kai Großjohann
2002-05-18 18:48 ` Richard Stallman
2002-05-18 22:24 ` Stefan Monnier
2002-05-19 12:02 ` Kai Großjohann
2002-05-19 14:50 ` Eli Zaretskii
2002-05-19 15:23 ` Kai Großjohann
2002-05-19 19:40 ` Richard Stallman
2002-05-19 23:33 ` Kim F. Storm
2002-05-20 9:50 ` Alex Schroeder
2002-05-16 21:58 ` Miles Bader
2002-05-17 12:01 ` Kai Großjohann
2002-05-17 21:56 ` Kim F. Storm
2002-05-18 6:31 ` Eli Zaretskii
2002-05-18 22:47 ` Stefan Monnier
2002-05-17 6:15 ` Eli Zaretskii
2002-05-17 11:58 ` Kai Großjohann
2002-05-16 4:54 ` Eli Zaretskii
2002-05-16 22:10 ` Kim F. Storm
2002-05-16 21:20 ` Miles Bader
2002-05-17 6:13 ` Eli Zaretskii
2002-05-18 18:49 ` Richard Stallman
2002-05-19 4:51 ` Eli Zaretskii
2002-05-19 19:40 ` Richard Stallman
2002-05-19 23:29 ` Kim F. Storm
2002-05-20 3:31 ` Eli Zaretskii
2002-05-16 20:24 ` Richard Stallman
2002-05-15 21:55 ` Kim F. Storm
2002-05-16 4:52 ` Eli Zaretskii
[not found] ` <5xbsbf4thx.fsf@kfs2.cua.dk>
2002-05-17 6:22 ` Eli Zaretskii
2002-05-12 10:06 ` Kai Großjohann
2002-05-12 17:03 ` Alex Schroeder
2002-05-13 19:26 ` Kim F. Storm
2002-05-14 5:26 ` Miles Bader
2002-05-16 11:04 ` Kai Großjohann
2002-05-16 12:30 ` Eli Zaretskii
2002-05-16 13:05 ` D. Goel
2002-05-16 22:37 ` Alex Schroeder
2002-05-16 22:44 ` Kim F. Storm
2002-05-17 19:28 ` Richard Stallman
2002-05-18 6:26 ` Eli Zaretskii
2002-05-19 5:30 ` Richard Stallman
2002-05-23 21:41 ` Kim F. Storm
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=5xg00r4tlo.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
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.