On 11/3/16, 4:21 PM, Chet Ramey wrote:
Quote Removal makes sense during command EXECUTION (since you wouldn't want
your quotes passed in with the arguments) but it doesn't make sense during
(readline) EDITING, IMHO...
OK. So let's talk about a mechanism to provide alternate behavior. The
conve
On 11/2/16 6:03 PM, Dabrien 'Dabe' Murphy wrote:
> I know this thread
> <http://gnu-bash.2382.n7.nabble.com/shell-expand-line-drops-quotation-marks-td16419.html>
> is a year old, but I do have to say I agree with the OP that
> `shell-expand-line`'s decision
most every case I came up with(!)
So, without further ado...
8< 8< Cut Here 8< 8<
I know this thread
<http://gnu-bash.2382.n7.nabble.com/shell-expand-line-drops-quotation-marks-td16419.html>
is a year old, but I do have to say I agree wit
And today I learned that there's an "undo" command! (It's bound to
Ctrl-X Ctrl-U and to Ctrl-_ by default.) Thanks, that's incredibly useful.
I still can't think of a case where I'd want quote removal, which changes
the meaning of the line, but I don't have to use it.
On Fri, Nov 6, 2015 at 5:
On 11/4/15 1:48 PM, Keith Thompson wrote:
> Thanks, I didn't know about history-expand-line.
>
> Is there some case where shell-expand-line would actually be useful?
> If I've typed *"foo bar"*, I can't think of any case where I'd *want*
> it to be replaced by *foo bar*, which has a very different
2015-11-04 14:45:40 +, Pádraig Brady:
> 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 f
Thanks, I didn't know about history-expand-line.
Is there some case where shell-expand-line would actually be useful?
If I've typed *"foo bar"*, I can't think of any case where I'd *want*
it to be replaced by *foo bar*, which has a very different meaning.
Of course the obvious answer is not to use
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
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 per
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.
I've seem this problem with all recent versions of bash, particularly
4.3.11 (preinstalled on
Linux Mint
10 matches
Mail list logo
