Closed molleweide closed 2 years ago
I am testing commit: 92aa392
on second restart after having run PackerCompile
however, there seems to be
cmp
errors.
the lsp seems to spin up correctly which is very nice.
Put all errs below for ref.
git checkout && vim
These are all the startup errors I get when starting nvim and running a couple of packer clean -> compile -> install
cycles a couple of times to see what happens.
now I have enabled all modules I want.
nice it seems that I get most stuff working kind of now, so I am going to prepare for migrating all my stuff into next then.
what urked me at first was that when I went back to my previous branch doom_conf_ui
i wasn't able to recall it properly but now it seems that most things do work for me in next branch, so now I am migrating everything, and looking into getting all my user moduEs working. I have a lot of git modules with nice commands for managing eveyrhing in vim.
The plugin vgit
has some insanely useful commands.
ideally I would like to create a command for stage_and_commit_chunk_under_cursor
so that you discard everything else and just process the chunk at cursor. would be nice!!
If you're installing doom-nvim 100% fresh (no packer compiled, no plugins installed) it seems to work pretty well.
This is the first load.
Then restart and everything is setup. These issues look like they come from an old packer_compiled.lua
trying to reference things that no longer exist. I'm not sure if it's worth trying to resolve this on behalf of the user (overmanaging what the user's doing could backfire, adding new bugs, annoying warnings etc). But I think I'll add a :DoomNuke
command that deletes packer-compiled and quits doom so the user can re-open it and run :PackerCompile
. If it's possible to detect errors in packer-compiled.lua
we could then suggest the user runs :DoomNuke
and restarts nvim.
The mapper unique identifier is a seperate thing that I need to resolve.
overmanaging what the user's doing could backfire, adding new bugs, annoying warnings etc).
Hmmm, yeah this is dangerous waters, but quite interesting to read your reply. I gotta read up more on packer docs later.
Stale, closed due to inactivity. If this issue is still happening on v4.x
post a comment and I'll re-open :)
I get these errors on startup, and even tho I have run packer compile a million times... so just putting it here now for reference. I am not running a completely clean
next
branch tho but anyways. I can close this later..