ludovicchabant/vim-gutentags

E117: Unknown function: gutentags#on_vim_leave

pbnj opened this issue · 0 comments

pbnj commented

Describe the bug

Recently, I started consistently seeing the following error when exiting vim:

Error detected while processing VimLeave Autocommands for "*":
E117: Unknown function: gutentags#on_vim_leave

Steps to reproduce

  1. Run vim: vim .
  2. Quit vim: :q (within 1-2 seconds of starting vim)

Share your setup

  • What OS and version of Vim are you using? macOS Monterey 12.3.1

    $ vim --version
    VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May 13 2022 20:56:28)
    macOS version - arm64
    Included patches: 1-4950
    Compiled by Homebrew
    
  • What version of ctags, gtags, or whatever do you have installed?

    $ brew info universal-ctags
    universal-ctags: stable p5.9.20220515.0 (bottled), HEAD
    
    $ ctags --version
    Universal Ctags 5.9.0, Copyright (C) 2015-2022 Universal Ctags Team
    Universal Ctags is derived from Exuberant Ctags.
    Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
      Compiled: May 15 2022, 05:44:02
      URL: https://ctags.io/
      Optional compiled features: +wildcards, +regex, +gnulib_fnmatch, +gnulib_regex, +iconv, +option-directory, +xpath, +json, +interactive, +yaml, +case-insensitive-filenames, +packcc, +optscript
    
  • Are you using g:gutentags_cache_dir? No

Post the logs

  • Run :let g:gutentags_trace = 1.
  • Reproduce the bug.
  • Run :messages and show the messages that Gutentags posted.
  • Look for the tags.log file that Gutentags' script left behind, and post its contents.

Note: Can't see error in :messages because error only occurs on exit & no tags.log file gets left behind after enabling trace and exiting vim.

Additional context

This started occuring after updating vim-gutentags to latest commit (May 12).

I am also able to replicate this issue on the previous commit (May 12), which introduces gutentags#on_vim_leave() for Windows.

Workaround: this is latest commit (Feb 25) that does not reproduce the issue for me. Downgrading to this commit is the suggested temporary workaround.