Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11842

Re: shell-expand-line drops quotation marks

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: shell-expand-line drops quotation marks
Date 2015-11-06 08:12 -0500
Message-ID <mailman.1828.1446815567.7904.bug-bash@gnu.org> (permalink)
References <CAAHpriOiAksOZSinXeZTnXtqT6fN0TsLuDNCW5QRY4ox-crihQ@mail.gmail.com> <563A0C7A.8030504@case.edu> <563A1A14.5060609@draigBrady.com> <CAAHpriMHm+d_w8gCLAJSn+kS-w2hf-es-23KMBaPHW1Ws2t_jw@mail.gmail.com>

Show all headers | View raw


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 meaning.
> Of course the obvious answer is not to use it, but I'm wondering why
> it's there.

Sure, when you want to expand aliases or variables in the command before
executing it.  It's only the quote removal that you -- in this case --
don't want.  You can also undo the word expansions after viewing them,
restoring the quoted strings.

There are separate bindable commands for history expansion, alias
expansion, and history-and-alias expansion.  If you don't want the
rest of the word expansions, you can easily rebind the commands.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: shell-expand-line drops quotation marks Chet Ramey <chet.ramey@case.edu> - 2015-11-06 08:12 -0500

csiph-web