From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31807@debbugs.gnu.org
Subject: bug#31807: 27.0; `info-apropos' bad name or bad matching
Date: Thu, 14 Jun 2018 16:27:04 +0300 [thread overview]
Message-ID: <83o9gd33dj.fsf@gnu.org> (raw)
In-Reply-To: <78156de2-86c8-4593-92b5-59edf7a8996e@default> (message from Drew Adams on Tue, 12 Jun 2018 16:01:37 -0700 (PDT))
> Date: Tue, 12 Jun 2018 16:01:37 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> `info-apropos', as its doc string says, apparently does NOT do "apropos"
> matching, i.e., regexp and keyword matching. It apparently does literal
> string matching against index entries in all of the manuals.
>
> Perhaps either the name should be changed (to not use the word
> "apropos") or the behavior should be changed, to allow apropos matching.
This command is the Emacs implementation of the "info --apropos"
feature present in the Texinfo's stand-alone Info reader, which also
looks for substring matches. Apparently, "apropos" doesn't
necessarily mean "regexps and keywords".
> I threw this together quickly, as a POC. It does the job, but
Thanks. The original command was introduced 11 years ago, so I don't
think we can make radical changes in the user-visible behavior by
default after all this time. This should be an opt-in optional
behavior, controlled either by a prefix argument or by a (new) user
variable. Would you like to modify your suggestion along these lines?
Btw, does this really work as intended without changes to
Info-apropos-matches? That function calls regexp-quote on its
argument.
> BTW, should the name be `Info-apropos' or `info-apropos'?
We've been through that, see the reason explained here:
http://lists.gnu.org/archive/html/emacs-devel/2017-11/msg00482.html
next prev parent reply other threads:[~2018-06-14 13:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 23:01 bug#31807: 27.0; `info-apropos' bad name or bad matching Drew Adams
2018-06-12 23:21 ` Drew Adams
2018-06-12 23:39 ` Drew Adams
2018-06-12 23:59 ` Drew Adams
2018-06-14 13:29 ` Eli Zaretskii
2018-06-13 0:04 ` Noam Postavsky
2018-06-13 0:16 ` Drew Adams
2018-06-13 18:24 ` Drew Adams
[not found] ` <<eb245b09-a156-4585-8021-7a3e0e173dbc@default>
[not found] ` <<83muvx33ab.fsf@gnu.org>
2018-06-14 14:16 ` Drew Adams
2018-06-17 7:44 ` Eli Zaretskii
[not found] ` <<<eb245b09-a156-4585-8021-7a3e0e173dbc@default>
[not found] ` <<<83muvx33ab.fsf@gnu.org>
[not found] ` <<f7814f7b-d9c0-48d5-83aa-b354b047db10@default>
[not found] ` <<83muvtuab9.fsf@gnu.org>
2018-06-17 14:26 ` Drew Adams
2018-06-14 13:27 ` Eli Zaretskii [this message]
2018-06-14 14:11 ` Drew Adams
2018-06-14 14:28 ` Eli Zaretskii
[not found] <<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<83o9gd33dj.fsf@gnu.org>
[not found] ` <<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<83in6l30ir.fsf@gnu.org>
2018-06-14 14:42 ` Drew Adams
2018-06-14 15:09 ` Eli Zaretskii
2018-06-14 20:45 ` Drew Adams
2022-04-21 15:05 ` Lars Ingebrigtsen
2022-04-21 20:04 ` Drew Adams
[not found] <<<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<<83o9gd33dj.fsf@gnu.org>
[not found] ` <<<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<<83in6l30ir.fsf@gnu.org>
[not found] ` <<5fc07c84-b8d2-493c-a17b-774ad1c213bf@default>
[not found] ` <<83fu1p2ym7.fsf@gnu.org>
2018-06-14 15:33 ` Drew Adams
2018-06-14 15:50 ` Eli Zaretskii
[not found] <<<<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<<<83o9gd33dj.fsf@gnu.org>
[not found] ` <<<<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<<<83in6l30ir.fsf@gnu.org>
[not found] ` <<<5fc07c84-b8d2-493c-a17b-774ad1c213bf@default>
[not found] ` <<<83fu1p2ym7.fsf@gnu.org>
[not found] ` <<73c2c21d-9fba-4ab5-a0b0-8b36e9a23bcf@default>
[not found] ` <<83efh92wr2.fsf@gnu.org>
2018-06-14 15:58 ` Drew Adams
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=83o9gd33dj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31807@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.