@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)

Yup! Did you want to create the ticket?

i think you and Benjy have the most context on it.

@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.

Hm. Yea, that would be a bit more contextual.

PR incoming 🙂

... depending on how reliable the error code is.

you have to start digging into subshells at that point, and you wouldn’t get an error under the status quo

Yea. You really only need the reminder the very first time.

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.