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
set editor-command according to doc in config file: (#set editor-command=termite -e "nvim %s") set editor-command=urxvt -e vis %s (note lack of quotes!)
try executing it on archlinux forums using ;e and CTRL-T. Also attempt Amazon and DuckDuckGo
Expected behaviour
Urxvt window with vis instance opens up, with text from the hinted field. When closed, contents would be transferred over to the hinted field.
Actual behaviour
If quotes are retained, as in example - there is a quick flash then nothing happens. I presume Urxvt opens then immediately closes as quotes seem to break the command somehow
on all three sites, hints aren't shown, but first field is sent to the external editor. This is understandable for archlinux forums and duckduckgo (as there's only one field), but amazon's Order page has two (search and search orders)
on archlinux forums contents aren't transferred back into the post field. On duckduckgo, sometimes the searchbar contents are transferred to editor as 'undefined', and not transferred back (works second time around though). On amazon everything works, except I can't hint the field I'd like. If I manually hint at the field using f first, then it works normally.
This seems to be fixed - I can't reproduce the error, and both ;e hinting and Ctrl+T immediate command work flawlessly.
Unfortunately, I can't recall if there's any parmeter that I changed in the meantime that might affect it either.
Steps to reproduce
#set editor-command=termite -e "nvim %s"
)set editor-command=urxvt -e vis %s
(note lack of quotes!);e
andCTRL-T
. Also attempt Amazon and DuckDuckGoExpected behaviour
Urxvt window with vis instance opens up, with text from the hinted field. When closed, contents would be transferred over to the hinted field.
Actual behaviour
f
first, then it works normally.Vimb --bug-info
Not using
wyebadblock
, but usinghblock
. No idea if that matters, but worth pointing out.The text was updated successfully, but these errors were encountered: