All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Watson <cjwatson@debian.org>
To: groff@gnu.org, linux-man@vger.kernel.org
Subject: Re: grof --run
Date: Mon, 5 May 2025 11:50:10 +0100	[thread overview]
Message-ID: <aBiX4joChgpehn0B@riva.ucam.org> (raw)
In-Reply-To: <20250503004917.6hg6ymsdfnnn4o7v@illithid>

On Fri, May 02, 2025 at 07:49:17PM -0500, G. Branden Robinson wrote:
>In my shell startup files, I make sure to update $MANPATH any time I
>update $PATH.
>
>This is not a common piece of cargo that Unix newcomers acquire;
>historically, I suppose a lot of man(1) implementations didn't support
>$MANPATH, but man-db has for decades, and I see mandoc(1) does too.

FWIW, with man-db, it's usually best for most people not to set MANPATH 
at all unless manual pages are somewhere that can't be straightforwardly 
derived from PATH.  man-db will normally work it out based on PATH, and 
that way it's harder for them to get out of sync.

-- 
Colin Watson (he/him)                              [cjwatson@debian.org]

  parent reply	other threads:[~2025-05-05 10:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 10:56 Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 12:01 ` G. Branden Robinson
2025-05-02 12:26   ` grof --run Alejandro Colomar
2025-05-02 14:19     ` G. Branden Robinson
2025-05-02 14:59       ` Alejandro Colomar
2025-05-03  0:49         ` G. Branden Robinson
2025-05-03  7:25           ` Alejandro Colomar
2025-05-05 10:50           ` Colin Watson [this message]
2025-05-05 15:41             ` Ingo Schwarze
2025-05-07 18:10               ` G. Branden Robinson
2025-05-02 12:42   ` Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 14:29     ` G. Branden Robinson
2025-05-02 15:30       ` Alejandro Colomar
2025-05-02 13:06   ` Martin Lemaire
2025-05-02 14:51     ` G. Branden Robinson
2025-05-02 15:34       ` Alejandro Colomar
2025-05-03  1:30         ` G. Branden Robinson
2025-05-02 17:42     ` Dave Kemper
2025-05-02 18:46       ` Martin Lemaire
2025-05-03  0:14         ` G. Branden Robinson
2025-05-05 16:00           ` Joey Hess
2025-06-02  6:49             ` on "bricktext" (was: Paragraphs formatted differently depending on previous ones) G. Branden Robinson
2025-06-02  7:16               ` on "bricktext" James Cloos

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=aBiX4joChgpehn0B@riva.ucam.org \
    --to=cjwatson@debian.org \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.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.
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.