Closed amadeus closed 3 years ago
Hey, Thank you for an issue
Could you please check in a clean MacVim and Vim provided by a MacVim package just to make sure where the issue is.
Also I'm not sure what is a term session you're referring to.
I’ll double check a clean macvim shortly, but when I say terminal session - I mean just launching a new window in iTerm or running :term
in macvim
I can confirm - using MacVim downloaded from releases, along without any vimrc/plugins/configuration, does the same thing:
So both in-term Vim and :term are affected, yes?
Could you check "pure" vim from Homebrew/MacPorts/macOS? Apple Terminal.app?
Could you also share your shell config?
My shell config is: https://github.com/amadeus/prezto
In normal terminal - I do not get a V character with my shell config.
If I launch vim in terminal, then start a term session, I see the V character there as well
I'm guessing, it's some sort of layout character that in Vim, isn't processed properly by the terminal code, so may not be something macvim can fix?
Hi,
I'm sorry for a delay response
I've played a bit with your ZSH configuration and I see this V-like symbol in many cases and it's even featured in a screenshot of the configuration
I personally prefer self-made configuration as it does load only what I really want and don't spam with aliases and it is relatively fast. I can share if you'd like to.
Gonna close this for now - it's a character that apparently has some meaning with my zsh config, so probs just need to figure out what that is.
Describe the bug
The best way to describe this bug is using the screenshot above - I am comparing terminal sessions between iTerm and a terminal buffer in MacVim - and I am noticing MacVim display a sort of odd V like character
I am unsure if this is a MacVim bug, a Vim bug, or something with regards to my terminal settings?
Expected behavior My expected behavior is that my MacVim terminal session would look identical to an iTerm session
Environment (please complete the following information):
Additional context This is not a new issue, I think it's been around since terminal sessions were introduced, just never got around to reporting it.