3 ms·

In particular I think Fish struggles with backgrounding of functions (backgrounding of non-fish commands seems to work fine). # these behave the same in bash

In particular I think Fish struggles with backgrounding of functions (backgrounding of non-fish commands seems to work fine). # these behave the same in bash but differently in fish some_command & # this works some_function & # this does not The relevant issues are listed here if you're curious about why it's difficult to implement this in Fish: https://github.com/pirate/fish-functions#issues-with-fish https://github.com/pirate/fish-functions#issues-with-fish

hnlmorg 6y ago
Thanks for the link. Makes sense that if Fish doesn't fork itself and isn't multi-threaded then that would be a difficult feature to implement. I had the same consideration right at the conception of my project: fork or multi-thread? I went with the latter. But my shell diverges quite a bit from the typical design a shell would take so there's a lot of reasons it's sub-optimal compared to the excellent work the Fish guys have done with their shell.