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
The hook being window or global makes no difference.
Expected
WinResize's output should be 1.4,1.4 just like eval -drafts. Additionally, moving the cursor after setting the hook should update the hook's output accordingly.
Otherwise, the documentation for WinResize should be updated, as it currently only states that the changes to the selection state will be "discarded", but not that it will be incorrect from the moment it triggers.
The text was updated successfully, but these errors were encountered:
I don't know why one creates a fresh InputHandler object, while the other adds to a stack(?) of input handlers, but it looks to me like eval -draft copies the current selections, while window hooks create a fresh, empty selection set, which matches the behaviour described above.
I'm not sure why the window hook doesn't use the window's current selections; maybe making a copy of the selections would be expensive? Maybe hooks like WinCreate fire before the window is properly initialised, so selection information is not yet available, and it was easier to make all window hooks behave the same way?
Steps
*debug*
buffer.Outcome
*debug*
content isThe hook being
window
orglobal
makes no difference.Expected
WinResize
's output should be1.4,1.4
just likeeval -draft
s. Additionally, moving the cursor after setting the hook should update the hook's output accordingly.Otherwise, the documentation for
WinResize
should be updated, as it currently only states that the changes to the selection state will be "discarded", but not that it will be incorrect from the moment it triggers.The text was updated successfully, but these errors were encountered: