You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be an environment independent issue. Sometime I would want to copy the url that contains non-ascii characters, for example, this one: http://zh.wikipedia.org/wiki/Wikipedia:首页.
If I copy this url with native firefox, (i C-l C-c), I will get http://zh.wikipedia.org/wiki/Wikipedia:%E9%A6%96%E9%A1%B5 in my clipboard where the non-ascii chars are encoded properly. However, if I do this via hitting y with vimperator. The content in clipboard would be http://zh.wikipedia.org/wiki/Wikipedia:首页.
Although this issue appears by directly hitting y, I've tested that this problem doesn't shows on yanking the target location of a link with hinting mode (;y).
Non-ascii characters in a URL sometimes cause to an incorrect recognition by some application, so I think this issue should be a bug rather than a feature ;-)
The text was updated successfully, but these errors were encountered:
I think the option you're looking for is yankencodedurl. We've discussed on the mailing list some time ago and decided to keep it as a default of false since a lot of users (myself included) preferred to be able to yank the unencoded url with all the unicode in it.
This should be an environment independent issue. Sometime I would want to copy the url that contains non-ascii characters, for example, this one: http://zh.wikipedia.org/wiki/Wikipedia:首页.
If I copy this url with native firefox, (
i C-l C-c
), I will gethttp://zh.wikipedia.org/wiki/Wikipedia:%E9%A6%96%E9%A1%B5
in my clipboard where the non-ascii chars are encoded properly. However, if I do this via hittingy
with vimperator. The content in clipboard would behttp://zh.wikipedia.org/wiki/Wikipedia:首页
.Although this issue appears by directly hitting
y
, I've tested that this problem doesn't shows on yanking the target location of a link with hinting mode (;y
).Non-ascii characters in a URL sometimes cause to an incorrect recognition by some application, so I think this issue should be a bug rather than a feature ;-)
The text was updated successfully, but these errors were encountered: