From: Alex Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] ascii.7: chase down History to earliest
Date: Mon, 17 Oct 2022 11:58:06 +0200 [thread overview]
Message-ID: <2b229c8d-9456-654a-d6a9-8b2727d8af41@gmail.com> (raw)
In-Reply-To: <20221017012257.kb25curb3gajgsxd@tarta.nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1707 bytes --]
Hi!
On 10/17/22 03:22, наб wrote:
> Cf., well, the UNIX Programmer's Manual:
> https://www.tuhs.org/Archive/Distributions/Research/Dennis_v1/UNIX_ProgrammersManual_Nov71.pdf
> PDF page 191; yes, the typographical convention here is insane, and
> the contemprary-correct way to refer to this page from within the manual
> would be /just/ "/etc/ascii", but, given the context, "/etc/ascii (VII)"
> makes the most sense to me
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> man7/ascii.7 | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/man7/ascii.7 b/man7/ascii.7
> index 1bba7bbaa..71e89384b 100644
> --- a/man7/ascii.7
> +++ b/man7/ascii.7
> @@ -134,9 +134,7 @@ F: / ? O _ o DEL
> .fi
> .SH NOTES
> .SS History
> -An
> -.B ascii
> -manual page appeared in Version 7 of AT&T UNIX.
> +/etc/ascii (VII) appears in the UNIX Programmer's Manual.
I wonder if '.BR /etc/ascii (7)' wouldn't be better.
Also, shouldn't we clarify the Version 7 of the UNIX Programmer's
Manual? Or was it only called that way in V7? I ignore much of history
about those times, but I guess older versions also used the exact same
title, right?
Maybe something like:
.BR /etc/ascii (7)
appears in the UNIX Programmer's Manual in Version 7.
I don't know if we refer to that thing in other pages. If so, it might
be interesting to check the syntax used there for consistency.
Cheers,
Alex
> .PP
> On older terminals, the underscore code is displayed as a left arrow,
> called backarrow, the caret is displayed as an up-arrow and the vertical
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-17 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 1:22 [PATCH] ascii.7: chase down History to earliest наб
2022-10-17 9:58 ` Alex Colomar [this message]
2022-10-17 10:56 ` наб
2022-10-17 11:02 ` Alex Colomar
2022-10-25 15:21 ` наб
2022-10-25 16:13 ` Alejandro Colomar
2022-10-17 11:10 ` Subdirs of man*/ (was: [PATCH] ascii.7: chase down History to earliest) (refers: man -M tcl) Alex Colomar
2022-10-17 11:17 ` Alex Colomar
2022-10-17 11:56 ` наб
2022-10-17 13:45 ` Alejandro Colomar
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=2b229c8d-9456-654a-d6a9-8b2727d8af41@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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