Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

powerline9k breaks Ctrl-C #714

Closed
githorse opened this issue Jan 2, 2018 · 4 comments
Closed

powerline9k breaks Ctrl-C #714

githorse opened this issue Jan 2, 2018 · 4 comments
Assignees

Comments

@githorse
Copy link

githorse commented Jan 2, 2018

Using this theme breaks Ctrl-C for me. Hitting Ctrl-C in the middle of certain long-running operation now just prints $RPROMPT_PREFIX$(build_right_prompt) to the screen; I have to hit Ctrl-C four or five times to actually quit.

 ~/a/b/c > master > long_running_task
                                                      $RPROMPT_PREFIX$(build_right_prompt)
                                                      $RPROMPT_PREFIX$(build_right_prompt)
                                                      $RPROMPT_PREFIX$(build_right_prompt)
                                                      $RPROMPT_PREFIX$(build_right_prompt)
 ~/a/b/c > master >

This doesn't always happen, but happens frequently on certain commands. Other zsh themes (e.g. agnoster) don't cause this issue (with the same commands). Removing the right prompt (POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=()) does not change the problem.

Ideas?

@bhilburn
Copy link
Member

Hey @githorse - So sorry for the delayed response, here!

YES. I see this too, actually. You actually don't have to hit it multiple times - it worked on the first time. At least for me, you can actually type a new command and execute it, even when that prompt drawing error occurs. Regardless, it's obnoxious and interrupts the flow.

I believe this problem might be related to how long the vcs segment can take to complete. Can you try removing the vcs segment and giving it another go? Do you see the same issue?

@andreroggeri
Copy link

@bhilburn For me, removing the vcs fixes the issue.

@bhilburn
Copy link
Member

bhilburn commented Feb 2, 2018

Okay, I have a suspicion that integrating the work @quicknir did in #732 is going to improve things here. I'll update again once I've pushed / merged changes.

@bhilburn
Copy link
Member

bhilburn commented Oct 8, 2018

I'm going to close this in favor of #812. Technically, that one is actually the duplicate of this one, but that one has bubbled to the top for whatever reason, hah.

@andreroggeri @githorse - If you wouldn't mind trying the next branch and letting us know if you are still seeing this behavior in #812, that would be SUPER helpful.

@bhilburn bhilburn closed this as completed Oct 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants