Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fzf always exits with code 130 #5

Open
ms-jpq opened this issue May 24, 2020 · 1 comment
Open

fzf always exits with code 130 #5

ms-jpq opened this issue May 24, 2020 · 1 comment

Comments

@ms-jpq
Copy link
Owner

ms-jpq commented May 24, 2020

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.
@NightMachinery
Copy link

Why is the only way to exit fzf using abort? Its normal usage with accept should work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NightMachinery @ms-jpq