note.nvim VS nvim-compe

I write a hierarchical structured task list (very similar to op) with a neovim plugin I wrote (https://github.com/gsuuon/note.nvim). Sometimes I'll write these items as commit messages, make the changes and check them off as I commit. I mark the current task so that if I get interrupted I can recontextualize fairly quickly.

I use my neovim plugin note.nvim[1] to brainstorm and plan features as well as track day-to-day stuff. It's one of the few projects of mine that I've spent more time using than building - by a good amount.

I have a top level ~/notes/projects/foo. When the project is small I just keep everything in a single file. Each feature gets its own item hierarchy and I use folds to manage which 'scope' I'm seeing. After I decide on what (not) to work on, I can mark that node as "won't do" or "pending". When I pick up a task for the day I can deep-link to where I initially brainstormed the feature.

[1]https://github.com/gsuuon/note.nvim

I think if you've spent more than 2 full weeks trying to figure out an effective note-taking system, it's time to just design and build out your own. Nothing will ever be more perfect for you than the one you build for yourself. Mine's at https://github.com/gsuuon/note.nvim

I just wanted easy daily task tracking and timestamped notes at first, now I slowly add things to it. I can deep-link to items or sections in other files (even at different commits) and have helpers that effectively exposes an API for my tasks. Everything else is just standard neovim things, like using Telescope for finding labeled items.

I use https://github.com/hrsh7th/nvim-compe and https://github.com/simrat39/rust-tools.nvim along with the built in LSP and auto completion works really well. You will want treesitter and all that setup too.

I want to share my code for my migration from nvim-compe (deprecated) to nvim-cmp. Though, I would describe myself as an experienced Vimmer I am not very familiar with the whole Lua thing (although I really appreciate it and hope that Lua's first class citizen can compete with the elisp ecosystem^^).

Wrong, plain and simple. A total misconception.

compe.nvim

For autocomplete/intellisense: https://github.com/hrsh7th/nvim-compe

But nvim-compe already exists.

completion-nvim OR nvim-compe

Here's some setup idea: - packer for package manager - clangd language server - nvim-lspconfig, required for navigator.lua - navigator.lua for enchanced IDE experience. This is a like adding a sugar to coffee. - completion-nvim OR nvim-compe for enchanching autocomplete & dropdown menu suggestion. - nvim-treesitter for better syntax highlighting. - telescope.nvim for amazing extensible & configurable fuzzy finder, you can also use fzf if you want. - Any custom color scheme you want (preferably one that supports tree sitter, like aurora )