[vim/vim] highlightedyank freezes in a loop after 9.2.0010 (Issue #19481)

10 views
Skip to first unread message

依云

unread,
4:27 AM (18 hours ago) 4:27 AM
to vim/vim, Subscribed
lilydjwg created an issue (vim/vim#19481)

Steps to reproduce

  1. install https://github.com/machakann/vim-highlightedyank
  2. set map y <Plug>(highlightedyank) in .vimrc
  3. Run gvim
  4. try yaw or yap
  5. Vim no longer responses to user input. Ctrl-C doesn't work. It is trapped in this loop:

https://github.com/machakann/vim-highlightedyank/blob/285a61425e79742997bbde76a91be6189bc988fb/autoload/highlightedyank/obsolete/highlightedyank.vim#L156-L163

This issue was introduced by #19062.

Expected behaviour

No freeze. It highlights the yank text for some time and waits for user input again.

Ctrl-C should be able to interrupt such a loop?

Version of Vim

9.2.15

Environment

Arch Linux, Wayfire Wayland compositor, GTK GUI.

Logs and stack traces


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481@github.com>

dezza

unread,
6:49 AM (16 hours ago) 6:49 AM
to vim/vim, Subscribed
dezza left a comment (vim/vim#19481)

So have you tried building without
b542ec0
and confirmed its the cause?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3940778041@github.com>

依云

unread,
8:23 AM (14 hours ago) 8:23 AM
to vim/vim, Subscribed
lilydjwg left a comment (vim/vim#19481)

I just tried reverting b542ec0 from master and the problem still happened.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3940942453@github.com>

dezza

unread,
8:41 AM (14 hours ago) 8:41 AM
to vim/vim, Subscribed
dezza left a comment (vim/vim#19481)

Then it is definetily not my PR, because the rest of the code is related to drawing/scrolling in gtk.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3940969383@github.com>

依云

unread,
9:09 AM (13 hours ago) 9:09 AM
to vim/vim, Subscribed
lilydjwg left a comment (vim/vim#19481)

I tested reverting b542ec0 again, and it worked! I (or make) must have made some mistakes earlier.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3941016225@github.com>

dezza

unread,
9:14 AM (13 hours ago) 9:14 AM
to vim/vim, Subscribed
dezza left a comment (vim/vim#19481)

Let me try to reproduce this in a minute.

Btw, did you know there is https://github.com/vim/vim/blob/master/runtime/pack/dist/opt/hlyank/plugin/hlyank.vim


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3941023665@github.com>

依云

unread,
10:06 AM (12 hours ago) 10:06 AM
to vim/vim, Subscribed
lilydjwg left a comment (vim/vim#19481)

Btw, did you know there is https://github.com/vim/vim/blob/master/runtime/pack/dist/opt/hlyank/plugin/hlyank.vim

I didn't know it! It was added only one year ago, but I installed vim-highlightedyank 9 years ago and kept using it since then.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3941149119@github.com>

dezza

unread,
10:22 AM (12 hours ago) 10:22 AM
to vim/vim, Subscribed
dezza left a comment (vim/vim#19481)

@lilydjwg I don't see a difference, but I only used both stock.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19481/3941191741@github.com>

Christian Brabandt

unread,
2:06 PM (8 hours ago) 2:06 PM
to vim/vim, Subscribed

Closed #19481 as completed via 00353b2.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/19481/issue_event/22984552865@github.com>

Reply all
Reply to author
Forward
0 new messages