Odd issues with becaon and info about beacon

[Malabarba]

Thanks for reporting. 👍 I'll look into this when I get a moment.

[tsdh]

I've debugged point 1 just now. The blink is caused by beacon--window-scroll-function, and the this-command is nil case applies. I have totally no clue why window-scroll-functions are run when point moves from an info heading upwards even when that causes no window scroll.

I can't reproduce the delay, though. This might be caused by beacon--movement-> being slow in large buffers due to its use of count-screen-lines.

[Malabarba]

Thanks Tassilo. I've also noticed something similar elsewhere. It looks like we can't rely on the hook being called only when there was a visible scroll.

[aecay]

I've checked and Tasssilo is correct about count-screen-lines -- commenting out that function in beacon--movement-< causes the delay to disappear. I'm not sure what the alternative would be though, if count-screen-lines is known to be slow.

[Malabarba]

@aecay Tassilo already wrote an improvement for that, I just haven't pushed it to Elpa yet. So at least this problem will be gone soon. ;-)

[Malabarba]

By the way, while we don't have a fix for the info bug. You can disable it info-mode with beacon-dont-blink-major-modes