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

Bad behaviour when SIGINT #29

Closed
ghost opened this issue Jul 28, 2014 · 1 comment
Closed

Bad behaviour when SIGINT #29

ghost opened this issue Jul 28, 2014 · 1 comment
Labels

Comments

@ghost
Copy link

ghost commented Jul 28, 2014

Hi. When writing commands, I use to type Ctrl+C to "reset" and start writing another command (not sure if this is a bad habit xD).

I know of Ctrl+W for deleting a whole word, but after writing a tar command with a filename containing a lot of spaces (example), Ctrl+C is faster than Ctrl+W.

Well, when I type Ctrl+C in elvish, this is what happens:

29

Order of events:

  1. Start elvish
  2. ^C
  3. Enter = "Editor error"... blah. After this error everything works fine...
  4. Enter. I could write a command and it would work.
  5. When I exit (Ctrl+D) and return to a bash shell, pressing Enter doesn't move the cursor to the new line; instead, the prompt is written inline.

I'm running Go v1.3 in a 64-bit Ubuntu 14.04.

@xiaq
Copy link
Member

xiaq commented Jul 29, 2014

This is interesting. I will work on a fix.

xiaq added a commit that referenced this issue Jul 29, 2014
@xiaq xiaq closed this as completed Jul 29, 2014
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