From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: wjenkner@inode.at, 16722@debbugs.gnu.org
Subject: bug#16722: 24.3.50; `M-x man' does not handle case appropriately
Date: Fri, 25 Sep 2020 14:29:51 +0300 [thread overview]
Message-ID: <83sgb6rt5c.fsf@gnu.org> (raw)
In-Reply-To: <873636rwbw.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 25 Sep 2020 12:21:07 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Wolfgang Jenkner <wjenkner@inode.at>, 16722@debbugs.gnu.org
> Date: Fri, 25 Sep 2020 12:21:07 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> But `man -k' always works (to the extent we need it to) if the whatis
> >> database is correctly installed.
> >
> > No, it doesn't. For example, it isn't supported with this clone:
> >
> > http://sourceforge.net/projects/ezwinports/files/man-1.4-bin.zip/download
> >
> > And, as demonstrated in this bug report, it can backfire when the
> > database is not "correctly installed".
>
> npostavs@users.sourceforge.net writes:
>
> > I can't reproduce the problem here, as my cygwin's man -k prints only to
> > stderr in this case. Does checking exit status help?
>
> [...]
>
> > - (setq table (Man-parse-man-k)))
> > + (when (eq 0
> > + (ignore-errors
> > + (call-process
> > + manual-program nil '(t nil) nil
> > + "-k" (concat (when (or Man-man-k-use-anchor
> > + (string-equal prefix ""))
> > + "^")
> > + prefix))))
> > + (setq table (Man-parse-man-k)))))
>
> There was no followup on this patch, and I don't have a Windows system
> to test with. Eli, would this patch fix the problem both with the
> uninstalled whereis database and the ezwinports version of man?
I can only test the ezwinports case: the code proposed by Noam will
cause that 'man' to return a non-zero exit status, so it sounds like
an okay solution for ezwinports.
The use case with uninstalled whatis database you could probably test
on your system, by moving the database aside or renaming it?
Thanks.
next prev parent reply other threads:[~2020-09-25 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 14:45 bug#16722: 24.3.50; `M-x man' does not handle case appropriately Drew Adams
2014-02-15 17:17 ` Wolfgang Jenkner
2014-02-15 19:55 ` Drew Adams
2014-02-16 0:28 ` Wolfgang Jenkner
2014-02-16 3:04 ` Drew Adams
2014-02-15 20:54 ` Eli Zaretskii
2014-02-16 1:08 ` Wolfgang Jenkner
2014-02-16 3:50 ` Eli Zaretskii
2014-02-16 14:17 ` Wolfgang Jenkner
2017-02-01 19:25 ` Drew Adams
2017-02-01 19:50 ` Eli Zaretskii
2017-02-02 1:08 ` npostavs
2020-09-25 10:21 ` Lars Ingebrigtsen
2020-09-25 11:29 ` Eli Zaretskii [this message]
2020-09-25 11:36 ` Lars Ingebrigtsen
[not found] <<bc83b9db-228c-4eb1-893a-9672bb376a4f@default>
[not found] ` <<85fvnkwarc.fsf@iznogoud.viz>
[not found] ` <<834n40ayg4.fsf@gnu.org>
[not found] ` <<858utbkgof.fsf@iznogoud.viz>
[not found] ` <<831tz3btr8.fsf@gnu.org>
[not found] ` <<85ob27ywed.fsf@iznogoud.viz>
[not found] ` <<c7667a78-58ba-4e9a-8eb9-c86727395b79@default>
[not found] ` <<831svhwv0z.fsf@gnu.org>
2017-02-01 22:36 ` 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
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=83sgb6rt5c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16722@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=wjenkner@inode.at \
/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).