Closed danxmoran closed 1 year ago
I'll add to this that this .pants.bootstrap
content doesn't work the same either:
export COLUMNS=$(tput cols)
export LINES=$(tput lines)
Both of these issues can be solved by re-execing through bash instead of sandboxing a bash source. I'm still working through a test detail, but this is solved.
I'll add to this that this
.pants.bootstrap
content doesn't work the same either:export COLUMNS=$(tput cols) export LINES=$(tput lines)
Ah, this is broken in a slightly different way from what I initially thought. It does export and propagate, only it is reporting the wrong numbers.. i.e. it doesn't solve the issue when used with scie-pants
, where as when used with ./pants
it does.
# cat .pants.bootstrap
export COLUMNS=$(tput cols)
export LINES=$(tput lines)
echo "COLS: $COLUMNS, LINES: $LINES"
$ ./pants
COLS: 241, LINES: 69
[...]
$ pants
COLS: 80, LINES: 24
[...]
But that I even have this in the bootstrap is just a work-around for the underlying issue of the term not reporting the dimensions properly in the Pants process in the first place. So it's hack through'n through.
Yeah, exactly. The fix fixes this use case anyhow and there is an IT for it now.
This fix is now live in the 0.4.2 release.
This fix is now live in the 0.4.2 release.
Confirmed working for my tput
use-case 👍🏽
In our
.pants.bootstrap
, we have:(It's a conditional
export
, otherwise we'd put it inpants.toml
)When running
./pants
, thisexport
works to append the 2 values to the end of the config specified inpants.toml
. When running thepants
binary, the setting instead seems to overwrite the existing value with the escaped string contents of the env var, resulting in the error: