all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 17:29:19 +0100	[thread overview]
Message-ID: <CAOnWdohRwezNYRDxmDHkxmJgEaZvFr_ds9-FLY3dbPjbGe1uiQ@mail.gmail.com> (raw)
In-Reply-To: <83d18n5itg.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

On 26 Jul 2017 4:17 pm, "Eli Zaretskii" <eliz@gnu.org> wrote:

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Wed, 26 Jul 2017 15:33:52 +0100
> Cc: 27833@debbugs.gnu.org
>
>  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.

Yes, but why not extend man.el by using manpath?  Is there a problem
that I don't see?


It would take more work, as man.el does not replicate the path
configuration as woman.el does, but relies on man -k. Furthermore, man-db
upstream is now aware of the problem and intends to fix it.

[-- Attachment #2: Type: text/html, Size: 1404 bytes --]

  reply	other threads:[~2017-07-26 16:29 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
2017-07-26 15:17     ` Eli Zaretskii
2017-07-26 16:29       ` Reuben Thomas [this message]
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=CAOnWdohRwezNYRDxmDHkxmJgEaZvFr_ds9-FLY3dbPjbGe1uiQ@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.