Prompted (pun intended) by the recent thread on detecting missing newlines
in command output, I'd had another look at my own version, and discovered
a potential issue with control characters being written as-is in declare
output. Minimal (harmless) reproducer:
╶➤ x () { echo $'\e[31m'"oops"$'
On 10/31/18 3:13 PM, Michael Felt wrote:
> Running "make test", and I amy have forgotten something I did in the past.
> a) running tests as root (initially)
> b) ends with:
> run-vredir
> 14,16c14,16
> < ./vredir.tests: line 25: $v: A file descriptor does not refer to an
> open file.
> < ./vredir.
On 10/31/18 3:03 PM, Michael Felt wrote:
> Hi,
>
> I finally got around to patching and packaging bash-4.4.23 and had to
> run a "make distclean" because I had copied the old version and without
> the make distclean make kept looking for "bashversion" in the old path
> .../bash-4.4.19/bashversion
On 10/31/2018 9:03 PM, Michael Felt wrote:
> Hi,
>
> I finally got around to patching and packaging bash-4.4.23 and had to
> run a "make distclean" because I had copied the old version and without
> the make distclean make kept looking for "bashversion" in the old path
> .../bash-4.4.19/bashvers
Hi,
I finally got around to patching and packaging bash-4.4.23 and had to
run a "make distclean" because I had copied the old version and without
the make distclean make kept looking for "bashversion" in the old path
.../bash-4.4.19/bashversion
This is just FYI - I'll install yacc, which is what
