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.

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

Ctrl-c (SIGINT) temporarily disrupts zshell #3

Open
vlymar opened this issue Jun 3, 2018 · 1 comment
Open

Ctrl-c (SIGINT) temporarily disrupts zshell #3

vlymar opened this issue Jun 3, 2018 · 1 comment
Labels

Comments

@vlymar
Copy link
Owner

vlymar commented Jun 3, 2018

Repro steps:

With zshell:

  1. Open a flanpage, e.g. flan ls
  2. Send a kill signal to flan. Doesn't seem to matter which signal (e.g. sigint via ctrl-c, sigterm via kill, etc).
  3. Interact with terminal (hit your enter key, type anything, etc).

Issue

Immediately after flan closes, you'll see the previously displayed flanpage and your shell prompt printed right below it. When you type anything in, the flanpage will disappear and you'll see your shell history.

The same thing exact happens with man, when you send a kill signal to it. The difference is man doesn't recognize Ctrl-c, and flan does.

Expected behavior

Either flan should ignore Ctrl-c (like man), or Ctrl-c should cleanly exit (no future interaction with the shell should cause anything weird to happen).

@vlymar vlymar added the bug label Jun 3, 2018
@vlymar vlymar changed the title Ctrl-c (SIGINT) temporarily disrupts shell Ctrl-c (SIGINT) temporarily disrupts zshell Jun 3, 2018
@vlymar
Copy link
Owner Author

vlymar commented Jun 3, 2018

update - I tested and couldn't reproduce this with bash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant