Commands inside traps are not resolved

[Jayman2000]

Consider this line of Bash code:

trap hello EXIT

The hello in that line of code is an external command that should be resolved, but unfortunately, resholve does not resolve it at the moment.

Steps to reproduce

1. Make sure that the hello command is not on your PATH.

2. Run the minimum reproduction script that I created by running this command:

   nix --extra-experimental-features 'nix-command flakes' run 'git+https://codeberg.org/JasonYundt/commands-inside-traps-are-not-resholved.git?ref=refs/heads/main&rev=48e736a6b3225210da87d4b21033883b6e4c459d'

Result

/nix/store/mam02cpq1v1y6hi242djd1fi5dk37gqi-test-trap-parsing/bin/test-trap-parsing: line 1: hello: command not found

[abathur]

Ha! Fair enough.

Do you have a real world example of a single-word external command used in a trap like this?

(I guess I'm wondering whether the simplest version of support would help real-world cases, or if this has to handle looking into strings before it'll be meaningful.)

[Jayman2000]

Do you have a real world example of a single-word external command used in a trap like this?

Nah, I only used a single command in the example in order to make the example as simple as possible. The only time I ever use traps is for making sure that temporary directories are cleaned up like this:

temporaryDirectory="$(mktemp --directory)"
trap "cd /; rm --recursive --force -- ${temporaryDirectory@Q}" EXIT

[abathur]

Ok. I imagined peeking into the string would be table stakes for trap. Thanks for confirming.