dasht-server is inserting encoded apostrophes that (neo)vim-dasht can't decode
snoblenet opened this issue · 7 comments
dasht-server is converting single straight quotes into encoded apostrophes:
https://github.com/sunaku/dasht/blob/master/bin/dasht-server-http#L57
'Vanilla' dasht in the shell knows how to handle these. For example, you can get:
xdescribe Jasmine method
Describing Hooks Mocha guide
However, vim-dasht on Neovim does not. Instead, you get:
'xdescribe' Jasmine method
'Describing Hooks' Mocha guide
I can think of several ways of fixing this, but I'm raising the issue on this repo (vs on vim-dasht) as the simplest solution surely would be to just not encode those straight single quotes.
Thoughts?
BTW this behaviour has stopped. I am not sure why. Feel free to close this issue if it suits.
I tell a lie. The problem is still there. It's just there is no longer an apostrophe at the start and end of each entry. The apostrophes in the middle of entries are still escaped in this way however.
Thanks for your report. Unfortunately, I'm unable to reproduce it on my system. 😥
I can at least isolate the issue to the rendering of XML entities, which is performed by the w3m browser.
Which version of w3m do you have? On my system, I have:
$ w3m -V
w3m version w3m/0.5.3+git20170102, options lang=en,m17n,image,color,ansi-color,menu,cookie,ssl,ssl-verify,external-uri-loader,nntp,ipv6,alarm,markThanks @sunaku. I have:
$ w3m -V
w3m version w3m/0.5.3, options lang=en,m17n,color,ansi-color,mouse,menu,cookie,ssl,ssl-verify,external-uri-loader,w3mmailer,nntp,ipv6,alarm,mark
Good news: I'm finally able to reproduce this issue now, using w3m from Debian instead of Void Linux. 🎉
$ cat /etc/issue
Debian GNU/Linux buster/sid \n \l
$ w3m -V
w3m version w3m/0.5.3+git20180125, options lang=en,m17n,image,color,ansi-color,mouse,gpm,menu,cookie,ssl,ssl-verify,external-uri-loader,w3mmailer,nntp,gopher,ipv6,alarm,mark,migemoLooks like this is an issue with w3m itself: I'm not able to reproduce it with Lynx or Chrome browsers:
