Will Vim survive the death of the keyboard?

I found in my notes an idea for an article I've written down in 2018. Guess I'll never get around to writing it anyway. Here are my (unedited) notes on the topic

* Will it happen? (neurointerfaces) -> When will it happen? Why didn't it happen already? Does coding has to change first? (Source code as a text is not the best possible option).
* What's the state of using Vim without the keyboard now? Touch screens (surprised by how useful it is), people with vision problems.
* Vim *feels* fast only because you're doing more things at a time (actions per minute) compared to your usual editor (mainly changing modes). But it is *actually* fast, in other sense though (less strokes, no clicks - more value).

Update: thanks for the lively discussion! Main takeaways for me are

- I overestimated the technological progress I'm going to see in my life time, so I can safely invest further into keyboard stuff.
- Both keyboard and Vim are tied to text and that has lived way longer. Any adapation of Vim to another "media" would be drastic, so the answer to my original question seems to be "no", but the spirit of Vim could be preserved somehow.

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

Is there any simple plugin where Vim is used along with an external language through jobs and channels?

I was reading into this: brammool/vim9: An experimental fork of Vim, exploring ways to make Vim noscript faster and better. and Bram raised very valid points about interfaces which give a further shareable insights on why developing Vim9Script, which I fully support.

However, I am wondering if there is any plugin that uses Vim in combination with some program written in some any other language (python, lua, ruby, Go, Java ...) where you can clearly see distinct .vim files and e.g. .py files and that use jobs and channels to communicate as Bram suggested in his excellent Section?

The simpler the plugin, the better it is :)

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

Vim issues on macOS 26.2 with Bash/zsh configuration.

I have a macOS 26.2 running with regular vim. My Bash/zsh is configured to have basic vi enabled. So far it's working well.

The only class of issue I'm running into is some commend will try to launch into VIM for some reason, not STDOUT.

Anyone experienced this before? here's an example

~> man top

Vim: Warning: Input is not from a terminal

^CError detected while processing /Users/xxxx/.vimrc:

line    1:

Interrupted

Interrupt: Press ENTER or type command to continueVim: Error reading input, exiting...

Vim: preserving files...

Vim: Finished.

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

Rust indentation noscript issue

https://github.com/vim/vim/issues/18974

Basically the Rust indentation noscript doesn't seem to be well maintained and it's caused one noticeable issue already (from what I could find).

I've opened an issue on github and the noscript seems to be pretty hard to get right, a fix was attempted but it caused more issues than it solved so it got reverted.

If anyone here knows VimScript and would be willing to fix the noscript that'd be pretty cool (I'd learn VimScript and do it myself if I didn't have college exams coming up).

Thanks :)

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

Vim is composable
https://www.matem.unam.mx/~omar/apropos-emacs.html#vim-is-composable

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

Advent Of Vim Day 25 - How To Quit Vim
https://youtu.be/w58XDY06UkE?si=Z9rcm8D4ljlwhyi7

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

Use a visual/operator mapping to check any Python code snippet for errors on the fly without further set-up
https://gist.github.com/Konfekt/f26f3759c857b683a9a9e27a6915bc9e

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

Unicode Headers for Markdown

https://github.com/Voltron369/markdown-headers.vim

default:

H1: ＦＵＬＬＷＩＤＴＨ，　ＡＬＬ　ＣＡＰＳ
H2: Ｆｕｌｌｗｉｄｔｈ，　ｎｏｒｍａｌ　ｃａｓｅ
H3: 𝔻𝕆𝕌𝔹𝕃𝔼𝕊𝕋ℝ𝕌ℂ𝕂, 𝔸𝕃𝕃 ℂ𝔸ℙ𝕊
H4: 𝔻𝕠𝕦𝕓𝕝𝕖𝕤𝕥𝕣𝕦𝕔𝕜, 𝕟𝕠𝕣𝕞𝕒𝕝 𝕔𝕒𝕤𝕖
H5: NORMAL FONT, ALL CAPS
H6: Normal font, normal case

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

If you're using a minimalist vim, what does your vimrc look like?

* Are there plugins for something that vim can't do by itself, but you could not live without?
* Do you use LSP? Completions, auto-indentation, live-linting?
* Which options have you set and with which values?
* Have you setup an alias for starting vim with options?
* Do you use vim for tasks other than code and config editing?
* If so, do you use any specific options or plugins for those other tasks?
* Are you using a theme that barely anyone else seems to be using or even your own?

How are you making your minimalist vim setup work for you?

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

How would i do this in vim at a similar speed

https://reddit.com/link/1q3y8ao/video/afwe1sx1qdbg1/player

I just found this screencast i took maybe 2 years ago "showing off" a fast edit.
I have since then transferred to using vim/vim-bindings, and i was wondering how one could redo this in a similar speed with vim. My first instinct was the regex
`s/\\v\^(.*) .*/"\\1",`
But this most definitely took me longer to write than it took me to complete the edit in the video.
I have also previously seen someone using emacs doing very similar conversions in a particularly fast manner, so i imagine there must be a better way to do this in vim than a regex.
Any tips?

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

Wrote a Blog Post on Vim
https://bladeacer.gitlab.io/portfolio/posts/vim/

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

I want to create coding sessions youtube videos for my channel.

Iam creating coding videos for my YouTube channel, and I want to know if there's a way I can stream text into a file in Vim to show a typing animation. It takes me a lot of time to write code, and recording live sessions consumes my bandwidth. Instead, I would prefer to have my finished code streamed into a file whenever I press any key, so the code appears gradually and creates the illusion that I am actually typing. When I pause without pressing any keys, no new characters should appear in Vim, allowing me to explain what I have done or what I am going to do next. Basically, the text already exists in a file but is invisible, and it only appears as I press keys.

Also i would like the vimnoscript to remember where i left off like say if i close the file to create another file or should i just avoid this and instead use :term for terminal or even open another file with :vs or add it to buffer. i hope you get the idea.

Has anyone ever done this before or something similar.

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

Are you using tabs?

With buffer navigation using :bn and :bp I don't see use cases for tabs. If you're using them, how are you utilizing this functionality?

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

Hierarchical movement across braced blocks

In nests of {} based blocks, how to navigate to inner {} from outer {} and vice versa?

For example, in code like:

Stuff stuff () {
//ancestor
//stuff
//stuff
...
{
//parent
//stuff
...
{
//child
//stuff
...
}
}
}




Also, another thing that crossed my mind, suppose you are editing or using code from other people with different indents than yours, what do you do then? Edit vimrc? Temporarily set indents to matching size?

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

Coding session in vim (sort of)
https://youtu.be/MGS39vd6mRk

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

Coding session with vim (sort of)
https://youtu.be/MGS39vd6mRk

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

Do I have to learn the home-row style of typing in order to be truly efficient?

I play a lot of video games. Things get heated, and over time I gained the ability to type profanities at 120-130wpm at 95-100% accuracy (tested on monkeytype) and getting back to the movement action (WASD) quickly.

The natural placement for my left hand is SHIFT & WASD.
When alternating between w and b in vim, I often have to shift my arms or stretch my fingers a little, it's not as efficient as using ring finger for w and pointer finger for b; I use middlefinger for w and my pointer finger for b.

When I try to get used to (alternating) skipping words with w and b, it kinda gets just a tiny bit annoying.

I'm a beginner at vim motions. Is this a significant problem that I have to fix or not? I think it would cause alot of friction if I learn to type with the traditional home-row fingers placement.

Not to mention, we are supposed to use t f / alot right? So, do you guys think the cases where I have to alternate between w and b justifies re-learning my keyboard fingering style?

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