From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 2/8] man/man4/console_codes.4: ffix
Date: Thu, 9 Oct 2025 16:57:24 -0500 [thread overview]
Message-ID: <20251009215724.7gms7w7zosrlg44n@illithid> (raw)
In-Reply-To: <20251009215344.tcknw7iexu3kbhnm@illithid>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
Consistently put inter-paragraph space before tables.
Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
---
man/man4/console_codes.4 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/man/man4/console_codes.4 b/man/man4/console_codes.4
index e4fa71422..64d914d7f 100644
--- a/man/man4/console_codes.4
+++ b/man/man4/console_codes.4
@@ -125,6 +125,7 @@ .SS Linux console controls
.P
.B "ESC- but not CSI-sequences"
.ad l
+.P
.TS
l l lx.
ESC c RIS Reset.
@@ -208,6 +209,7 @@ .SS Linux console controls
.P
The action of a CSI sequence is determined by its final character.
.ad l
+.P
.TS
l l lx.
@ ICH T{
@@ -325,6 +327,7 @@ .SS Linux console controls
An empty parameter (between semicolons or string initiator or
terminator) is interpreted as a zero.
.ad l
+.P
.TS
l lx.
param result
@@ -409,6 +412,7 @@ .SS Linux console controls
.ad
.P
Commands 38 and 48 require further arguments:
+.P
.TS
l lx.
;5;x T{
@@ -514,6 +518,7 @@ .SS Linux console controls
6 = cyan,
7 = white;
8\[en]15 = bright versions of 0\[en]7.
+.P
.TS
l lx.
ESC [ 1 ; \f[I]n\f[] ] T{
@@ -692,6 +697,7 @@ .SS Comparisons with other terminals
.B Escape sequences
.P
VT100 console sequences not implemented on the Linux console:
+.P
.TS
l l l.
ESC N SS2 T{
@@ -735,6 +741,7 @@ .SS Comparisons with other terminals
accepts a BEL to terminate an OSC string.
These are a few of the OSC control sequences recognized by
.BR xterm (1):
+.P
.TS
l l.
ESC ] 0 ; \f[I]txt\f[] ST T{
@@ -755,6 +762,7 @@ .SS Comparisons with other terminals
.P
It recognizes the following with slightly modified meaning
(saving more state, behaving closer to VT100/VT220):
+.P
.TS
l l l.
ESC 7 DECSC Save cursor
@@ -762,6 +770,7 @@ .SS Comparisons with other terminals
.TE
.P
It also recognizes
+.P
.TS
l l lx.
ESC F T{
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-09 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:53 [PATCH 0/8] man/man4/console_codes.4: content and style fixes G. Branden Robinson
2025-10-09 21:57 ` [PATCH 1/8] man/man4/console_codes.4: Document codes better G. Branden Robinson
2025-10-09 21:57 ` G. Branden Robinson [this message]
2025-10-09 21:57 ` [PATCH 3/8] man/man4/console_codes.4: ffix G. Branden Robinson
2025-10-09 21:57 ` [PATCH 4/8] " G. Branden Robinson
2025-10-09 21:57 ` [PATCH 5/8] man/man4/console_codes.4: wfix G. Branden Robinson
2025-10-09 21:58 ` [PATCH 6/8] man/man4/console_codes.4: ffix G. Branden Robinson
2025-10-09 21:58 ` [PATCH 7/8] " G. Branden Robinson
2025-10-09 21:58 ` [PATCH 8/8] " G. Branden Robinson
2025-10-09 22:25 ` Alejandro Colomar
2025-10-09 23:00 ` G. Branden Robinson
2025-10-09 23:03 ` G. Branden Robinson
2025-10-09 22:17 ` [PATCH 0/8] man/man4/console_codes.4: content and style fixes Alejandro Colomar
2025-10-09 22:21 ` 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=20251009215724.7gms7w7zosrlg44n@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.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