metakirby5 / codi.vim

:notebook_with_decorative_cover: The interactive scratchpad for hackers.
MIT License
3.04k stars 84 forks source link

Codi crashes when coc.nvim is used to autocomplete #137

Open gimelg opened 3 years ago

gimelg commented 3 years ago

Issue description

When selecting an item from the autocomplete list generated by coc.nvim, Codi exits with the following error:

E939: Positive count required: keepjumps keepalt buf! 0

.vimrc settings

call plug#begin('~/.vim/plugged')
Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'metakirby5/codi.vim'
call plug#end()

Steps to reproduce

  1. Open vim from command line (e.g. vim test.js)
  2. Open Codi with :Codi command
  3. Type anything that will trigger an autocomplete list by coc.nvim (like an existing variable, or a standard language keyword)
  4. Navigate to a suggested option
  5. Select an item to autocomplete
  6. Click space or ; or any key that will close the autocomplete list
  7. Observe Codi crashing and the error appear

Here is a gif showing the behavior:

codi_cocnvim_bug

Environment

MacOS 10.15.7 (Catalina)

vim --version: VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 10 2021 19:39:20) macOS version - x86_64 Included patches: 1-3325 Compiled by Homebrew Huge version without GUI. Features included (+) or not (-): +acl +file_in_path +mouse_urxvt -tag_any_white +arabic +find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo -balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects -browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers +byte_offset +insert_expand +perl +title +channel +ipv6 +persistent_undo -toolbar +cindent +job +popupwin +user_commands -clientserver +jumplist +postscript +vartabs +clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +virtualedit +cmdline_hist +langmap -python +visual +cmdline_info +libcall +python3 +visualextra +comments +linebreak +quickfix +viminfo +conceal +lispindent +reltime +vreplace +cryptv +listcmds +rightleft +wildignore +cscope +localmap +ruby +wildmenu +cursorbind +lua +scrollbind +windows +cursorshape +menu +signs +writebackup +dialog_con +mksession +smartindent -X11 +diff +modify_fname -sodium -xfontset +digraphs +mouse -sound -xim -dnd -mouseshape +spell -xpm -ebcdic +mouse_dec +startuptime -xsmp +emacs_tags -mouse_gpm +statusline -xterm_clipboard +eval -mouse_jsbterm -sun_workshop -xterm_save +ex_extra +mouse_netterm +syntax +extra_search +mouse_sgr +tag_binary -farsi -mouse_sysmouse -tag_old_static system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" defaults file: "$VIMRUNTIME/defaults.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X -DMACOS_X_DARWIN -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: clang -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl@1.1/lib -L/usr/local/opt/readline/lib -L/usr/local/lib -o vim -lncurses -liconv -lintl -framework AppKit -L/usr/local/opt/lua/lib -llua5.4 -mmacosx-version-min=10.15 -fstack-protector-strong -L/usr/local/lib -L/usr/local/Cellar/perl/5.34.0/lib/perl5/5.34.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -L/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/config-3.9-darwin -lpython3.9 -framework CoreFoundation -lruby.3.0 -L/usr/local/Cellar/ruby/3.0.2/lib

I was unable to get Codi to log anything. When trying to set a path to a log file I get the following error:

E482: Can't create file ~/Desktop/playground/codi-bug/codi_logs.txt

I wasn't sure which man page you were referring to for script version.

Thank you 🙏🏽

lukelbd commented 2 years ago

I'm also getting this issue with vim-lsp. If there is a preview window open showing help info it triggers the same E939 error and the codi pane disappears every time I leave insert mode.

LoneExile commented 2 years ago

same here