dhruvasagar / vim-prosession

Handle vim sessions like a pro
254 stars 22 forks source link

Error on VimLeave #81

Closed dapetcu21 closed 2 years ago

dapetcu21 commented 3 years ago

I get something like this every time I close nvim. Here's my init.vim: https://github.com/dapetcu21/vimrc

This is with just one buffer open (init.vim):

[coc.nvim] Error on autocmd VimLeavePre: request error nvim_command - Vim(mksession):E190: Cannot open "/Users/da_petcu21/.local/share/nvim/prosession//Users/da_petcu21/.config/nvim/init.vimUsers/Users/da_petcu21/.config/nvim/init.vimda_petcu21/Users/da_petcu21/.config/nvim/init.vimWork/Users/da_petcu21/.config/nvim/init.vimvscode-language-fuior.vim" for writing[coc.nvim] Error on autocmd VimLeavePre: request error nvim_command - Vim(mksession):E190: Cannot open "/Users/da_petcu21/.local/share/nvim/prosession//Users/da_petcu21/.config/nvim/init.vimUsers/Users/da_petcu21/.config/nvim/init.vimda_petcu21/Users/da_petcu21/.config/nvim/init.vimWork/Users/da_petcu21/.config/nvim/init.vimvscode-language-fuior.vim" for writing
dhruvasagar commented 3 years ago

@dapetcu21 It looks like an error stemming from fuior, I don't know much about it. Does not seem to be related to vim-prosession.

dapetcu21 commented 3 years ago

How would that be stemming from fuior? What makes you think that? The only mention to fuior in that error is that vscode-language-fuior mention, which happens to be the dirname of a repo I've been working on recently (could as well have been part of the current dir).

Fuior is just a language I've been working on, btw. It has a tree-sitter grammar that I loaded with neovim's tree sitter support. If there's something wrong with it, I'd love to be able to debug it, though.

dhruvasagar commented 3 years ago

The error message you pasted :

Error on autocmd VimLeavePre: request error nvim_command - Vim(mksession):E190: Cannot open "...init.vimvscode-language-fuior.vim" for writing
dhruvasagar commented 3 years ago

@dapetcu21 Also the path mentioned there is weird and wrong, I don't know exactly where this is coming from, but vim-prosession is certainly not trying to write this file.

dhruvasagar commented 2 years ago

Let me know if this is still an issue and wasn't addressed in #86