Hi James,
On 2/27/23 20:17, James K. Lowden wrote:
> On Wed, 7 Sep 2022 00:13:18 +0200
> Alejandro Colomar
> wrote to :
>
>> If someone wants to send it as a patch, I'm open to discussing it.
>> I remember having some concerns when I read the page, but I don't
>> remember now about them. I'd
James K. Lowden wrote:
> Attached is a straw man 1st draft of what an introduction to the man
> system might look like. If it clears the threshold of raspberries,
> perhaps we can mold it into something useful.
>
> I think the page should be called man-intro, or intro-man. (Need
> help?
On 5/23/21, Oliver Corff wrote:
> in a follow-up to my last message I just want to give one real-world
> example of a very terse manpage, "for the initiated reader only."
>
> Take refer(1).
There is an open bug report documenting the deficiencies of the refer
man page (http://savannah.gnu.org/bug
On Sun, May 23, 2021, Oliver Corff wrote:
> in a follow-up to my last message I just want to give one
> real-world example of a very terse manpage, "for the initiated
> reader only."
>
> Take refer(1).
> Terseness is nice, but in the case presented here the first paragraph of
> DESCRIPTION in the
Hi All,
in a follow-up to my last message I just want to give one real-world
example of a very terse manpage, "for the initiated reader only."
Take refer(1).
It starts with
NAME
refer - preprocess bibliographic references for groff
DESCRIPTION
This file documents the GNU ve
Well, isn't this a good reason to emphasize the difference between man
and help?
Not finding "cd" in a man page means that it is a shell internal; this
could be stated as an explicite reason why it doesn't come with its own
manpage.
Perhaps a note of caution to the novice reader could be added i
I don't know why that would occur...
(Aside note):
[In the HP-UX Reference Manual (HP's Unix which was POSIX compliant) I
produced in late 1992, which contained all manpages, there is a manpage
included in Volume 1 on page 91 and 92 with the heading at the top of each
past: "cd(1)". The manual c
Ulrich Lauther wrote in
<20210522214249.GA20730@starlite>:
|On Sat, May 22, 2021 at 08:18:41PM +0200, Oliver Corff wrote:
|>
|> "man cd", on the other hand, opens the bash built-in command *man page*,
|> which, at least on my system is a plethora of text to read (and digest).
|>
|on my syt
On Sat, May 22, 2021 at 08:18:41PM +0200, Oliver Corff wrote:
>
> "man cd", on the other hand, opens the bash built-in command *man page*,
> which, at least on my system is a plethora of text to read (and digest).
>
on my sytem (ubunto mate) "man cd" results in "No manual entry for cd".
> Just m
Hi James,
this is a very nice intro indeed. I have a few suggestions:
I agree with Dave that the passus on numbered sections of man pages
should be moved further down. The majority of novice users will likely
search for commands, not necessarily for functions etc. A dedicated
section "On Section
On 5/17/21, James K. Lowden wrote:
> Attached is a straw man 1st draft of what an introduction to the man
> system might look like. If it clears the threshold of raspberries,
> perhaps we can mold it into something useful.
I think it looks great!
I'm admittedly not its target audience, as I hav
On Mon, 17 May 2021 16:24:34 +1200
"Michael Kerrisk (man-pages)" wrote:
> > Maybe Michael or Alejandro can advise regarding where they think a
> > good place for a man page utilization tutorial would be.
>
> If any place, I think intro(1) would be most appropriate, or,
> failing that, an initial
12 matches
Mail list logo
