vim-pencil VS vimwiki

Another option is vim-pencil.

Both of the above are naturally integrated into billions of nvim plugins. I store files in a cloud folder to have access to them on my phone. There are apps that allow you to work with notes written in markdown like Obsidian. You should have a way to quickly go to your writing files. You could use telescope-project.nvim, startify shortcuts, or any other session plugin. I would also recommend setting up LSP for writing. You will be able to have diagnostics, "code actions" on wrong grammar, allowing you to add words to dictionary and suppress rules. I use ltex_extra.nvim for this. There are also a good set of plugins for writing by one author, just check them at the bottom of the pencil page.

Two years ago, I did nanowrimo in Vim with a whole suite of plugins:

- https://github.com/preservim/vim-pencil

- https://github.com/junegunn/goyo.vim.git

- https://github.com/junegunn/limelight.vim.git

- https://github.com/vimwiki/vimwiki

It was fun, and the setup is almost identical to iA Writer which I appreciate. I even had it all on my phone with Termux!

Last year I just did it in Markdown in VSCode in "zen mode" which also worked pretty well. It was definitely easier to setup than Vim and had better highlighting of bold/italics/etc.

You may like vim-pencil if you use markdown. It adds several small conveniences around word wrap options, among other things. Note also that the author of pencil includes many useful links in the README for conceiving vim as a tool for prose. My workflow is based on pandoc and bibtex. But that part's not vim- specific.

The most efficient way to do this is to install the vim-pencil plugin--when you go to edit the file, say :Pencil to activate the plugin, and it'll reformat the text on the fly while you're editing it. Basically it makes vim act less like vim and more like a word processor.

You may find vim-pencil usefull. The readme has some good links.

preservim/vim-pencil: Rethinking Vim as a tool for writing

vim-pencil sets undo points at the end of every sentence (and other things) although you might not want to install a full plugin just for that.

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.