I'm doing some testing with an on-screen colorizer library I wrote,
which does
some PTY manipulation, captures screen output, and renders certain regex
patterns in certain colors. It's designed to help testers notice certain
keywords in a test environment that is not easily automated.
On bash 4.3.
I figured it out. Turns out PS1 wasn't set. Interesting how this impacts
interactive process fork behavior (maybe it runs some things the way
non-interactive processes would normally be launched)?
Matthew Giassa, MASc, BASc, EIT
Security
Hi Matthew,
I have a couple questions:
1. How are you testing this? (small concrete cases are helpful)
2. Do you have some specific builtins that exhibit that behavior? (it
doesn't make sense for builtins to fork on their own, unless you're
doing an explicit subshell. Like you mentioned, executin
