sad
sad copied to clipboard
fzf always exits with code 130
the only way to exit fzf while executing sad is using abort, however this always results in fzf exiting with code 130.
with a stateless architecture, i don't have a good way to know if fzf exiting with 130 is from user interrupts or from intended action.
Why is the only way to exit fzf using abort? Its normal usage with accept should work?