halt on exit #178
Comments
|
I'm seeing the same thing when editing git commit messages, which tend to be short-lived temp files (I think) |
|
Ah good to know -- I might have to add a default list of There's a general issue in Neovim right now about exiting while tags generation is running -- see issue #167. That said, it looks like there might be some other problem here caused by Gutentags and some other plugin interfering with each other. The error you mentioned seems to be raised through something running auto-commands on the |
|
How could I check the autocmd runned in the process? @ludovicchabant |
|
You can type |
|
output maybe startify or neovim itself? |
|
Maybe..... (I didn't know startify, thanks for that, it looks interesting :) ) You could try to disable startify... I don't know what that rpcnotify is though... is that Neovim itself? (I don't have it in my copy of Neovim, but I'm still on 0.2.2). |
|
Yeah, it used to notify python client that current dir has been changed, which included in neovim 0.3.0 |
|
Hello @ludovicchabant, I am writing to confirm that I also experience this error, specifically seeing this message when I use Neovim to edit a commit message for Git: Here are the details about the version of Neovim: I am running Neovim on an Ubuntu 16.04 machine. Is there a workaround that you would suggest? |
|
This issue still exists in the release version of neovim 0.3.1 |
|
I can't reproduce this bug with Neovim 0.3.1, but I just pushed commit 2689e11 which adds a new |
|
I'm still getting the error in the original issue description here, even though it seems from #167 that it should be resolved. My If I open a ruby file, then quickly Neovim version output: And the output of |
|
@stephendolan getting the same with elixir files. /cc @ludovicchabant |
|
@ludovicchabant I get this error on exit also. |
|
i use spacevim, this is the result of search |
|
It looks like the common factor with all people having this bug is that they all have this |
|
rpcnotify looks like is about remote plugin and my |
|
for what it worth with the |
|
I'm not too concerned with the fact that Neovim doesn't kill jobs right away on exit (if it's a problem, you could try to either file a bug upstream, or see if force-killing jobs on Also, I'd rather not detach on exit. I think it could lead to a situation where you're exiting Vim while tags are being generated, and then you start another new Vim session and another tags generation starts, while the old one isn't finished, and now you have the two of them potentially trying to write to the same files. |
|
I got the same error: Just to make sure that this is not related to another plugin I created a really simple init.vim file: So only vim-plug is loaded and so far everything is working as expected with NVIM v0.3.4
Build type: RelWithDebInfo
LuaJIT 2.0.5
Compilation: /usr/bin/gcc-5 -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-bb83ace7-63ac-4a89-b318-3a124a2bc311
Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "
/home/travis/build/neovim/bot-ci/build/neovim/build/nvim.AppDir/usr/share/nvim |
|
I have tried to find a specific plugin responsible for the problem, but I am unable to do so, using
I noticed that the error message is displayed when pgrep is showing one or 2 ctags process ids that are still running * Project contains 6788 PHP files: included in the framework, auto-generated (cache, views, etc) or created by the team, counted them using |
Seems to have come in with the recent version of NeoVim Patch was here: ludovicchabant/vim-gutentags#178 (comment)
|
Same issue here 😞 |
|
I have the same issue. It always happens with gitcommit messages but also when I use nvim as VISUAL (VISUAL=$TERMINAL_EMULATOR -e $EDITOR) and close a file too quickly. The bug does not seem to have any negative impact except for the fact that it is annoying to see that warning once in a while. |
|
I also have this issue. If I disable vim-virtualenv the error message disappear but I still get (after a few second lags, when saving a file): If I don't save the file and just quit I don't have the error. |
|
I got the same error. |
As there is a bug in gutentags which causes some errors when exiting, gutentags is only enabled for some filetyes which are known to not cause any issues. This is the corresponding issue: ludovicchabant/vim-gutentags#178
|
I got the same error. I do feel it's file type related. For me, it doesn't have to be git commit messages. For example, when I open a .premake file in a git directory (I guess it has to be in a git directory, because that's where the gutentags plugin works), remove a line, then ":wq", I would get it. But if I do the same with a ".cpp" or ".py" file, I won't get the error. |
|
Some additional information for the .premake file case I mentioned, if I keep the session open long enough, I won't get the error either. |
|
save error when exiting from git commit messages |
|
for people still looking for an answer as according to the author he added a workaround . i went to vim filetypes and these are ALL the git related file types possible:
|
|
I have exactly the same error. On nvim 0.4.3 and latest gutentags. |
|
I have solved this issue once and for all. let g:gutentags_add_default_project_roots = 0
let g:gutentags_project_root = ['package.json', '.git', '.hg', '.svn']
let g:gutentags_cache_dir = expand('~/.gutentags_cache')
let g:gutentags_exclude_filetypes = ['gitcommit', 'gitconfig', 'gitrebase',
'gitsendemail', 'git']
let g:gutentags_generate_on_new = 1
let g:gutentags_generate_on_missing = 1
let g:gutentags_generate_on_write = 1
let g:gutentags_generate_on_empty_buffer = 0
let g:gutentags_ctags_extra_args = ['--tag-relative=yes',
'--fields=+ailmnS']
let g:gutentags_ctags_exclude = [
\ '*.git', '*.svn', '*.hg',
\ 'cache', 'build', 'dist', 'bin', 'node_modules', 'bower_components',
\ '*-lock.json', '*.lock',
\ '*.min.*',
\ '*.bak',
\ '*.zip',
\ '*.pyc',
\ '*.class',
\ '*.sln',
\ '*.csproj', '*.csproj.user',
\ '*.tmp',
\ '*.cache',
\ '*.vscode',
\ '*.pdb',
\ '*.exe', '*.dll', '*.bin',
\ '*.mp3', '*.ogg', '*.flac',
\ '*.swp', '*.swo',
\ '.DS_Store', '*.plist',
\ '*.bmp', '*.gif', '*.ico', '*.jpg', '*.png', '*.svg',
\ '*.rar', '*.zip', '*.tar', '*.tar.gz', '*.tar.xz', '*.tar.bz2',
\ '*.pdf', '*.doc', '*.docx', '*.ppt', '*.pptx', '*.xls',
\] |
|
None of the mentioned fixes worked for me. |
There was an issue with ctags running at 100% indefinitely when shutting down vim whilst it's running. May have been related to ludovicchabant/vim-gutentags#178 - can't quite recall
|
This bug still occurs. I'm not sure if it's intended behavior but it's certainly not expected. It's not expected because I didn't expect to (potentially have to) exclude file types like JSON to prevent this error I can trigger it consistently (100% of the time) by opening a certain json file on my system, and then doing a If I add I appreciate that gutentags works 99% of the time so this one thing doesn't detract from it's value as a useful plugin (I ignored the error until recently when I realized it occurred 100% on certain files) Edit: This still occurs for me on certain files, like ruby files, even if I do |
|
occurs to me 100% on alacritty's yaml. Just like everybody else, WA is to include the file extension in |
The suggested workaround for this issue from the comments on ludovicchabant#178 is to add any offending file types to the gutentags exclude list. I don't want to do that, since the file types causing me issues are ones with which I DO want to use gutentags!
The suggested workaround for this issue from the comments on ludovicchabant#178 is to add any offending file types to the gutentags exclude list. I don't want to do that, since the file types causing me issues are ones with which I DO want to use gutentags!
ludovicchabant/vim-gutentags#178 The suggested workaround is to exclude as many file types as possible so it doesn't run so often. I think for me it's mostly caused by git co -av and then very quickly exiting
Add "'detach': 1," to the build_default_job_options in autoload/gutentags.vim ref to: - ludovicchabant#178 - ludovicchabant#167 - ludovicchabant#168
and others
If I open a file in the file system and quit quickly, neovim complains following and halt
nvim --versiongenerateThe text was updated successfully, but these errors were encountered: