Robin Allen

Then this is a bug, and does not constitute support for ligatures. They need to be rendered correctly or not at all.

Yeah, sounds like the way to go.

No, it's a bug. OSX is being clever and sometimes rendering ligatures when we happen to draw several chars at the same time.

Gitgutter gives me similar errors too. Usually if I restart the app, they go away for a while. At some point it will probably annoy me enough that I'll try...

Are you using the latest release (brew install neovim-dot-app) or are you using the latest master (--HEAD)? There have been some fixes merges recently relating to large window support, so...

Interesting stuff, thanks for your research! Might be worth setting a conditional breakpoint to figure out what weird string we're getting.

I'd support this. I think we're stable enough now.

https://github.com/rogual/neovim-dot-app/commit/4641f1f2997bc8da62daaa228f38bce0e29857ab

Can't reproduce. How are you pasting and what font are you using? Can you reproduce with -u NONE using "+gP?

It's not planned, but I'm open-minded! How would you like it to look? Edit: Something to consider would be the width of the separators, which would have to remain as...