note-refactor-obsidian VS vimwiki

I know I can create a page by selecting the link and pressing [[ and/or use Note Refactor

Could Note Refactor plugin help with what you need to do?

Happy to share some of what's been working for me. Some of this is stuff I'm actively using, some of it hasn't quite made it into the "day to day use" yet, but I've been experimenting with. (Random personal advice: Never let your note taking tools feel like using them is work, that's the first step towards not keeping notes!)

- For fans of "outline workflows" Outliner is excellent. A whole bunch of outline/indented text movement and manipulation commands: https://github.com/vslinko/obsidian-outliner

- For easily refactoring notes that are getting too large you want to have Note Refactor. It gives you tools to easily take blocks of text and quickly cut them out into new notes. Its not magic out of the box, but its a powerful tool you can use when building workflows with other plugins. https://github.com/lynchjames/note-refactor-obsidian

- Local images is another good one, working with online content can get messy when you copy notes and then want to be able to work any where you have Obsidian synched. I've got it on my Laptop, two desktops, phone and tablet... I want to carry as much of my related content with me so having an easy way to convert remote images to local copies is a big productivity boost when making notes about content from the internet. https://github.com/aleksey-rezvov/obsidian-local-images

- For analysing the content for some useful stats there's: https://github.com/SkepticMystic/graph-analysis but this is for a relatively specific sort of analysis.

- More general and flexible analysis and graph visualisations are available from the combination of https://github.com/zsviczian/excalibrain , https://github.com/blacksmithgu/obsidian-dataview and https://github.com/zsviczian/obsidian-excalidraw-plugin ... in short query your notes and note metadata like its a database, build reports and data visualisations, and then excalibrain is a whole thing built on top of that power.

- Dynamic embeds of outside content are available from https://github.com/dhamaniasad/obsidian-rich-links and https://github.com/Seraphli/obsidian-link-embed depending on the style and use you like. While there is a built in functionality to preview the links to other notes when you hover over them https://help.obsidian.md/Plugins/Page+preview which has a demo here https://youtu.be/dmnVml_jbsQ?t=222

- And a real force multiplier is adding https://github.com/Taitava/obsidian-shellcommands to your setup. It lets you run scripts and prompt for information and really invest time in procedural automation without having to build your own javascript plugins. So you can setup your system so that when you use the refactor to cut out a new note, the automations will trigger, ask you to give the note a new heading, tags, and you have a little script that checks last modified time of the folder tree of text files, and looks at the folder of the last modified time and asks you in that popup if you want to move the new note to the folder the note you cut it from is located in. Or anything else you can imagine using outside automation and scripting tools on your plain text markdown files.

These are just a start and if you haven't already browsed the plugins at https://obsidian.md/plugins I wholeheartedly recommend it, people are adding new cool things pretty often and other plugins add new functionality that makes them worth checking out if they were previously not something that you found interesting. I do a read through of the plugin list probably at least once every month or two just to see what's new, and more often if I'm experimenting with changes to my workflow.

If visualization were important to me, in your position I would split the note on headers, and then link between the new notes.

u/Arthurpmrs you might like this plug-in, helpful for those files that get too long, or your original organization patterns runs out of steam. https://github.com/lynchjames/note-refactor-obsidian

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.