Re: unquoted expansion not working (was Re: Not missing, but very hard to see)

From	L A Walsh <bash@tlinx.org>
Newsgroups	gnu.bash.bug
Subject	Re: unquoted expansion not working (was Re: Not missing, but very hard to see)
Date	2019-12-15 09:40 -0800
Message-ID	<mailman.895.1576431652.1979.bug-bash@gnu.org> (permalink)
References	(9 earlier) <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <17197.1576365173@jinx.noi.kre.to> <5DF6701C.7040202@tlinx.org>

Show all headers | View raw


On 2019/12/14 15:12, Robert Elz wrote:
>     From:        L A Walsh <bash@tlinx.org>
>
>   | it could break existing scripts that
>  
> Scripts _/should /_not be using brace expansion in the first place,
------
    "Should" is about wishful thinking, not reality.  What you or I
think "should" be done may be depressingly or surprisingly different
from what actually is done.

>  it is useful to save typing for interactive shells,
----
    I wouldn't know, since it doesn't take much for me to re-edit a line
and press 'v' to have it in an editor which I've found is usually the
prudent thing to do, since I can start a more comfortable editor and not
risk losing everything in the re-edit buff due to a misplaced quote among
other reasons. 

    The main reason is about what may be useful and the difficulty in
supporting a ton of small ranges accommodating  the rest of Unicode's
alpha-numerics, or not having to worry about ranges so much as just
proper quoting  for the, relative, handful of meta characters needing it.

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

Thread

Re: unquoted expansion not working (was Re: Not missing, but very hard to see) L A Walsh <bash@tlinx.org> - 2019-12-15 09:40 -0800

csiph-web