hat can deal with real life challenges and requirements.
Bash should not work that way. no programming language handles logic
this way. Not pascal, korn shell, c shell, cobol, c, c++, lua , fortran
or any other language i ever used.
Thank you for your willingness to open up your trench line,
es from
children to parents? I find that hard to believe.
that makes no sense.
there is no read command in my path.
so, with that out of the way, what is your comment ?
On 12/24/13 08:04, Chris Down wrote:
On 2013-12-23 23:57:32 +0100, rens wrote:
Hello,
this script:
_
wrote:
On 2013-12-24 09:25:05 +0100, rens wrote:
*read is a built in. there is no subshell.
$ echo "$BASHPID"; : | echo "$BASHPID"
26269
26271
any way, it seems then to me that even IF "read" was a subshell, the scope
of that would start and e
a new bash shell
* Run the following commands:
export HISTTIMEFORMAT="[%F %T] "
history
When history gets executed bash segfaults.
--
Rens Hordijk
