unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: new apropos feature in Emacs-22
Date: Fri, 11 Nov 2005 02:42:55 -0500	[thread overview]
Message-ID: <E1EaTYl-0001fa-4R@fencepost.gnu.org> (raw)
In-Reply-To: <200511080458.jA84wXB17185@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 7 Nov 2005 22:58:33 -0600 (CST))

    I believe that (emacs)Apropos should _explicitly_ warn that, if one
    wants to search by keywords, keywords should not contain regexp special
    characters and warn in particular that filenames containing dots can
    normally not be used as keywords.

I will do that.

				       As people will sometimes _want_ to
    use things like .emacs, .mailrc or .XDefaults as keywords, especially
    for apropos-documentation, some escape convention should be provided.
    Why not use my original proposal: final unquoted `[' (or final single
    `\') is ignored and means that the input is unconditionally a list of
    keywords, for this specialized (but real) need?

I don't think this will be very useful, because the people it is most
aimed at are beginners and they are unlikely to remember that this
is available.

The only think I can think of that would help beginners with such
inputs would be to detect such cases and ask the user "Did you mean
this as a regexp or as a list of keywords?"  That question would
help people without requiring them to remember in advance that the
two options exist.

I have not looked at the program callers of the apropos commands.
If this is likely to break them, maybe we should not do it.
Otherwise, would you like to do it?

  parent reply	other threads:[~2005-11-11  7:42 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05  3:15 new apropos feature in Emacs-22 Luc Teirlinck
2005-11-05 10:26 ` Eli Zaretskii
2005-11-05 15:52   ` Luc Teirlinck
2005-11-05 16:43     ` Eli Zaretskii
2005-11-05 17:33       ` Drew Adams
2005-11-05 19:46         ` Eli Zaretskii
2005-11-05 20:38           ` Drew Adams
2005-11-05 22:10             ` Luc Teirlinck
2005-11-05 23:00             ` Kim F. Storm
2005-11-05 23:18               ` Lennart Borgman
2005-11-05 23:28                 ` Luc Teirlinck
2005-11-05 23:37                   ` Lennart Borgman
2005-11-05 23:31                 ` Drew Adams
2005-11-05 23:36                   ` Drew Adams
2005-11-05 23:39                   ` Lennart Borgman
2005-11-05 23:21               ` Drew Adams
2005-11-06  1:57               ` Luc Teirlinck
2005-11-06  4:32                 ` Eli Zaretskii
2005-11-06  5:36                   ` Luc Teirlinck
2005-11-06 17:05                     ` Eli Zaretskii
2005-11-06 17:22                       ` David Kastrup
2005-11-06 18:43                         ` Eli Zaretskii
2005-11-06 18:31                       ` Luc Teirlinck
2005-11-06 18:46                         ` Eli Zaretskii
2005-11-07  9:45                           ` Alan Mackenzie
2005-11-07 20:43                             ` Eli Zaretskii
2005-11-07 20:58                             ` Eli Zaretskii
2005-11-07 21:54                         ` Richard M. Stallman
2005-11-06 20:16                       ` Luc Teirlinck
2005-11-06 22:54                         ` Kim F. Storm
2005-11-06 18:47                     ` Kim F. Storm
2005-11-06 19:19                       ` Luc Teirlinck
2005-11-07  7:04                       ` Luc Teirlinck
2005-11-07 21:55                       ` Richard M. Stallman
2005-11-06  9:19                   ` David Kastrup
2005-11-05 17:39       ` Luc Teirlinck
2005-11-06 17:02     ` Stefan Monnier
2005-11-06 17:08       ` Eli Zaretskii
2005-11-06 19:55       ` Luc Teirlinck
2005-11-05 23:43 ` Richard M. Stallman
2005-11-06  0:27   ` Luc Teirlinck
2005-11-07 15:34     ` Richard M. Stallman
2005-11-07 17:54       ` Drew Adams
2005-11-07 18:56         ` Stefan Monnier
2005-11-07 19:25           ` Drew Adams
2005-11-07 22:39           ` Lennart Borgman
2005-11-07 20:52         ` Eli Zaretskii
2005-11-07 22:59           ` Drew Adams
2005-11-08  4:47             ` Eli Zaretskii
2005-11-08  4:58       ` Luc Teirlinck
2005-11-08 12:48         ` Kim F. Storm
2005-11-08 23:53           ` Miles Bader
2005-11-09  0:21             ` Lennart Borgman
2005-11-11  7:42         ` Richard M. Stallman [this message]
2005-11-11  9:29           ` Kim F. Storm
2005-11-11 10:57             ` Miles Bader
2005-11-11 16:16               ` Kim F. Storm
2005-11-12  3:38               ` Richard M. Stallman
2005-11-12  3:15           ` Luc Teirlinck
2005-11-12 17:49             ` Richard M. Stallman
2005-11-12  3:36           ` Luc Teirlinck
2005-11-12 21:19             ` Juri Linkov
2005-11-14  4:55               ` Richard M. Stallman
2005-11-15  0:52                 ` Juri Linkov
2005-11-15 23:22                   ` Richard M. Stallman
2005-11-17  7:38                     ` Juri Linkov
2005-11-17 10:06                       ` Kim F. Storm
2005-11-09 23:25       ` Kim F. Storm
2005-11-10  5:44         ` Richard M. Stallman

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=E1EaTYl-0001fa-4R@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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 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).