Using commandline
when trapping a signal in background
#10126
Labels
bug
Something that's not working as intended
Milestone
Tried running with
sh -c 'env HOME=$(mktemp -d) XDG_CONFIG_HOME= fish'
- produces the same behavior.When in background,
commandline "<cmd>"
inside a function that handles signals doesn't actually insert text into the prompt.Let's open two terminals:
Produces no commands inserted into the first terminal. However, when sending the signal from the first terminal to itself, everything works as expected.
Furthermore,
commandline -f execute
would insert a newline as expected, andeval "ls -la"
works as well.The text was updated successfully, but these errors were encountered: