From: Simon Branch <simonmbranch@gmail.com>
To: linux-man@vger.kernel.org
Cc: alx.manpages@gmail.com, mtk.manpages@gmail.com,
Simon Branch <simonmbranch@gmail.com>
Subject: [patch] termios.3: Clarify the description of ONLRET
Date: Mon, 29 Nov 2021 07:00:17 -0800 [thread overview]
Message-ID: <20211129150017.1435-1-simonmbranch@gmail.com> (raw)
Hello! While perusing various termios(3) and termios(4) manpages (as one does)
I noticed the following inconsistency for ONLRET. FreeBSD and NetBSD say
this:
If ONLRET is set, the NL character is assumed to do the carriage-return
function; the column pointer will be set to 0.
OpenBSD says this:
If ONLRET is set, NL also performs CR on output, and reset current column
to 0.
POSIX says this:
NL performs CR function.
The current Linux manpage says this (!):
Don't output CR.
Perhaps I'm misunderstanding the purpose of this flag, but (if nothing else) the
constrast here is a little confusing. It looks like Linux follows the same
behavior as all the other platforms:
$ stty -icanon -onlcr -icrnl -echo onlret onocr; cat
this is some text (^J pressed)
and some more (^M pressed before additional text)
Comments? OK?
---
man3/termios.3 | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/man3/termios.3 b/man3/termios.3
index c11937458..20641f14d 100644
--- a/man3/termios.3
+++ b/man3/termios.3
@@ -203,7 +203,9 @@ Map CR to NL on output.
Don't output CR at column 0.
.TP
.B ONLRET
-Don't output CR.
+The NL character is assumed to do the carriage-return function;
+the kernel's idea of the current column is set to 0
+after both NL and CR.
.TP
.B OFILL
Send fill characters for a delay, rather than using a timed delay.
--
2.34.0
reply other threads:[~2021-11-29 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211129150017.1435-1-simonmbranch@gmail.com \
--to=simonmbranch@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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