From: roarde <roarde@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Manual pages for some Tcl commands not accessible
Date: Thu, 08 Oct 2020 05:19:31 +0200 [thread overview]
Message-ID: <20201008031931.2VrZ27G5poU0BGPZBGcjwP8CXVhiuEvghxc1H2oXkgE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25285@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
New comment by roarde on void-packages repository
https://github.com/void-linux/void-packages/issues/25285#issuecomment-705305418
Comment:
The man command processed "3tcl" as a page-entry to search for, which matches with man's documentation.
`man -s n expr` displays the page for tcl's expr command. Section "n" is the default and usual place for tcl-command documentation. The man command will try using arguments as sections until the *first* one fails, then it and the remainder are taken to be pages to be searched for, and the first one found, rather than the first one listed in arguments, is displayed. It found the *page* expr(1) first, so it didn't continue to look for the *page* for 3tcl. All proper. `man -s tcl3 expr` says "No entry for expr in section 3tcl of the manual"; also proper.
We have tcl commands in section n, and the page for the installed binary tclsh in section 1; most usual, and by default. Tcl *libraries* are pulled off into the tcl-devel package along with their manpages in section 3.
Debian does histrionics with shell, sed, make, and patch to shove all the pages, *installed tclsh binary included*, into a created "3tcl". Confusion is normal, given that.
next prev parent reply other threads:[~2020-10-08 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 17:19 [ISSUE] " msiism
2020-10-02 17:21 ` ericonr
2020-10-02 17:21 ` ericonr
2020-10-08 3:19 ` roarde [this message]
2020-10-08 7:23 ` roarde
2020-10-08 7:28 ` roarde
2020-10-08 14:19 ` msiism
2020-10-08 14:19 ` [ISSUE] [CLOSED] " msiism
2020-10-08 15:09 ` msiism
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=20201008031931.2VrZ27G5poU0BGPZBGcjwP8CXVhiuEvghxc1H2oXkgE@z \
--to=roarde@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).