Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created April 22, 2019 at 4:47 PM
Updated November 9, 2019 at 8:01 PM
Resolved November 9, 2019 at 8:01 PM
BoxLang: Our new JVM Dynamic Language made by Ortus! Check it out: https://www.boxlang.io
When using bash, if a command doesn't require STDIN, it doesn't read stdin. This means I can do things like copy a script and paste it into a terminal, and it'll run the same whether it's run from a .sh file, or the terminal line by line.
Consider
$ echo "echo hello" | bash hello $ echo "echo hello" | bash -c 'ls' box.json coldbox docbox hi java jmimemagic.log modules testboxNotice in the second command, bash did NOT consume the "echo hello" and did not echo hello after running ls.
commandbox always reads STDIN, and passes STDIN as parameters to the command even when run non-interactively, so I get different results when scripted vs non-scripted. I suppose I'd also get unknown behavior if my script was passed STDIN , and I didn't intend for box to parse that. (The first commandbox invocation would read the entire STDIN)
Consider:
$ /usr/local/bin/box install ✓ | Installing ALL dependencies | ✓ | Installing package [forgebox:coldbox@^5.1.3+737] | | ✓ | Uninstalling package: coldbox | | | ✓ | Uninstalling package: testbox | ✓ | Installing package [forgebox:cbcommons@^1.1.0] | ✓ | Installing package [forgebox:BCrypt@^2.1.0+0000] | ✓ | Installing package [forgebox:docbox@2.1.0+16] | ✓ | Installing package [forgebox:testbox@^2.4.0] $ svc -t ~/service/Lucee5DockerNow consider that's in a script, and I copy into my clipboard
/usr/local/bin/box install svc -t ~/service/Lucee5DockerAnd paste it
$ /usr/local/bin/box install | Installing package [forgebox: svc -t ~/service/Lucee5Docker]Not expected behavior.
It also means if I run this update script, for instance:
bash upd.sh
And then I start typing my next command... ls, echo,cd, whatever - box steals my STDIN and fails. Unless I explicitly set box STDIN to dev null.
In a bash environment this isn't necessary, stdin is only read if BASH needs it (i.e. command was not specified via -c or -s was specified, or run interactively), or if the COMMAND executed needs it (i.e. cat) . And scripts all run the same way regardless of what I'm typing at the time.