Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | fix(events): avoid unnecessary CursorMoved (#24675) | zeertzjq | 2023-08-12 |
| | | | | | | Problem: Temporarily changing current window in a script causes CursorMoved to be triggerd. Solution: Don't trigger CursorMoved if neither curwin nor cursor changed between two checks. | ||
* | fix(events)!: trigger CursorMoved later on switching window (#23711) | zeertzjq | 2023-06-04 |
| | |||
* | feat(lua): add api and lua autocmds | TJ DeVries | 2022-02-27 |
| | |||
* | fix: update last cursor on first CursorMoved (#16698) | Michael Lingelbach | 2021-12-18 |
| | | | | | | | | | | | | | | | | | | | | Closes https://github.com/neovim/neovim/issues/16625 https://github.com/neovim/neovim/issues/12923 The first defined CursorMoved autocommand will immediately fire if the cursor has previously moved upon definition of the autocommand. Plugins add dummy autocommands such as: ```lua autocmd CursorMoved * execute '' ``` to avoid this behavior. Instead, when defining a new CursorHold autocommand, force update the last cursor position. See https://github.com/vim/vim/issues/2053 | ||
* | cursormoved: add tests for CursorMoved | Marco Hinz | 2019-03-29 |