Closed miklhh closed 2 years ago
I've now asked a friend of mine to reproduce this issue aswell, from a different system:
NVIM v0.6.1
Build type: Release
LuaJIT 2.0.5
Compiled by builduser
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/share/nvim"
Run :checkhealth for more info
He experiences the same issue.
FAQ
Issues
Neovim Version
NVIM v0.6.1 Build type: Gentoo Lua 5.1 Compilation: /usr/bin/x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/var/tmp/portage/app-editors/neovim-0.6.1/work/neovim-0.6.1_build/config -I/var/tmp/portage/app-editors/neovim-0.6.1/work/neovim-0.6.1/src -I/usr/include -I/var/tmp/portage/app-editors/neovim-0.6.1/work/neovim-0.6.1_build/src/nvim/auto -I/var/tmp/portage/app-editors/neovim-0.6.1/work/neovim-0.6.1_build/include Compiled by portage@localhost Features: +acl +iconv +tui See ":help feature-compile" system vimrc file: "/etc/vim/sysinit.vim" fall-back for $VIM: "/usr/share/nvim" Run :checkhealth for more info
Minimal reproducible config
The minimal config used to reproduce this issue is exactly matching the example minimal reproducible config.
Description
See: Steps to reproduce.
Steps to reproduce
(1) Files used to reproduce error.
(2) Bare minimum VHDL file with preamble only.
(3) Open
test.vhdl
with nvim using the minimal config.(4) Create a new line at the bottom of the file. Start inserting
iee
and let cmp-buffer suggestieee
from the nvim-cmp drop down menu. Selectieee
from the drop down menu and use<CR>
to callcmp.mapping.confirm({ select = true })
from the minimal config.(5) Observe.
Expected behavior
Normal autocompletion, as it works for all other filetypes, beside the VHDL file type.
Actual behavior
Additional context
No response