| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
| |
I mistakenly suggested maxlines=&cmdwinheight, forgetting that it is
calculated from topline, not cursor. maxlines=1 makes the most sense in
cmdwin.
ref #15401 622a36b1f1c652a8de433028bc4a03a1216db23f
|
| |
|
|
|
|
|
|
|
| |
Add a new default autocommand to limit syntax highlighting
synchronization in the command window. This refactors the nvim_terminal
autocommand out of main() and into a new init_default_autocmds()
function, which is now part of the startup process and can be further
extended with more default autocommands down the road.
ref #6289 #6399
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
"enter"/"leave" is more conventional for Vim events, and
"attach"/"detach" distinction does not gain much.
|
| |
|
|
|
| |
doc: ginit.vim, gvimrc
fix #3656
|
| |
|
|
|
|
|
| |
ref #343
Though I don't see a strong benefit, it isn't too much of a burden, and
maybe avoids confusion in some cases.
|
| |
|
|
|
|
|
|
|
| |
* Remove FUNC_ATTR_NONNULL_ALL from function without pointer arguments.
Otherwise the ASAN build would complain:
error: 'nonnull' attribute applied to function with no pointer arguments [-Werror,-Wignored-attributes]
static void do_autocmd_focusgained(_Bool gained) __attribute__((nonnull));
|
| |
|
|
| |
Generalize the "schedule schedule" technique.
|
| |
|
|
|
|
|
|
|
|
|
| |
main_loop.fast_events does not manifest as K_EVENT, because it is
processed at a different stage than main_loop.events. In order to queue
into main_loop.events, we need to go through the threadsafe
loop_schedule(), which queues into main_loop.thread_events and
eventually main_loop.fast_events. _Then_ it is safe to directly queue
into main_loop.events.
This makes it more likely that the event is treated as K_EVENT.
|
|
|
closes #4840
closes #6164
|
