[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:50:09 +0300 |
> Date: Thu, 14 Jun 2018 08:33:32 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 31807@debbugs.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.
- bug#31807: 27.0; `info-apropos' bad name or bad matching, (continued)
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, 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, Drew Adams, 2018/06/14