Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15718
| From | L A Walsh <bash@tlinx.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Not missing, but very hard to see (was Re: Backslash missing in brace expansion) |
| Date | 2019-12-12 11:43 -0800 |
| Message-ID | <mailman.743.1576179851.1979.bug-bash@gnu.org> (permalink) |
| References | (2 earlier) <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <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> |
On 2019/12/06 14:14, Chet Ramey wrote:
Seems very hard to print out that backquote though. Closest I got
was bash converting it to "''":
> read -r -a a< <(printf "%q " {Z..a})
> my -p a
declare -a a=([0]="Z" [1]="\\[" [2]="''" [3]="\\]" [4]="\\^" [5]="_"
[6]="\\\`" [7]="a")
#2 is where backslash would be and has been transliterated to the pair
of single quotes. Guess "\\\\" was too messy looking?
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Not missing, but very hard to see (was Re: Backslash missing in brace expansion) L A Walsh <bash@tlinx.org> - 2019-12-12 11:43 -0800
csiph-web