Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > gnu.bash.bug > #16851
| From | Bruce Lilly <bruce.lilly@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Bash parameter expansion (remove largest trailing match, remove largest leading match, pattern replacement) does not work |
| Date | 2020-08-29 15:25 -0400 |
| Message-ID | <mailman.1729.1598729159.2469.bug-bash@gnu.org> (permalink) |
| References | <CAPyES363zNvUZHWo6imXOyC3UPU5FAbsyFGzWkcJMO-HBhT6gQ@mail.gmail.com> <CAFLRLk_k+J3-Nt9UJ4Fb8c-RewPnVjf_b=ShqGGASG0GmREAhg@mail.gmail.com> <CAPyES3685SjyZfrL+M_56wGqxvh=N9xNchWJ1xqMSrmmEJb9ww@mail.gmail.com> <CAMLQOtQtYxMiiP9=nN72AKC+hKTJ06rLxM7=Nt5LF1M47jvWrA@mail.gmail.com> <CAPyES36MM0OL2gDnaqfpywoyRwk29NWSXWTNFSCgA4a+jBfENQ@mail.gmail.com> |
Unfortunately, because bash is GPL, I can't post the copyrighted script which is covered by a non-GPL license. On Sat, Aug 29, 2020, 15:22 Ilkka Virta <itvirta@gmail.com> wrote: > On Sat, Aug 29, 2020 at 9:56 PM Bruce Lilly <bruce.lilly@gmail.com> wrote: > >> Please don't assume that something output by printf (without quoting) for >> clarity is representative of actual expansion by the shell when properly >> quoted. >> > > If you don't want people to assume (and you shouldn't, if you want them to > help you), > you'd better post the actual script you use, and not just something output > by printf. > Without that, it's impossible to check what quoting you used, or to > reproduce the issue. > >
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Bash parameter expansion (remove largest trailing match, remove largest leading match, pattern replacement) does not work Bruce Lilly <bruce.lilly@gmail.com> - 2020-08-29 15:25 -0400
csiph-web