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


Groups > gnu.bash.bug > #15719

Re: Not missing, but very hard to see (was Re: Backslash missing in brace expansion)

From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups gnu.bash.bug
Subject Re: Not missing, but very hard to see (was Re: Backslash missing in brace expansion)
Date 2019-12-12 14:49 -0500
Message-ID <mailman.744.1576180223.1979.bug-bash@gnu.org> (permalink)
References (3 earlier) <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <5DF2987E.5000309@tlinx.org> <20191212194951.GM851@eeg.ccf.org>

Show all headers | View raw


On Thu, Dec 12, 2019 at 11:43:58AM -0800, L A Walsh wrote:
> >  read -r -a a< <(printf "%q " {Z..a})
> >  my -p a
> declare -a a=([0]="Z" [1]="\\[" [2]="''" [3]="\\]" [4]="\\^" [5]="_"
> [6]="\\\`" [7]="a")

Nice try.  I guess the takeaway from this thread is: "You cannot mix
capital and lowercase letters in brace expansion.  If you try, you
get garbage out."

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


Thread

Re: Not missing, but very hard to see (was Re: Backslash missing in brace expansion) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-12-12 14:49 -0500

csiph-web