From: Alejandro Colomar <alx@kernel.org>
To: Jeremy Baxter <jtbx@disroot.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 6/6] intro.1: Revise paragraph documenting GNU texinfo
Date: Sun, 17 Mar 2024 16:10:38 +0100 [thread overview]
Message-ID: <ZfcH732MgRtXdojj@debian> (raw)
In-Reply-To: <20240317080850.28564-9-jtbx@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi Jeremy,
On Sun, Mar 17, 2024 at 09:08:34PM +1300, Jeremy Baxter wrote:
> ---
> man1/intro.1 | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/man1/intro.1 b/man1/intro.1
> index 72f28bc2e..5aad9d4e7 100644
> --- a/man1/intro.1
> +++ b/man1/intro.1
> @@ -314,15 +314,17 @@ the previous page, and "q" to quit.
> In documentation it is customary to refer to man pages
> by using the name followed by the section number in brackets, as in
> .BR man (1).
> -Man pages are terse, and allow you to find quickly some forgotten
> -detail.
> -For newcomers an introductory text with more examples
> -and explanations is useful.
> .P
> -A lot of GNU/FSF software is provided with info files.
> -Type "info info"
> -for an introduction on the use of the program
> -.IR info .
> +Man pages are concise, and allow you to quickly find a forgotten detail.
> +They're designed to be a complete reference manual for a program.
> +Usually you'd want a guide/tutorial when learning how to use software,
> +rather than a long exhaustive reference manual.
> +For this purpose a lot of GNU software comes with
> +.I info
> +manuals, which are designed to be more of an introduction for newcomers.
> +Use the command "info info" for a first introduction on using the
Redundant: introductions are first, of course. :)
Have a lovely day!
Alex
> +.I info
> +program.
> .P
> Some topics can be documented in HOWTO files.
> To find these, look for HTML files in
> --
> 2.44.0
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-17 15:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 8:08 [PATCH v2 1/6] intro.1: Revise language Jeremy Baxter
2024-03-17 8:08 ` [PATCH v2 2/6] intro.1: Document the meaning of the PS1 variable Jeremy Baxter
2024-03-17 15:00 ` Alejandro Colomar
2024-03-18 19:52 ` Jeremy Baxter
2024-03-17 8:08 ` [PATCH v2 3/6] intro.1: Explain the meaning of a directory Jeremy Baxter
2024-03-17 15:05 ` Alejandro Colomar
2024-03-18 19:57 ` Jeremy Baxter
2024-03-18 21:57 ` Alejandro Colomar
2024-03-18 22:28 ` Jeremy Baxter
2024-03-17 8:08 ` [PATCH v2 4/6] intro.1: Demonstrate special cases of the cd command Jeremy Baxter
2024-03-17 15:07 ` Alejandro Colomar
2024-03-17 8:08 ` [PATCH v2 5/6] intro.1: Define a process ID Jeremy Baxter
2024-03-17 8:08 ` [PATCH v2 6/6] intro.1: Revise paragraph documenting GNU texinfo Jeremy Baxter
2024-03-17 15:10 ` Alejandro Colomar [this message]
2024-03-17 14:47 ` [PATCH v2 1/6] intro.1: Revise language Alejandro Colomar
2024-03-18 19:50 ` Jeremy Baxter
2024-03-18 19:56 ` G. Branden Robinson
2024-03-18 22:05 ` Alejandro Colomar
2024-03-18 22:32 ` Jeremy Baxter
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=ZfcH732MgRtXdojj@debian \
--to=alx@kernel.org \
--cc=jtbx@disroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox