vim-be-good VS vimwiki

Sure! The first thing I did was follow this video: https://www.youtube.com/watch?v=w7i4amO_zaE

This is ThePrimeagen's 0 to LSP, Neovim RC from Scratch. In this video he performs a clean installation of Neovim and goes step by step adding the things he considers essential. This was very important for me to acquaint myself with how things work, how to install plugins, how to define custom key maps. I remember the first times I tried using Vim, I couldn't figure out how to get Nerdtree to work. This video made me realize I just lacked the knowledge of how Vim config works.

This video was such a good start because It provided me with the tools to continue my exploration of Vim autonomously. In a week I was already able to install new plugins and tweak them using Lua config files the way I specifically wanted. It's such a cool experience!

Keep in mind that both the author of this video and I use Neovim, which is a fork of Vim. As a text editor they both function essentially the same. The difference lies on the config files and in broader UI capabilities by Neovim. While Vim uses Vimscript, Neovim prefers Lua, although Neovim is fully backwards compatible, so you can choose to use Vimscript for your configuration if you want as well. This also means that Vim plugins just work with Neovim!

The docs are also a huge source of knowledge for me. In the beginning I resorted to :help key-codes a lot when defining key mappings.

To learn the Vim motions, which is the most challenging part of using Vim, I suggest you find a cheatsheet online and refer to it all the time. One very cool plugin that will help you get comfortable with Vim motions is ThePrimeagen's VimBeGod: https://github.com/ThePrimeagen/vim-be-good. It's a set of game-like exercises to practice the motions. This is also pretty cool and helped a lot: https://vimsnake.com/. It's a classic snake game where instead of using arrow keys, you use HJKL. And speaking of arrow keys, one thing I did very early on was disabling them (or, in reality, remapping them to noop) in normal mode so I was forced to move around the text using Vim Motions.

At first you will get frustrated because your brain will need some time to rewire in a way to absorb all the new abstractions Vim presents. It's a whole new logic of editing text. The most important thing is to stick to it and you will be surprised with how fast you end up picking things up. Of course, don't expect to be crazy fast in a few weeks. But right now, after a little over a month, I no longer feel that discomfort using Vim anymore. I suppose I'd still be faster on VS Code, but I really want to master Vim, so I'm sticking with it and I feel a constant improvement.

If you're not familiar with Vim, I'd encourage you to download a few Vim cheatsheets, the VimBeGood extension[1] and practice navigating code in Vim.

[1] https://github.com/ThePrimeagen/vim-be-good

For Neovim, then this Hardtime plugin will help you change the habit, and this vim-be-good from Primeagen helps learn vim motion. TJ DeVries is also a good source to learn.

A game for learning vim, in vim: https://github.com/ThePrimeagen/vim-be-good

I'm trying to NeoVim (and vi) in general having never used it. I decided to start with VimBeGood but I can't get it to launch a game. I've gotten the plugin installed but when I run :VimBeGood it just shows the screen saying "to play a game delete that line." I deleted words and noob but after that I'm lost. Nothing happens. What did I do wrong?

I recommend vim-be-good for practicing this

There are plugins like https://github.com/ThePrimeagen/vim-be-good that can help with practice.

I found https://github.com/ThePrimeagen/vim-be-good to be kind of a nice way to build some muscle memory for vim.

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.