Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packer.nvim: Error running config for nvim-navic: [string "..."]:0: attempt to call field 'setup' (a nil value) #3045

Closed
bobek opened this issue Sep 20, 2022 · 5 comments · Fixed by #3044
Labels
bug Something isn't working

Comments

@bobek
Copy link

bobek commented Sep 20, 2022

Problem description

After starting lvim the error is shown:

packer.nvim: Error running config for nvim-navic: [string "..."]:0: attempt to call field 'setup' (a nil value)

This is most-likely related to #3043, but breadcrumbs itself are working. I've done LvimCacheReset, PackerUpdate, PackerSync.

LunarVim version

rolling-03ec312

Neovim version (>= 0.7.2)

NVIM v0.8.0-dev-1120-ga0e6e767a

Operating system/version

Debian/sid

Steps to reproduce

No response

support info

Language client log: /home/bobek/.local/state/nvim/lsp.log
 Detected filetype:   go
 
 1 client(s) attached to this buffer: 
 
 Client: gopls (id: 1, pid: nil, bufnr: [1])
 	filetypes:       go, gomod, gowork, gotmpl
 	autostart:       true
 	root directory:  /home/bobek/Sources/moistureguard/golang/modbus-poller
 	cmd:             gopls
 
 Configured servers list: gopls
    __                          _    ___         
   / /   __  ______  ____ _____| |  / (_)___ ___ 
  / /   / / / / __ \/ __ `/ ___/ | / / / __ `__ \
 / /___/ /_/ / / / / /_/ / /   | |/ / / / / / / /
/_____/\__,_/_/ /_/\__,_/_/    |___/_/_/ /_/ /_/ 


Buffer info
* filetype:                go
* bufnr:                   1
* treesitter status:       active

Active client(s)
* name:                      gopls
* id:                        1
* supported filetype(s):     [go, gomod, gowork, gotmpl]
* attached buffers:          1
* root_dir pattern:          1
* capabilities:              implementationProvider  | definitionProvider     | referencesProvider
                             workspaceSymbolProvider | documentSymbolProvider | documentHighlightProvider
                             typeDefinitionProvider  | hoverProvider          | documentFormattingProvider
                             callHierarchyProvider   | foldingRangeProvider

Automatic LSP info
* Skipped servers: [angularls, ansiblels, csharp_ls, cssmodules_ls, denols, ember, emmet_ls, eslint, golangci_lint_ls, graphql, jedi_language_server, ltex, phpactor, psalm, pylsp, quick_lint_js, rome, reason_ls, solang, sorbet, sourcery, sqlls, sqls, stylelint_lsp, tflint, svlangserver, verible, vuels]

Formatters info
* Active: 
* Supported: [gofmt, gofumpt, goimports, goimports_reviser, golines]

Linters info
* Active: 
* Supported: [golangci_lint, revive, semgrep, staticcheck]

Code actions info
* Active: 

Screenshots

No response

@bobek bobek added the bug Something isn't working label Sep 20, 2022
@bobek
Copy link
Author

bobek commented Sep 20, 2022

Dah, I have not seen #3043 (review) when started filling in this ticket. Ended up at the same spot, but was not sure, if it is really the culprit :)

cc @abzcoding , please feel free to close this one, if you don't need it. Thank you.

@abzcoding
Copy link
Member

@bobek can you test if #3044 fixes your issues?

@bobek
Copy link
Author

bobek commented Sep 20, 2022

@abzcoding it fixed the nvim-navic issue for me, broke the colorscheme takeing a closer look (Packer removed the tokionight plugin)

@abzcoding
Copy link
Member

abzcoding commented Sep 20, 2022

@abzcoding it fixed the nvim-navic issue for me, broke the colorscheme takeing a closer look (Packer removed the tokionight plugin)

you might need to run another :PackerInstall since I've replaced lunarvim/tokyonight.nvim with folke/tokyonight.nvim

also make sure you've set your theme like this:

lvim.colorscheme = "tokyonight"

@bobek
Copy link
Author

bobek commented Sep 20, 2022

Yup, that is exactly my config. But for some reason Packer got confused and hasn't handled the switch correctly. Anyway, I was able to make it behave.

Happy to report, that everything is working as expected for me. Thank you for your awesome support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants