[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31807: 27.0; `info-apropos' bad name or bad matching
From: |
Eli Zaretskii |
Subject: |
bug#31807: 27.0; `info-apropos' bad name or bad matching |
Date: |
Thu, 14 Jun 2018 18:09:52 +0300 |
> Date: Thu, 14 Jun 2018 07:42:11 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 31807@debbugs.gnu.org
>
> I seriously doubt that anyone will be upset if `info-apropos'
> is enhanced to support more general matching.
When in doubt, we should err on the safe side in these situations.
> 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.
bug#31807: 27.0; `info-apropos' bad name or bad matching, Eli Zaretskii, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Drew Adams, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Eli Zaretskii, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Drew Adams, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching,
Eli Zaretskii <=
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Drew Adams, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Eli Zaretskii, 2018/06/14
- bug#31807: 27.0; `info-apropos' bad name or bad matching, Drew Adams, 2018/06/14
bug#31807: 27.0; `info-apropos' bad name or bad matching, Drew Adams, 2018/06/14