-
Notifications
You must be signed in to change notification settings - Fork 54
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
Combinaten zsh + promptline + urxvt won't work well #34
Comments
Probably related to #26 – but I don't know why it's only in urxvt |
Probably this commit should fix it: |
I'm seeing this same issue using Konsole and Termite |
Invoking C-c seems to mitigate this, so the prompt is using some function urxvt doesn't like. EDIT: Seems it's something in
Commenting out the if statement fixes the indent issue, but the return code is always displayed. Also confirmed this, EDIT 2: Done some more digging, turns out RPROMPT is the issue. EDIT 3: I seem to have fixed it. I'm looking into creating a PR, but for now make
Result is various terminals. |
Some terminals experienced a weird bug with indentation. Should close edkolev#34.
Still an issue in bash under WSL |
Any other combination combination works:
zsh + promptline + qterminal
bash + promptline + urxvt
zsh + not promptline + urxvt
The first line suggests urxvt is the problem, the second, zsh and the third that promptline is the problem.
The problem itself / steps to reproduce:
MYPROMPT>WHATITYPED
MYPROMPT> WHATITYPEDNOW
notice the whitespace between the > and what I typed in the latter example?
This wouldn't be a major issue itself but when being in the state of having no whitespace one can get wired behavior for example like this:
MYPROMPT>ccd ...
now there's a 'ccd'.
These are only "easily reproducible" examples but it can get really weird when one is using the terminal for a longer time.
The text was updated successfully, but these errors were encountered: