Joe Casadonte
Joe Casadonte
I (personally) don't need the focus to return back to the terminal when the file is closed -- I'm not even sure that's possible. But the first part, raising the...
Another use-case: when viewing application log files, I do not wish to accidentally change a file.
I couldn't get the unit tests to run, so I'm not comfortable submitting a pull request. That and I don't really do Python, so I don't know if what I...
There's my Bash ignorance showing -- thanks!
Here is the output: ``` $ test/bats/bin/bats test/99* --formatter cat 1..5 suite /tmp/bats-assert-issue/test/99-bats-issue.bats begin 1 [1] this one executes successfully ok 1 [1] this one executes successfully begin 2 [2]...
It was not -- my apologies! ``` $ test/bats/bin/bats test/99* --formatter cat 1..5 suite /tmp/bats-assert-issue/test/99-bats-issue.bats begin 1 [1] this one executes successfully ok 1 [1] this one executes successfully begin...
Sadly it does. Replacing the third test with the following: ``` @test "[3a] this one will report as not executed" { foo=/tmp/foo touch $foo assert_file_exist "x$foo" } @test "[3b] this...
That's very esoteric -- thanks for digging into it! I agree, that's a Bash bug that can be worked around rather than a Bats issue to be fixed. Will you...
I think this behavior is intended (or at least expected). From the Bash manual: > local > > local [option] name[=value] … > > For each argument, a local variable...