Question about aerial.nvim HOT 1 CLOSED

Nope! This is a bit needlessly complex because of the extra-lazy loading logic that I don't think is really required anymore. setup() is split into two parts: there's the initial call to setup() which does as little work as possible (for startup time). It creates commands and autocmds, and stores the config options for later. Only at some future point when we're actually using aerial (we run a command, call an API function, etc) do we perform the second half, do_setup() which creates highlight groups, more autocmds, and some other work. It also sets initialized = true.

So coming back to this line, when you call setup(), if-and-only-if we have already completed this second step of running do_setup once before, call it again now. If we haven't called do_setup before, don't do it right now because we want to put that work off for as long as possible.

from aerial.nvim.