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

Groups > gnu.bash.bug > #15735 > unrolled thread

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

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

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

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.

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web