From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: storm@cua.dk (Kim F. Storm),
rms@gnu.org, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Apropos commands and regexps
Date: Fri, 17 May 2002 14:01:49 +0200 [thread overview]
Message-ID: <vafr8kbyocy.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87sn4rdabb.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "17 May 2002 06:58:32 +0900")
Miles Bader <miles@gnu.org> writes:
> `or' is clearly wrong; even in emacs' `limited' universe, it generates
> way too many hits.
>
> E.g., (apropos "\\(find.*file\\|file.*find\\)") gets about 50 hits,
> whereas (apropos "\\(find\\|file\\)") gets over 700!
>
> Maybe your idea of `at least N matches' is a good compromise.
Information Retrieval research has shown that weighting and ranking is
what's needed. Just list the "good" matches first. With Boolean
searches, people need to issue a lot of queries to select an
appropriate answer set. If you have ranking, fewer queries will be
sufficient.
But it might be useful to somehow indicate to the user the nature of
each match so that the user can decide what they want. For example:
this group of matches contains all words, the following group of
matches misses the word foo, ...
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-05-17 12:01 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
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 [this message]
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
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=vafr8kbyocy.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).