I made a note taking plugin with the new image integration.

https://redd.it/1uvjsxq
@r_vim

What is missing in Vim compared to Neovim?

In my opinion:

1. Tools for helping scripts/plugin development. Lua has LSP, linters, etc. Vim9 has... nothing. It seems to be back to the beginning of the 90:s when it comes to develop in Vim9 language, in-spite it is very nice.

2. A Native Vim9 DAP. There is vim-spector but that is mostly Python,

3. Plugins: for example, I got copilot from work and the Vim9 and Neovim copilot-chat plugin are not even comparable,


What else?

https://redd.it/1uvha3g
@r_vim

Does a plugin like this exist?

Hi, sry first time poster, hope its ok to just ask my question like this.

Question:

Is there a plugin for vim that can replace/ shows the code behinde for a function so I can follow the code flow better.

Why:

I have the task to maintain some legacy codebase, some written in python some written in c#, but its a lot of spagetti code. I know i can jump to the definition, but this gets confusing really fast. So I want to read it top to bottom, a option to hide states for if statements would be nice. Loops should stay the way they are.

Any hint for direction would be nice, thanks for reading.

https://redd.it/1uwbzik
@r_vim

What's one Vim command you use every day that beginners almost never know about?

I'm trying to move beyond the basics and really learn the parts of Vim that make experienced users so fast.

What's one command, motion, text object, register, macro, or workflow that's become second nature for you but rarely gets mentioned in beginner tutorials?

Bonus points if it's something you now use multiple times a day.

https://redd.it/1uxcrpx
@r_vim

VimTendo - An arcade game that teaches you Vim commands
https://atticarun.itch.io/vimtendo

https://redd.it/1uxldc3
@r_vim

GitHub - ubaldot/vim-markdown-extras: Modern note taking plugin with markdown focus
https://github.com/ubaldot/vim-markdown-extras

https://redd.it/1uyb5og
@r_vim

Musings on Vim from an Emacs luser

I've used mostly vanilla Emacs for about a decade. I'm thinking about switching to Vim because the values that made me appreciate Emacs have changed.

What I loved about Emacs is that it's essentially a Lisp machine packaged as an application, which makes Emacs a legitimate target platform. The primitives provided by Emacs are probably better-suited to extensions than those provided by Vim. But over time, I've come to two conclusions:

First, the editor-with-extension-language paradigm is outdated. Plan 9's Acme editor showed that an editor need not impose a particular language on its users. It can instead expose a language-agnostic API via a filesystem (or socket), thereby permitting any program in any language whatsoever to extend the editor. This is, in my opinion, the way forward.

Second, I want to use my operating system. I don't want to use Emacs replacements for what my operating system or supporting software already provide. It is silly for there to be a 'man' mode for man pages when the 'man' program works better. I want all of the tools I use to make the fullest use of the hardware and OS. That is simply not possible with Emacs.

Obviously, none of these complaints point to Vim as a solution. I would, in fact, use Acme as my daily editor, but for my mode of working, accessing remote systems on a slow network connection, neither a graphical editor nor mounting a remote filesystem are options, so using some editor in tmux is my best option, and for that reason, for now, Vim may be the more performant option.

https://redd.it/1uzcl5i
@r_vim

TIL @: repeats the last command and @@ repeats the last macro.

Holy cramole!

Where has this been all my life? I found out about these macros while doing a bit of coding that involved a lot of running things like :w | foo ./%. After typing : followed by up a zillion times, I realized that there had to be a better way. A quick Google and I was enlightened.

If this is a TIL for you, lemme know. If you have another lovely tip or trick, please share too.

https://redd.it/1uzuidc
@r_vim

A tiny Vim plugin for everyday git operations, inspired by lazygit
https://github.com/ubaldot/vim-git-box

https://redd.it/1v0m01f
@r_vim

Are you a vim or a gvim person?

Which one do you use (more)?

View Poll

https://redd.it/1v1jn8c
@r_vim

Repeat character to position, rather than number of characters?

I want to pad a section title line in a config file with `=` up to a specific character position (specifically, column 64). Since the title text is of inconsistent length, a normal <n>i <char> won't do it.

Example of a title line formatted the way I want it:
;===== reset machine status ===================================

https://redd.it/1v1s2de
@r_vim

Is there anything like explainshell.com for vim? Not just using :help <command>, but breaking apart complex commands?

The title should say everything needed. I was thinking that having an explainshell equivalent for vim would be neat.

https://redd.it/1v2ckrx
@r_vim

VimTeX v2.18
/r/neovim/comments/1v3bvnq/vimtex_v218/

https://redd.it/1v3bvyx
@r_vim

Are we slowly forgetting that you can just "speak" vi?

You don't need much more than the core grammar. You know how :source file executes Ex commands linewise from the file? Well, :source! file executes commands as if you were typing them and ends each line with a CR for you.

Opening vim to your favorite layout is just a matter of writing down the keystrokes you keep typing each time:

:edit ~/.vimrc<CR><C-w>v:edit ~/.tmux.conf<CR>
:term top<CR>ggVGy:enew<CR>:read!date<CR>p
<C-w>s<C-w>Hi"hello world"<Esc>

and `source!` it from somewhere. If you want to save all the `Shift+.,` typing, `<C-v><C-w>` would directly insert ^(`\^W`) in the buffer and keep it looking exactly like what you would.

Vi is a language. Even better, vi is a homoiconic language in that the code that is executed is identical to the representation of keys on your keyboard plus minimal syntax for control-characters.

You do not need to learn lisp to feel the power of '(insert-new-line) when you are a single o away from executing OR representing your intention to open a new line for insertion.

To grok further, hunt down the legendary StackOverflow answer and meditate for a little longer than usual.

https://redd.it/1v39ur5
@r_vim