-
Notifications
You must be signed in to change notification settings - Fork 262
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
E670 in neovim with the doc file #162
Comments
Thanks and I appreciate it. Let me know if I can help but I might not be able to |
@ryanoasis I have the same issue. I will test it later. |
@zchee Hey thanks |
PR Sent 🎉 |
Cool thanks for the fix. Ha who would have figured that would cause such a breaking issue 😛 I actually generate the vim doc file from the readme markdown using for reference: https://github.com/ryanoasis/vim-devicons/wiki/Development-Workflow Anyway I am going to tag this for the next release 👍 |
Hi, Thanks |
Same here. Maybe it has to do with |
@junkmechanic did you pull the latest devicons? |
hi @ryanoasis Its when @mhartington mentioned that it could be an issue with |
Posting relevant discussion from neovim chat group:
Not sure when they intend to fix this feature/bug in neovim, but in the meantime, would it be possible to change the hyphen in the title of the doc? |
hey @ryanoasis, sorry to ping, but could this be reopened? Looks like it's still around, and the explanation seem to be legit. Will try to PR. |
@mhartington Darn. Yeah sure go for it. I did update the build notes so it doesn't accidentally make it's way back: https://github.com/ryanoasis/vim-devicons/wiki/Development-Workflow But maybe there is another character causing issues. Good luck |
Tested it out locally, it is indeed that From the looks of it, just removing that and dropping the |
Makes sense
I'd prefer to keep it as is. Maybe replace the dash |
PR sent! |
Required Info
vim --version
NVIM v0.1.5-459-g7df9dd3
:echo webdevicons#version()
0.8.3
iTerm
Mac
Optional Info
I've been poking around in the doc file, trying to see where the error is coming from. Seems like bad encoding is happening in nvim, but not regular vim(7.4).
I'll try to hunt it down and look for the culprit and send a PR your way.
Cheers.
The text was updated successfully, but these errors were encountered: