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

Interferes with normal behavior of man #20

Closed
ChemGuy88 opened this issue Jun 3, 2018 · 1 comment
Closed

Interferes with normal behavior of man #20

ChemGuy88 opened this issue Jun 3, 2018 · 1 comment

Comments

@ChemGuy88
Copy link

ChemGuy88 commented Jun 3, 2018

Hello!

Kudos on this great product, first of all.

Issue:

While this theme is active, doing $ man [anything], for example, no longer behaves as normal. That is, when I q out of the man view, the contents stay on the terminal instead of flushing out, as it should.

There's a mother bug, that I don't know how to describe (I can upload a video if necessary). Characters get stuck. It happens when I'm scrolling up or down the history with the up and down keys. Then, seemingly at random, some of the characters from that history will remain at the command line, but you can't erase them by pressing backspace. It's just part of the terminal, now. I'm hoping these two bugs are related.

EDIT: So I did some troubleshooting, and it's not at random. The characters get stuck when the number of characters input is >= 32. So if I type in wwwwwwwwwwwwwwwwwwwwwwwwwwwwwww (31 w's), I won't have ghost w's in the prompt. But if I type in wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww (32 w's), it'll leave the ghost w's.

This is on Terminal macOS High Sierra 10.13.4 (17E202)

@ChemGuy88
Copy link
Author

I found a solution, at least for my case:

Under Terminal > Preferences... > (Profile) > Advanced, "Declare terminal as:" should be set to xterm-256color. (source: https://gist.github.com/shawnbot/3277580)

Funny story; the way I found this solution was because I was trying to figure out why the prompt colors I used in Terminal weren't porting over to iTerm2. When I fixed that, I wondered if I could use the same colors on Terminal, which lead me the aforementioned GistHub page. That allowed me to use the same PS1 value for both iTerm2 and Terminal. Then I thought, "hm, I wonder if Terminal is still buggy?" I performed the error-producing behavior in my issue report and they no longer produced buggy behavior!

I hope this helps anybody else that ends up here Googling similar issues.

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

No branches or pull requests

1 participant