unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 27833@debbugs.gnu.org
Subject: bug#27833: 25.2; Add support for manpath command to woman.el
Date: Wed, 26 Jul 2017 17:26:04 +0300	[thread overview]
Message-ID: <83shhj5l6r.fsf@gnu.org> (raw)
In-Reply-To: <871sp4xhq8.fsf@sc3d.org> (message from Reuben Thomas on Tue, 25 Jul 2017 23:41:03 +0100)

> 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?

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.





  parent reply	other threads:[~2017-07-26 14:26 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 [this message]
2017-07-26 14:33   ` Reuben Thomas
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

  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=83shhj5l6r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27833@debbugs.gnu.org \
    --cc=rrt@sc3d.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).