note.nvim VS neorg

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.

[https://github.com/vhyrro/neorg

Link: https://github.com/vhyrro/neorg Extra GIFs: https://github.com/vhyrro/neorg/tree/main#camera-extra-gifs ​ Neorg is a tool designed to reinvent your life's organization at a modern, unique way. Use all of the latest shiny Neovim features to provide the best possible note taking experience. Right off the bat let's ask ourselves the most important question: why Neorg - why not something like org mode? I'm gonna be real, I don't like org mode. The org format is ugly, it's difficult. Complexity isn't about how complicated the medium is, it's about how expressive it is; this is precisely the problem we're solving. We want this to be the true organizational plugin for Neovim, going head to head with emacs in a battle of the titans. ​ # Features * New and revised norg format - take everything that's good from markdown, everything that's good from org, reimagine it, piece ‏‏‎ it together - almost like it's some form of art. Little ambiguity, lots of expressiveness, perfect for writing. It's so syntactically predictable in fact it's almost like a programming language ;) * TreeSitter Parser - remember when I talked about shiny features, this is just one of em! Thanks to said parser (link here) Neorg can have a deep understanding of your documents, allowing us to almost read your mind. Having such a parser opens up almost endless possibilities, and we're excited to continue improving on the technology. * Logical keybinds - Neorg currently doesn't have much keybinds, but we can guarantee that the keys we will provide by default will just "make sense", following suit in Neovim's keybind methodology. Keys form a language, one that you can simply think of, not one that you must memorize. * Completion source for nvim-compe - that's not it though! We don't just support a completion source, how boring would that be? Our completion source works tightly with TreeSitter to provide contextual completion based on where you are in the syntax tree. Getting shivers just thinking about it. Smart completion for everyone! * Language injection for Neorg code tags, get syntax highlighting for any language that's supported by TreeSitter :D * Workspaces - group together your .norg files and jump between different workspaces like a wizard thanks to the :Neorg workspace command. * Insane extensibility - it's easy to throw around such a buzzword, so let me reiterate: we're not joking, we're serious. Neorg is built on top of a very configurable and powerful backend, one built on top of modules. Modules are pay-for-what-you-use pieces of code that build the foundation of Neorg like lego bricks. They can interact, they can be hotswapped, they're fully independent (unless you don't make them so). This means you can throw away any features you don't use with absolutely no performance penalties whatsoever. * The Wiki - we want to make this plugin accessible to both users and developers. The wiki is your informational powerhouse, I can guarantee that most of your questions will be answered there. # Why the "road to 0.1" in the title? Neorg is nowhere close to being finished - in fact, we're only just getting started. We've spent 3 months making this plugin and we're only just starting to get serious features. Neorg 0.1 will be the first official release of Neorg - one that will provide you with all the basics to kickstart you on your note taking journey. If I had to make an estimate, we're currently somewhere in version 0.0.7 or 0.0.8. Not too far off from that beautiful 0.1, eh? We're always open to support, bug fixes, and creating issues on GitHub. If you have any knowledge in lua then hop along for the ride! # Expected features for 0.1 (not present yet): * Telescope.nvim integration to fuzzy find anything - .norg files in workspaces, headings, subheadings, markers, drawers, you name it. * Magical time snippets. Type +date to insert the current date, +now to insert the current date and time, +tomorrow to insert tomorrow's date etc. Also provide a +custom to allow you to specify your own date and time format. * Smart indentation thanks to TreeSitter * Even more autocompletion and editing supports * Maybe custom LSP triggers upon entering a code block with a defined language? * Smarter syntax highlighting in some scenarios * Video tutorials on using Neorg and its format # If you want to look even further into the future, here's what we plan on doing for version 0.2: * Tangling support - execute code blocks, see their output. Easy peasy. Flex on your friends with configurations written in .norg too * Native image support - yeah. We'll either use hologram.nvim or we'll create some PRs to improve it beforehand if no development happens in that area * Pandoc engine for file format conversion - if there's someone smart enough to do it. I'm certainly not. * Snippet support * Beginnings of a table editor * UIs * Ability to upgrade .org files into .norg files (either through the pandoc engine or through a custom implementation) At first you may be a bit confused, this is normal! There's no real tutorial on Neorg's format yet, however you may be interested in reading the specification as I make the tutorials :) If I don't respond to comments it's probably because I'm sleeping. I hope y'all have a blast trying and testing this new technology out just as much as I am having a blast making it. Much love, Vhyrro

I like to use vhyrro/neorg plugin. Readme is self-descriptive.