mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robert Karszniewicz <r.karszniewicz@phytec.de>
To: barebox@lists.infradead.org
Subject: Re: readling, ctrl-u is not working like linux console
Date: Wed, 16 Oct 2019 17:01:37 +0200	[thread overview]
Message-ID: <c95fed0c-08d9-46fe-9c69-bf004a0e4adb@phytec.de> (raw)
In-Reply-To: <20191016085747.dhb6z3s2ckw5tpnq@pengutronix.de>

On 10/16/19 10:57 AM, Roland Hieber wrote:
> On Wed, Oct 16, 2019 at 04:57:45AM +0800, duhuanpeng wrote:
>> Hi,
>>
>> I find it the barebox console's ctrl-u is not working like my
>> linux host.
>> for now, the barebox's ctrl-u discard the whole line. but the
>> linux consle just remove characters before cursor.
>> is the barebox ctrl-u follows any standard, if not, how about
>> make it just works like linux(ah, it is gnu readline) does.
> 
> FWIW, in bash on both my tty2 and urxvt, Ctrl-U clears the whole line.
> But I don't know if there is a standard for this shortkey.
> 
>   - Roland
> 

In some shells, like mksh, the default behaviour of ctrl-u is to kill 
the whole line. But then it's not called unix-line-discard, and I don't 
think mksh uses readline, either. The "standard" is probably just 
readline, though it makes me wonder where the "unix" came from…

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-10-16 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 20:57 duhuanpeng
2019-10-16  8:57 ` Roland Hieber
2019-10-16  9:14   ` Ulrich Ölmann
2019-10-16 13:47   ` duhuanpeng
2019-10-17  8:54     ` Roland Hieber
2019-10-16 15:01   ` Robert Karszniewicz [this message]
2019-10-16 15:33     ` duhuanpeng

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=c95fed0c-08d9-46fe-9c69-bf004a0e4adb@phytec.de \
    --to=r.karszniewicz@phytec.de \
    --cc=barebox@lists.infradead.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