Neorg no longer renders text correctly

[Tvrt1e]

I've been using neorg for about a month now, but all of a sudden neorg stopped working. :Neorg works fine, but in .norg files no Neorg features work. I installed neorg using vim-plug, so I removed it and installed via rocks.nvim, but still nothing worked. Any ideas as to why? Maybe I misunderstood the configuration
neorg.lua:

require('neorg').setup {
load = {
    ["core.defaults"] = {
        config = {
            disable = {
                -- module list goes here
                "core.autocommands",
                "core.itero",
            },
        },
    },
}
}

Reverting to 7.0.0 fixes this, but I would rather use the latest version if possible.

[pysan3]

@Tvrt1e @curelesss

• https://vhyrro.github.io/posts/neorg-and-luarocks/
• Luarocks Issues Thread #1342
• https://github.com/pysan3/Norg-Tutorial/blob/main/MIGRATION-v8.md

[Tvrt1e]

Thanks for the reply. I'm using rocks.nvim, should I switch to lazyvim? I've tried all of the steps in those documents that don't apply to lazyvim.

[curelesss]

Thank you for pointing me to the right place for troubleshooting.

Manage to get Neorg 8.0 install correctly by running :Lazy build luarocks.nvim & :Lazy build neorg

btw, Neovim outputs of building Luarocks states it requries unzip .

[pysan3]

@Tvrt1e AFAIK rocks.nvim is still beta release so you have to dig into the source code to fix your issue, and you are on your own.

Rocks.nvim and lazy.nvim are incompatible so if you are already using lazy, you cannot use rocks for installation.

If you are using some other pm, there is no feature to automatically run build.lua so you'll need to specify it yourself. Read #1342 (comment)

PM other than lazy should be compatible with rocks tho so trying to debug rocks would also be a good way to go.

[Tvrt1e]

I switched to lazy.nvim and got the exact same behavior as with Rocks.nvim. I'm starting to think maybe something other than neorg is the problem, but to my kowledge neorg is the only thing that changed. Everything in Neorg works except for anything that changes the quality of text. Also vimwiki works perfectly fine.

[pysan3]

@Tvrt1e Give me your config including neorg's lazy spec as well as luarocks.nvim.

[Tvrt1e]

All neorg features work save for the ones that modify the way text looks. :Neorg command works, and headers render with concealer enabled.

[pysan3]

So what does not work?

[Tvrt1e]

It really just comes down to colors. Text looks like plain text as opposed to colored/highlighted text, etc..

[Tvrt1e]

I know that bold/colored text functions work in neovim using my colorscheme because code syntax is properly colored and all vimwiki features work without a hitch.

[pysan3]

I found you were having the same discussion here so let me join there.

• Neorg markup no longer renders after 8.0.0 #1374