From: Reuben Thomas <rrt@sc3d.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27833@debbugs.gnu.org
Subject: bug#27833: 25.2; Add support for manpath command to woman.el
Date: Wed, 26 Jul 2017 15:33:52 +0100 [thread overview]
Message-ID: <CAOnWdog8TfVbNG5Bk6sDWbAxQJbj5EjSzrQHwkcEtUozBdXv-A@mail.gmail.com> (raw)
In-Reply-To: <83shhj5l6r.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
On 26 July 2017 at 15:26, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Reuben Thomas <rrt@sc3d.org>
> > Date: Tue, 25 Jul 2017 23:41:03 +0100
> >
> > The attached patch against git master adds support for the man-db
> > manpath command to woman.el.
> >
> > For now, this can actually be better than using man, as man -k/apropos
> > does not currently support man directories lacking a database or whatis
> > file, which is typical for directories derived from PATH.
>
> Could you please provide a rationale for this addition?
>
> It sounds strange to me to enhance woman.el, whose main purpose is to
> work without ("wo") 'man', including on systems where 'man' is not
> easily available, by making it run 'manpath'. If something is wrong
> with woman-manpath's built-in database, why cannot we extend it by
> adding potential candidates to those already existing there?
>
You're right about woman being designed to run without man, I hadn't
thought of that.
There's nothing wrong with woman-manpath's built-in database. The idea is
simply to use "manpath"'s extra functionality, which looks for man pages in
directories formed from the directories on PATH.
I guess the logical thing to do would therefore be to replicate this
functionality directly, but I don't propose to do it.
> On top of that, I think we semi-deprecated woman.el because AFAIR it
> cannot support newer roff features which are abundant in recent man
> pages. So I wonder what kind of use case do you have that on the one
> hand needs woman.el, and OTOH finds its manpath emulation lacking.
>
I explained that: man -k does not support man directories lacking a
database.
I've fixed that for my own purposes by running "mandb" as a per-user
cronjob, so I suggest you can ignore this patch (which I agree is
ill-conceived), and close the bug report.
Thanks as always for your penetrating analysis.
--
https://rrt.sc3d.org <http://rrt.sc3d.org>
[-- Attachment #2: Type: text/html, Size: 3422 bytes --]
next prev parent reply other threads:[~2017-07-26 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 22:41 bug#27833: 25.2; Add support for manpath command to woman.el Reuben Thomas
2017-07-25 23:40 ` Mark Oteiza
2017-07-26 8:43 ` Reuben Thomas
2017-07-26 14:26 ` Eli Zaretskii
2017-07-26 14:33 ` Reuben Thomas [this message]
2017-07-26 15:17 ` Eli Zaretskii
2017-07-26 16:29 ` Reuben Thomas
2019-09-29 2:03 ` Stefan Kangas
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=CAOnWdog8TfVbNG5Bk6sDWbAxQJbj5EjSzrQHwkcEtUozBdXv-A@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=27833@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 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.