lua/packer/display.lua:151: Invalid key 'border' error when trying to sync

[thepenguinthatwants]

When I use PackerSync I get

Error executing vim.schedule lua callback: ...ite/pack/packer/start/packer.nvim/lua/packer/display.lua:151: Invalid key 'border'

using aur and nvim nightly

• [ ]

[akinsho]

@thepenguinthatwants this error is most likely because your version of nvim does not yet have the border feature which was added a few weeks ago. You need to update your nvim version to the latest nightly

[shadmansaleh]

does not yet have the border feature which was added a few weeks ago .

I'm sure it's at least a few months old :D

edit : Added on Mar 23 actually commit

[wbthomason]

@thepenguinthatwants I agree with @akinsho. However, we should, now that we use the border key by default, update the minimum required commit in the README (unless there's an easy way to test for this feature's presence and only pass border if it's available).

[jonvaldes]

Hey, I have the exact same issue (same error message on same line), but I'm on a very recent version of nvim (nightly as of 4 hours ago, NVIM v0.5.0-dev+1115-gc1fbc2ddf).

This issue only happens, though, once I add this line to the packer startup function:

use 'ryanoasis/vim-devicons'

If I don't add that plugin, everything runs fine 🤷🏻‍♂️

This is my whole startup function, in case it matters:

local use = require('packer').use
require('packer').startup(function()
    use 'wbthomason/packer.nvim'       -- Package manager

    -- Editing tools
    use 'chaoren/vim-wordmotion'
    use 'junegunn/rainbow_parentheses.vim'
    use 'kshenoy/vim-signature' -- Shows marks on the left
    use 'yuttie/comfortable-motion.vim' -- Smooth scrolling

    -- UI
    use 'scrooloose/nerdtree'
    use 'ryanoasis/vim-devicons' -- <<<<<<<<<<<<< THIS SEEMS TO BE THE ONE CAUSING TROUBLE
    use 'mbbill/undotree'
    use 'vim-scripts/a.vim'
    use {'nvim-telescope/telescope.nvim', requires = {{'nvim-lua/popup.nvim'}, {'nvim-lua/plenary.nvim'}} }
    use 'nvim-telescope/telescope-fzy-native.nvim ' -- Faster fuzzy matcher for telescope

    use 'itchyny/lightline.vim'        -- Fancier statusline

    -- File formats
    use 'vim-scripts/FX-HLSL'
    use 'tikhomirov/vim-glsl'

    -- Colorschemes
    use 'joshdick/onedark.vim'         -- Theme inspired by Atom
    use 'morhetz/gruvbox'
    use 'jacoborus/tender.vim'
    use 'kristijanhusak/vim-hybrid-material'
    use 'nanotech/jellybeans.vim'
    use 'NLKNguyen/papercolor-theme'
    use {'dracula/vim', as = 'dracula'}
    use 'gosukiwi/vim-atom-dark'
    use 'chriskempson/base16-vim'

    -- Programming
    use 'neovim/nvim-lspconfig'        -- Collection of configurations for built-in LSP client
    use 'hrsh7th/nvim-compe'           -- Autocompletion plugin
end)

[wbthomason]

@jonvaldes: That's bizarre. Does it happen while installing that plugin, or only on operations after devicons is installed?

[ghost]

I had the same problem but instead of the invalid key being "border" it was "noautocmd". What solved my issue was uninstalling packer, cloning the repo again and running PackerCompile and PackerInstall with only the config below. After this I was able to normally install plugins with use.

require('packer').startup(function()
    use 'wbthomason/packer.nvim'
end)

[jonvaldes]

@wbthomason So I cleaned the nvim-data directory, and then it wouldn't only happen when adding that line to the packer config. Instead, it happened always. I commented the border line from the packer source, and now it works (albeit that makes it quite ugly).

[wbthomason]

@vitorof: Your error should just mean that your Neovim is out of date (noautocmd was added recently). Did you also update Neovim while debugging?

@jonvaldes: Is nvim-data ~/.cache/nvim/ or another directory? Can you please also provide more information about your system (i.e. the full output of nvim --version)?

[ghost]

@vitorof: Your error should just mean that your Neovim is out of date (noautocmd was added recently). Did you also update Neovim while debugging?

Weirdly I did not update Neovim while debugging and it still worked by doing what I mentioned. Perhaps it was ignored or something.

[jonvaldes]

@wbthomason

nvim --version

Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2 /Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -DWIN32 -D_WIN32_WINNT=0x0600 -DINCLUDE_GENERATED_DECLARATIONS -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -ID:/a/neovim/neovim/build/config -ID:/a/neovim/neovim/src -IC:/projects/nvim-deps/usr/include -ID:/a/neovim/neovim/build/src/nvim/auto -ID:/a/neovim/neovim/build/include
Compiled by runneradmin@fv-az152-985

Features: -acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM\sysinit.vim"
  fall-back for $VIM: "C:/Program Files/nvim/share/nvim"

This is a Win10 machine, nvim-data is in ~\AppData\Local\nvim-data\

[typkrft]

I am also having this issue running on macOS using --head and --nightly. Edit: In my case I was actually using the wrong nvim binary sorry. I have an M1 mac and an x86 binary running through Rosetta was installed and in my path before the native head/nightly binaries. Using the native binary resolved this issue.