[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: feature request, shift-enter to inline a newline
From: |
Greg Wooledge |
Subject: |
Re: feature request, shift-enter to inline a newline |
Date: |
Thu, 3 Feb 2022 13:44:32 -0500 |
On Thu, Feb 03, 2022 at 06:40:09PM +0100, Alex fxmbsw7 Ratchev wrote:
> as title says, pressing shift enter would produce a newline into all
> instead of send the cmd away
Two issues.
1) This is terminal dependent. Shift-Enter doesn't do anything different
from Enter on my terminal (rxvt-unicode) for instance. If the terminal
doesn't differentiate between these key combos, then there's nothing
bash can do.
2) What exactly would it *mean* to "produce a newline instead of send
the command"? Are you simply hoping to go back and edit the command
later? If you know in advance that you're writing a multi-line command
that you may wish to edit retrospectively, I strongly advise you to
write it in a script using a real editor. Either by explicitly
running an editor with a filename, or by using bash's "call $EDITOR
for me" feature (ESC v in vi mode, ctrl-X ctrl-E in emacs mode).
- feature request, shift-enter to inline a newline, Alex fxmbsw7 Ratchev, 2022/02/03
- Re: feature request, shift-enter to inline a newline,
Greg Wooledge <=
- Re: feature request, shift-enter to inline a newline, Kerin Millar, 2022/02/03
- Re: feature request, shift-enter to inline a newline, Seth David Schoen, 2022/02/03
- Re: feature request, shift-enter to inline a newline, Chet Ramey, 2022/02/03
- Re: feature request, shift-enter to inline a newline, Dennis Williamson, 2022/02/03