Hi all,
I'm reaching out to report what I believe to be a bug with the
*--pretty-print* feature in bash-5.2. From what I can tell, Bash uses the
utf-8 character */001* as an escape character. However, when using the
pretty-print feature in Bash, this doesn't seem to be considered. So, for
example,
Are you planning on releasing a patch for this? If you'd like me to try to
prepare a patch, I'd appreciate some guidance around the various
dequote_... functions in subst.c. Thanks!
Best,
Seth
On Wed, Dec 27, 2023 at 1:03 PM Chet Ramey wrote:
> On 12/25/23 5:00 PM, Seth Sabar wrot
Hi Grisha,
I didn’t know to look there (I’m still pretty new to the Bash source).
Thanks, this is exciting!
Best,
Seth
On Jan 16, 2024, at 12:18 PM, Grisha Levit
wrote:
On Tue, Jan 16, 2024, 11:01 Seth Sabar <[1]sethsa...@gmail.com> wrote:
A
Hi,
I'm reaching out to report a bug with the -*-pretty-print* option in bash.
Consider the following script:
*case esac in (esac) echo esac;; esac*
When bash is run with *--pretty-print* on this script the result is:
*case esac in esac)echo esac;;esac*
which is no longer v
Hi,
I'd like to report a bug with the *--pretty-print* feature of bash. When I
run the following script:
*coproc sleep 5*
the pretty-printed result is
*coproc COPROC* sleep 5
The reason this happens is because within Bash's AST every *coproc* is
given a name regardless of whether the user spec
