You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My installation is on Windows altough I will run nvim in WSL/TMUX.
Issue happens wether I run from PShell or Bash.
When using WSL I run nvim.exe from the windows install, just to be clear.
Reproduce:
Acces any file past the Dashboard, exit.
Some exceptions seem to occur but I cannot pinpoint what makes a file not being created. A mostly sure-fire way to not have any temp file written is to: acces a buffer, do nothing, :w and quit. If changes are made, or if NO changes are made AND NO :w is issued, then a shada is generetated (mostly, it seems, really...)
Fix:
Easily fixable (?) with:
vim.api.nvim_create_autocmd("VimEnter", {
callback = function()
-- Path for Windows
local shada_path = vim.fn.expand("C:\\Users\\USERNAME\\AppData\\Local\\nvim-data\\shada\\main.shada.tmp*")
vim.fn.system('del /Q ' .. shada_path)
end,
})
If someone stumbles upon this ... altough I have absolutely no clue what the implications of doing this are. So far it seems only this plugin has been generating those files, and they are empty so... idk.
The text was updated successfully, but these errors were encountered:
My installation is on Windows altough I will run nvim in WSL/TMUX.
Issue happens wether I run from PShell or Bash.
When using WSL I run nvim.exe from the windows install, just to be clear.
Reproduce:
Acces any file past the Dashboard, exit.
Some exceptions seem to occur but I cannot pinpoint what makes a file not being created. A mostly sure-fire way to not have any temp file written is to: acces a buffer, do nothing, :w and quit. If changes are made, or if NO changes are made AND NO :w is issued, then a shada is generetated (mostly, it seems, really...)
Fix:
Easily fixable (?) with:
If someone stumbles upon this ... altough I have absolutely no clue what the implications of doing this are. So far it seems only this plugin has been generating those files, and they are empty so... idk.
The text was updated successfully, but these errors were encountered: