vim-snippets VS nerdtree

Also, I'm using vim-snipmate style snippets in LuaSnip. How can I import snippets in javascript.snippets in html.snippetswithout having to copy everything.

cmp works fine and I was able to trivially make it only suggest lsp completion for me by only including lsp sources. The setup is significantly more complicated with having the install 7ish plugins instead of just 3 for coq. I don't think I would've had the patient to go through the setup when I was just starting to use neovim. cmp also have much nicer UI (e.g. it shoulds documentation and sometimes function signiture as you browse through the suggestion.) With snippet you can find something like https://github.com/honza/vim-snippets which have more than what I need. You also need to choose a snippet engine so that's more decision to make.

Since LuaSnip also supports snipmate I'm using vim-snippets since it's offering a lot of snippets I'm using often without having to write my own. But as @eliizaak said: it's not Lua and perhaps I'll find the time and energy to learn a bit more about LuaSnip and write my own snippets ... ;)

It includes the snippets from honza/vim-snippets and my own snippets.

vim-snippets as you've already mentioned.

Skimming over the blog post you linked, it appears that the author uses Vim plugins to get some of the snippets working, which I'm near-certain is impossible with the Vim features available to Obsidian. I don't think installing Vim plugins with vim-plug (as used by both myself and the author of the linked blog) is possible in Obsidian, for example. Without some way to manage installing Vim plugins, you won't be able to get plugins which enable vim snippets as used in the blog post.

Sorry does it?

Auto adding include files or a specific non-static function is generally a bad idea, but I use yasnippet on Emacs for copyright/licensing info, this seemingly has the same purpose but oriented towards vim users, which makes file templates trivial (on Emacs at least, I don’t usually use vim unless I can’t use Emacs or mg for some reason).

I personally use nerdtree. Add nerdtree-git-plugin too, that's nice when looking at your project (for files, use vim-gitgutter).

nerdtree is another very popular option

Using my toy js refactoring plugin and NERDTree.

2) Syntax check https://github.com/vim-syntastic/syntastic 3) File navigation https://github.com/preservim/nerdtree 4) Autocomplete There are many autocomplete extensions. I haven't found one that I feel comfortable to recommend. Another way is to create a txt file with all the key words and lines in the languages you use, make an autocommand that adds the txt file to the buffer, and then use ctrl-n or ctrl-p to autocomplete. You can also use ctrl-x-ctrl-l to autocmplete entire lines. 5) Running code Add commands in your .vmrc to run the current file as a a whatever file. I use :J to run java files, :P to run python files, :C to run c files and so on. For example, this is my command to run a java file: command J execute "!java %:t"

Plug 'https://github.com/preservim/nerdtree'

My basic vim workflow is that I open vim, which opens NerdTree for me by default. I can find the file I want in NerdTree, or I can hit Ctrl+p to open a file with fuzzy searching.

What's also useful is to have a tree plugin (such as nvim-tree or nerdtree), so you can just open any file in the workspace (or outside it) if needed. That way, even if you delete a buffer, you can just come back to a file whose buffer you deleted.

Worth noting Nerdtree’s repo is now at https://github.com/preservim/nerdtree and not at https://github.com/scrooloose/nerdtree