New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not all trigger_events are working
#52
Comments
|
Just as a side-note: I think I've seen someone else complaining in an issue about the rewrite. I understand that things dont just work right away without bugs. |
|
I had |
|
I can all but guarantee that this is due to the use of When you create an autocmd, the |
I also had this issue with -- /lua/config/autocmds.lua
local function augroup(name)
return vim.api.nvim_create_augroup("lazyvim_" .. name, { clear = true })
end
vim.api.nvim_create_autocmd({ "BufLeave", "WinLeave", "FocusLost" }, {
callback = function()
local curbuf = vim.api.nvim_get_current_buf()
if not vim.api.nvim_buf_get_option(curbuf, "modified") or vim.fn.getbufvar(curbuf, "&modifiable") == 0 then
return
end
vim.cmd([[silent! update]])
end,
pattern = "*",
group = augroup("autosave"),
}) |
|
Check out https://github.com/okuuva/auto-save.nvim , we introduced a fork that solves your problems :) |
Hi,
trigger_events = { "InsertLeave", "TextChanged", "CursorHold", "CursorHoldI", "FocusLost" }reacts only for the first two events, as in the default settings. It used to work before the rewrite, except forFocusLostbut I think that's on my side.Cheers, Daniel.
The text was updated successfully, but these errors were encountered: