Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11835
| From | Pádraig Brady <P@draigBrady.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: shell-expand-line drops quotation marks |
| Date | 2015-11-04 14:45 +0000 |
| Message-ID | <mailman.1681.1446648348.7904.bug-bash@gnu.org> (permalink) |
| References | <CAAHpriOiAksOZSinXeZTnXtqT6fN0TsLuDNCW5QRY4ox-crihQ@mail.gmail.com> <563A0C7A.8030504@case.edu> |
On 04/11/15 13:47, Chet Ramey wrote: > On 11/3/15 7:44 PM, Keith Thompson wrote: >> The shell-expand-line command (bound to Escape-Ctrl-E) incorrectly removes >> quotation marks from >> the command line, often resulting in a command that differs from what the >> user intended to type. > > This is the documented behavior. shell-expand-line performs all of the > shell word expansions, including quote removal. How useful is that though when the expansion gives a different meaning? >> I often type Escape-Ctrl-E to expand a history substitution in place >> before typing Enter, but it has the side effect of stripping quotes from >> what I've already typed. > > If you want to perform history expansion, try M-^ (history-expand-line). Yes this is useful. I've set it up to happen automatically with this in my .inputrc $if Bash # do history expansion when space entered Space: magic-space $endif cheers, Pádraig.
Back to gnu.bash.bug | Previous | Next | Find similar
Re: shell-expand-line drops quotation marks Pádraig Brady <P@draigBrady.com> - 2015-11-04 14:45 +0000
csiph-web