astrocommunity icon indicating copy to clipboard operation
astrocommunity copied to clipboard

Error message when after installing neorg

Open c02y opened this issue 5 months ago • 6 comments

Checklist

  • [x] I have searched through the AstroNvim documentation
  • [x] I have searched through the existing issues of this project
  • [x] I have searched the existing issues of plugins related to this issue
  • [x] I can replicate the bug with the minimal repro.lua provided below

Neovim version (nvim -v)

NVIM v0.11.2

Operating system/version

Archlinux

Terminal/GUI

kitty+zellij

Describe the bug

After I add the following line into my ~/.config/nvim/lua/community.lua and restart nvim, it installs neorg plugin, right after installation of the plugin or restart nvim, a few notifications pop up.

# community.lua
{ import = "astrocommunity.note-taking.neorg" },

Error message:

[neorg] 
 .../lazy/neorg/lua/neorg/modules/core/completion/module/.lua:279
No engine specified, aborting...

Info message:

See https://github.com/nvim-treesitter/nvim-treesitter/#adding-parsers on how to add a new parser!

Error message:

Installation not possible: ...vim/lazy/nvim-treesitter/lua/nvim-treesitter/install.lua:97: Parser not available for language "norg_meta"

Steps to Reproduce

Add

# community.lua
{ import = "astrocommunity.note-taking.neorg" },

Expected behavior

It should work without any error message.

Screenshots

No response

Additional Context

No response

Minimal configuration

-- SORRY, do not know how to add the norg part in this file.
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  -- stylua: ignore
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", lazypath })
end
vim.opt.rtp:prepend(vim.env.LAZY or lazypath)

-- install plugins
local plugins = {
  { "AstroNvim/AstroNvim", import = "astronvim.plugins" },
  { "AstroNvim/astrocommunity" },

  -- add any other plugins/customizations here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

-- add anything else here (autocommands, vim.filetype, etc.)

c02y avatar Jul 08 '25 00:07 c02y

This is actually because of the fact that neorg doesn't support blink.cmp as the completion engine. I suggest you take a look at this there is a solution provided for now until the blink.cmp engine is supported

std-enigma avatar Jul 21 '25 16:07 std-enigma

Info message:

See https://github.com/nvim-treesitter/nvim-treesitter/#adding-parsers on how to add a new parser!

Error message:

Installation not possible: ...vim/lazy/nvim-treesitter/lua/nvim-treesitter/install.lua:97: Parser not available for language "norg_meta"

To resolve this error, simply run the command: :TSInstall norg_meta

This command needs to be executed manually to register the parser with Treesitter. Unfortunately, I’m not sure why it isn’t automatic, but running the above command should fix the issue.

std-enigma avatar Jul 21 '25 16:07 std-enigma

Thanks, after running :TSInstall norg_meta, there is now only one error message:

[neorg] 
 .../lazy/neorg/lua/neorg/modules/core/completion/module.lua:279
No engine specified, aborting...

c02y avatar Jul 31 '25 08:07 c02y

That's good to hear... I’m currently trying to integrate Neorg with blink.cmp, but I haven’t had any success yet. I’m still working on it, and I’ll let you know once I get it working.

std-enigma avatar Aug 01 '25 14:08 std-enigma

Same here... But some people, somehow, make use of the plugin, don't they?

Tyrn avatar Aug 18 '25 12:08 Tyrn

I believe it’s possible to use blink.cmp with Neorg without needing an extra completion source. In fact, with the help of the blink.compat plugin/extension, you can use existing nvim-cmp sources.

That said, I haven’t personally tried this, as I’m not a fan of this approach — I’d much prefer a native blink.cmp completion source. The compatibility method can sometimes cause issues with completion quality and reliability.

std-enigma avatar Aug 20 '25 09:08 std-enigma