All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Bug in tty cooked mode kernel 3.12.3
Date: Sat, 07 Dec 2013 18:46:07 -0500	[thread overview]
Message-ID: <20131107184607.eklhad@comcast.net> (raw)

This may have appeared in 3.9.11 with the changes to tty.
Don't know; I just started running 3.12 from kernel.org.
Perhaps nobody saw it before because nobody runs command line programs,
we're all on desktops or x or whatever,
and even those in the command line are still raw.
bash is raw by default, but I run it cooked.
You can supress its readline functions like this.

set +o emacs
set +o vi
set +o histexpand
set +o history

That puts its tty back into cooked mode.

Come up in run level 3, command line mode,
and bring up two consoles with bash in cooked mode as above.
Set a simple prompt like this.

PS1='$ '

Switch to console 2 via alt-f2.
Hit return.
The cursor should drop to a new line then give you the $ prompt.
But it puts the $ prompt next too the old one, then drops down
to a blank line.
The $ prompt and the crlf are out of sequence.
Hit return a few more times and it will straighten itself out.
Then switch back to console 1 alt-f1
Hit return and the same bug,
$ $

hit return a few more times to straighten it out.
Switch back to console 2 and the same problem.
For me it's repeatable.

It's also very confusing when I'm running other command line programs with cooked tty.
For unknown reasons the crlf can come out at the wrong time,
breaking lines or leaving lines together.
My editor can run either way, so I've switched it over to readline mode
and I haven't noticed any problems this way, yet.
But I would prefer the cooked mode.

I looked through MAINTAINERS but couldn't find
a clear maintainer for drivers/tty/tty*.c
Please forward this to the appropriate people.

Thank you.

Karl Dahlke

             reply	other threads:[~2013-12-07 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 23:46 Karl Dahlke [this message]
2013-12-08  5:36 ` Bug in tty cooked mode kernel 3.12.3 Greg KH
2013-12-08  6:16   ` Karl Dahlke
2013-12-08  7:18     ` Greg KH
2013-12-09 23:06 ` Peter Hurley
2013-12-09 23:06   ` Peter Hurley
2013-12-10  0:12   ` Karl Dahlke
2013-12-17 17:30   ` Greg Kroah-Hartman
2013-12-17 17:46     ` Peter Hurley

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=20131107184607.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.