micro/internal
Dmytro Maluka 2a1790d15a Don't call onSetActive for an already active pane
Currently onSetActive is called when the user clicks with the mouse on
a pane even if this pane is already active. We should avoid calling it
in this case.

Implementation detail: like with tabs in the previous commit, we cannot
check if the pane is already active just by checking the index passed
to the Tab's SetActive() (since the index may not change while the pane
itself changes), we need to check state of the pane itself. So we move
the onSetActive invocation from the Tab's SetActive() to the BufPane's
SetActive().
2024-04-12 02:21:03 +02:00
..
action Don't call onSetActive for an already active pane 2024-04-12 02:21:03 +02:00
buffer chore: fix some typos (#3239) 2024-04-08 12:04:38 +02:00
clipboard Use zyedidia/clipper for external clipboard 2022-06-14 08:40:57 -04:00
config Temporarily don't initialize runtime files in buffer test 2024-04-03 04:37:44 +02:00
display Highlighting trailing whitespaces 2024-03-14 03:10:31 +01:00
info chore: fix some typos (#3239) 2024-04-08 12:04:38 +02:00
lua Revert "Don't expose Go timers directly to lua" (#3211) 2024-03-25 17:11:12 +01:00
screen Reset mouse release state after restarting the screen 2023-01-29 18:26:55 +01:00
shell Fix term output capturing 2023-09-08 23:27:39 -07:00
util Highlighting trailing whitespaces 2024-03-14 03:10:31 +01:00
views chore: fix some typos (#3239) 2024-04-08 12:04:38 +02:00