esup VS coc.nvim

Probably the best way to figure out what's going on at startup time is ESUP (Emacs Start Up Profiler): https://github.com/jschaf/esup You could run it on the old config and the new. Although I suppose the processes may be different enough that there's nothing meaningful to compare.

I agree with you. For startup profiling, use-package-report and https://github.com/jschaf/esup can help too.

A very useful tool for achieving faster startup is esup (https://github.com/jschaf/esup) which times each code block that runs in the emacs startup.

Have you tried running M-x esup with https://github.com/jschaf/esup to see what is taking up the start-up time?

Are you on Emacs 28? Native-comp is enabled by default and it's Just Worked™ for me. Or are you on at least Emacs 27? Emacs 27 added native JSON parsing; stuff like lsp-mode works a lot better now.

(Personally running Emacs 29 built from source on an M1 Pro; everything is instant! Even on my old dumpy i5 machine, everything except startup was pretty snappy, with the exception of startup which took ~4 seconds.)

If it's startup you're concerned about, try the esup[1] package to figure out what's taking so long.

[1]: https://github.com/jschaf/esup

If you're really interested what happens on startup, you can play around with the startup profiler( https://github.com/jschaf/esup ) or similar packages that time the execution of your .emacs.

I used the Emacs Startup Profiler (ESUP) https://github.com/jschaf/esup which identified several culprits in my init files. Removing or deferring the loading of those packages took my startup time from ~15 seconds to about 2.5 seconds. (Still room for improvement!)

GitHub - jschaf/esup: ESUP - Emacs Start Up Profiler

Try out esup

As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2].

I would be surprised if emacs couldn't do the same.

1. https://github.com/neoclide/coc.nvim

The most famous TypeScript one probably is coc.nvim

It is flatly the wrong mindset to think of vim as an IDE. vim is a code editor: get in, make change, get out. Consider vim koans, which are a fun little read. You can throw coc.nvim at Neovim, along with a few other bits to give you a Good Enough setup, but vim isn't and will never be an IDE.

I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

coc.nvim

There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.

Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt

Actually you can with coc.nvim & coc-sh. So long as shellcheck is also installed and in PATH, it'll integrate with coc/vim just fine.

When you install an extension it runs an npm install or yarn, iirc, which is going to be problematic for you being offline. I was going to say you could copy that ~/.config/coc folder directly to the other machine but yeah, Windows, no idea. You see here https://github.com/neoclide/coc.nvim/wiki/Using-coc-extensions

You can try https://github.com/neoclide/coc.nvim, the pre-requisite is to install nodeJS, then to install all the languages LSP. This works for me for Angular, Rust, JavaScript, Vimscript, etc