github-orgmode-tests VS vimwiki

Each code block could be evaluated in place, with results appearing inline. Want to test JSON parsing? Write a block, execute it, see the output. Need to try different data structures? Compare approaches side-by-side with immediate feedback. This resembles the classic Lisp REPL workflow but with all the organizational benefits of org-mode. The development document became a living laboratory.

I'm a fan of Org Mode with Emacs [0] and using the app BeOrg [1] on my iPhone.

I have 3 main task files:

- todo.org for things I need to do

- backlog.org for things that I don't have to do now but should do in the future

- inbox.org for any random ideas or notes

The concept of an Inbox was taken straight from Getting Things Done [2].

I have different searches set up in BeOrg so that it is easy to view tasks from each different file.

This is definitely more complicated than a single file, but I like it mainly because it keeps my main task file (todo.org) organized. I also don't go through organizing my files that much either.

inbox.org is just a great place to dump anything, so I usually do a quick scan and either delete everything or refine it to the backlog.org.

For backlog.org, I'll usually just let things sit there and build up. After a while I'll realize that if something has been there for a long time, it probably isn't worth doing - or I already did it, so I delete it.

[0]: https://orgmode.org/

[1]: https://www.beorgapp.com/

[2]: https://hamberg.no/gtd

TIP: When asking for advice in relation to knowledge management, note-taking, etc., be sure to ask for precise details regarding commenters' solutions. There are many people who participate in these discussions who don't seem to take a lot of notes (e.g., one file or paper notepad for all of their notes!).

I have a personal knowledge base that currently includes almost 7,000 files in which I store my notes. I take notes on everything. Every technology. Every product. Every meeting. EVERYTHING.

My notes are stored in Org files that I edit with Emacs and Org mode[1]. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (which is used by alternative note-taking tools like Obsidian). For example, Org supports plain text spreadsheets[3], a feature I love.

Too many people will disqualify Org and say, "I don't use Emacs," while assuming that Emacs users choose Org because we already use Emacs. But I started using Emacs specifically to use Org, not for programming.

But regardless of which tool you end up using, consider organizing your note files using hierarchical tagging. I started using hierarchical tagging for my notes right after Wikipedia was first launched and I saw how effectively hierarchical tagging was being used there. Each Wikipedia article can belong to multiple categories, and each category can belong to multiple categories. This is hierarchical tagging, and it's worked great for my notes. At the bottom of every one of my Org files, there is a list of "parent topics", and each parent topic has a list of parent topics (excluding the "main topics", which have no parents).

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/The-Spreadsheet.html

My favorite static site generator is Org mode[1] for Emacs. Org files are written using a feature-rich lightweight markup language[2] that is much more powerful than Markdown (e.g., plain text spreadsheets). Org files can be exported to HTML[3].

The reason I prefer Org for static site generation is not because I already use Emacs. I actually started using Emacs about 20 years ago specifically to use Org mode.

[1] https://orgmode.org/

[2] https://orgmode.org/features.html

[3] https://orgmode.org/manual/HTML-Export.html

"until recently, Jupyter notebooks were the only programming environment that let you see your data while you worked on it."

This is false. Org-mode has had this functionality for over two decades.

https://orgmode.org/

Work - I use org-mode heavily for my personal project management and note keeping.

While embracing analog tools, I've also refined my digital organization using ORG mode in Emacs. The system has evolved to become more structured and efficient.

Org mode. Org mode is just great for taking notes and organizing tasks. I might write a post on it one day. If you're interested, check out Org Mode in the mean time.

orgmode seems to be a big change after using Notion. However, I fell in love with Emacs, so I wanted to use all the best things. It was easy to set up org-agenda, org-roam, etc. Unfortunately, after a while, I noticed that using a non-standard system(not Markdown) could impact my note-sharing capabilities, as well my ~work~ docs were mostly built with Markdown. So, a note system that uses Markdown. Also, I switched to VIM :)

I use vimwiki[1] just for this "diary" functionality, with different days in different files. Can browse the directory in netrw to find a day's notes, and I have scripts that let me archive old stuff. I tend to put an "x" in front of completed lines (and move uncompleted lines forward to new days) so it is easy to detect and archive unactionable or "completed" files.

[1]: https://github.com/vimwiki/vimwiki

My comparison is always with good ol' Vim Wiki[1], which still works great with NeoVim. I'd add that to the list for comparison too.

1. https://github.com/vimwiki/vimwiki

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 ?