https://pantsbuild.org/ logo
#development
Title
# development
w

witty-crayon-22786

11/21/2022, 7:18 PM
@ancient-vegetable-10556: a random papercut thing for the
experimental_shell_command
list (which i think would be good in either a
Project
board or stabilization ticket): the
tools
list is required even if no tools are used (i.e. if all you need is
bash
itself)
a

ancient-vegetable-10556

11/21/2022, 7:19 PM
Yup! Did you want to create the ticket?
w

witty-crayon-22786

11/21/2022, 7:20 PM
i think you and Benjy have the most context on it.
oh, you mean for this papercut? yea, i can if that would help
on second thought, it’s likely a rare case to use only
bash
, and in all the other cases it’s probably a useful bit of guidance that you’ll need to declare the tools you use.
a

ancient-vegetable-10556

12/02/2022, 4:53 PM
@witty-crayon-22786 I just started updating the exception message here, and wondered whether we could do better. If a user needs
tools
, and fails to specify them, it looks like
bash
has a reliable error code of
127
for command-not-found errors.
w

witty-crayon-22786

12/02/2022, 6:07 PM
Hm. Yea, that would be a bit more contextual.
a

ancient-vegetable-10556

12/02/2022, 6:07 PM
PR incoming 🙂
w

witty-crayon-22786

12/02/2022, 6:07 PM
... depending on how reliable the error code is.
a

ancient-vegetable-10556

12/02/2022, 6:08 PM
you have to start digging into subshells at that point, and you wouldn’t get an error under the status quo
w

witty-crayon-22786

12/02/2022, 6:09 PM
Yea. You really only need the reminder the very first time.
a

ancient-vegetable-10556

12/02/2022, 6:10 PM
Right, with proposed behaviour:
$ echo fleh
would raise an error log, alerting you to update your
tools
, `$ echo `fleh`` would fail silently, but that would fail silently either way.