neorg VS vimwiki

[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.

No, Neorg does not use the same markup as Org-mode. They use their own specification that is specifically designed to be different from Org-mode spec.

https://raw.githubusercontent.com/nvim-neorg/norg-specs/main...

Furthermore, each item you have listed as a benefit to Org-mode is in fact capable of being done in Markdown via plugins for neovim, and probably other markdown editors, like Loqseq, Roamresearch, or Obisidian, much in the same way you speak of plugins that interface with .org docs.

https://github.com/wthollingsworth/pomodoro.nvim

https://github.com/Myzel394/easytables.nvim

https://github.com/vimwiki/vimwiki

So, my suggestion is that before dismissing a comment regarding a plugin that is unfamiliar to you, is to read its spec, and then try to understand why people would be perhaps dismissive of that tool, especially when it chooses to conflict with existing, more popular choices.

you might want to look at how vimwiki does markdown tables https://github.com/vimwiki/vimwiki

I've been thinking of setting up a note taking enviroment in neovim. I've been searching around, and plugins as vimwiki, and nabla.nvim are great choices for me. I'm using Notion right now because of the great commands that brings that make the note taking pretty enjoyable. But the dividers, or putting background to text are features that I don't wanna lose, if possible.

I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim.

I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also, while the extra features afforded by Obsidian don't really make a difference during the writing process, I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something.

Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markup than in a rich text editor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content.

I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future.

[1]: https://github.com/junegunn/goyo.vim

[2]: https://vimwiki.github.io/

I use vimwiki.

Hey folks, I have been using Neovim for the past 2 years, don't have any complaints, however, I really want to give Emacs an honest try but not really sure where to start. I want to do basic text editing, programming and something similar to vimwiki (https://github.com/vimwiki/vimwiki)

How about learning vim and using vimwiki ?

What, we're talking about wikis and vim, and not mentioning vimwiki?

https://github.com/vimwiki/vimwiki

I tried a whole bunch of personal wikis over the years (I see Zim has been mentioned, that's one of the ones I remember trying) and this is the only one that stuck.

I have created full on programs to systematically created screenshots with the game emulators with RetroArch. Also an automation tool to use a preexisting program named chdman that converts files into a needed format (also unpacking from archives). A little Python script to create a recents list of files for Vimwiki. I also created a program to access 🌈 emojis 🌈. I wrote my own GE Proton downloader and manager. Hell even the window manager I am using on Linux is written and configured in Python, Qtile. I wrote one or two plugins for it and the entire configuration is written in Python, meaning I can use functions, modules and every logic of Python to enhance it. It's Awesome.