From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 08:58:40 -0700 (PDT) [thread overview]
Message-ID: <42fbb21a-e7f6-4e15-b609-662c58093b5c@default> (raw)
In-Reply-To: <<83efh92wr2.fsf@gnu.org>>
> > > > Did you present the same, we-can't-enhance-because-legacy
> > > > argument when Kim (I think it was) added keyword-matching
> > > > to the `apropos*' commands?
> > >
> > > That change was backward-compatible.
> >
> > No more so than this one, IMO. In fact less.
>
> I don't agree, but even if you are right, you can consider my views
> today the result of learning over all those years since then what such
> changes mean.
When I get some time I will test and update the code I sent.
You can then do what you will with it (e.g. rename or recode).
Thx.
next parent reply other threads:[~2018-06-14 15:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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 ` bug#31807: 27.0; `info-apropos' bad name or bad matching 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
2018-06-12 23:01 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
2018-06-14 14:11 ` Drew Adams
2018-06-14 14:28 ` Eli Zaretskii
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=42fbb21a-e7f6-4e15-b609-662c58093b5c@default \
--to=drew.adams@oracle.com \
--cc=31807@debbugs.gnu.org \
--cc=eliz@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).