public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: g.branden.robinson@gmail.com, linux-man@vger.kernel.org, groff@gnu.org
Subject: Re: man -M tcl (was: All caps .TH page title)
Date: Fri, 29 Jul 2022 15:27:48 +0200	[thread overview]
Message-ID: <0aaf05d3-dc7f-660a-641d-be75d053d3f9@gmail.com> (raw)
In-Reply-To: <YuPfLqJldAA9XP9t@asta-kit.de>


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

On 7/29/22 15:22, Ingo Schwarze wrote:
>> What are your thoughts?
> 
> Yes, even though /usr/local/share/doc/pkgname/man/man* is a bit long,
> it makes more sense than paths like
> 
>    /usr/local/cyrus/man/
>    /usr/local/heirloom-doctools/man/
>    /usr/local/lib/erlang21/man/
>    /usr/local/lib/node_modules/npm/man/
>    /usr/local/lib/stk/4.0.1/man/
>    /usr/local/lib/tcl/tcl8.6/man/
>    /usr/local/plan9/man/
>    /usr/local/share/fish/man/
> 
> Then again, *if* we go the -M alias way, these paths are only
> ever used in the man.conf(5) file.  So where exactly they are
> has no major impact on the user and is more a matter of system
> cleanliness.

Yeah, I do want to have system cleanliness, especially to help 
programmers organizing their file hierarchy know where they should put 
things.

So, let it be </usr/local/share/doc/pkgname/man/man*>.

I'll have a look at the POSIX man pages and see if there's something I 
can do there.

Thanks,

Alex

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-07-29 13:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 14:29 All caps .TH page name Alejandro Colomar
2022-07-21 18:36 ` G. Branden Robinson
2022-07-21 23:16   ` All caps .TH page title Alejandro Colomar
2022-07-22  0:22     ` Colin Watson
2022-07-22  1:34       ` G. Branden Robinson
2022-07-22  4:07         ` G. Branden Robinson
2022-07-22 14:44       ` Ingo Schwarze
2022-07-22  2:14     ` G. Branden Robinson
2022-07-22 10:35       ` Alejandro Colomar (man-pages)
2022-07-22 11:46         ` Alejandro Colomar
2022-07-22 19:03           ` G. Branden Robinson
2022-07-22 22:20             ` Alejandro Colomar
2022-07-23 19:29           ` Ingo Schwarze
2022-07-24 11:20             ` Alejandro Colomar (man-pages)
2022-07-24 14:57               ` Ingo Schwarze
2022-07-24 15:44                 ` G. Branden Robinson
2022-07-24 17:07                   ` FHS and packaging (was: All caps .TH page title) Alejandro Colomar
2022-07-27 16:05                   ` All caps .TH page title Ingo Schwarze
2022-07-29 11:33                     ` man0, man3head (was: All caps .TH page title) Alejandro Colomar
2022-07-29 12:31                       ` Ingo Schwarze
2022-07-29 11:43                     ` BSD and GPL " Alejandro Colomar
2022-07-24 16:17                 ` man -M tcl " Alejandro Colomar
2022-07-27 15:32                   ` Ingo Schwarze
2022-07-29 12:03                     ` Alejandro Colomar
2022-07-29 13:22                       ` Ingo Schwarze
2022-07-29 13:27                         ` Alejandro Colomar [this message]
2022-07-22 16:19   ` All caps .TH page name Ingo Schwarze

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=0aaf05d3-dc7f-660a-641d-be75d053d3f9@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=schwarze@usta.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox