Normal Mode

imho

Nightmare when I try to Vim on someone else’s computer now, though.

I’m not sure whether I agree with this or not, but I think Bill Joy probably does.

Hah! mT was one I was planning on submitting to you!

The exact command without -q would open up a file descriptor or temporary filewith the output of the ripgrep command, which wouldn’t be that useful.

But if you tweak the bash command to just pass multiple paths then Vim will populate the arglist with them e.g.

vim $(rg -l needle)

Yep! On the Apple keyboards for various regions (I’m in the UK) it’s a key under the Escape key.

Full line completion is one of those things I miss so much when I have to use another editor.

Here’s one I learned from romainl. A use for select mode!

nnoremap § *``gn<C-g>
inoremap § <C-o>gn<C-g>
snoremap <expr> . @.

Vim’s -q argument allows you to prepopulate the quickfix list directly on startup.

e.g. using ripgrep via bash’s process substitution:

vim -q <(rg --vimgrep needle)

Vim has a built in MRU list.

Use :oldfiles to view it, and e.g. :e #<5 to open the fifth entry in the list.

Is this cool? https://gist.github.com/sedm0784/4443120

Please do write about it. I would like to read that!

I think that’s the most effusive praise I’ve heard for a multicursor plugin from someone with your Vim bona fides. What kind of task do you find is better handled with multicursors?

Hi

I was fast enough to use Vim at work without a productivity hit after about a week of playing with it in my lunch breaks.

It was *years* before I could use it in a crisis with someone looking over my shoulder.

Heredocs Can Make Your Bash Scripts Self-Documenting Comments

Heredocs Can Make Your #Bash Scripts Self-Documenting | Hold The Robot
https://holdtherobot.com/blog/heredocs-can-make-your-bash-scripts-self-documenting/

#Markdown #vim #documentation

Is it a plugin? Could be that it’s doing something that breaks macro playback somehow. I have a vague recollection that there are some things that don’t work during playback without workarounds, although the only one I can remember right now is that undo doesn’t work normally.

What are your exact keystrokes?
I just tested with the built in dictionary completion and if I mashed <C-K> a few times to pick an option and then pressed Space the completion wasn’t included when I played it back, but if I hit <C-Y> to accept the completion instead then the macro worked correctly.

Getting out of the emoji search thing on the ios keyboard is much harder than exiting vim

Whatcha gonna replace it with?

In Xcode 16 they’re finally good enough that I didn’t immediately switch them off again, but I still trip over missing/inaccurate things daily.

An alternative technique in bash or zsh, using process substitution instead of a pipe, is:

```
vim -q <(rg --vimgrep search)
```

What's your favorite vscode/emacs/vim plugin or script that you've written for yourself?

Bonus points if it's something you can't morally make into a mass-installable plugin, like it executes untrusted code or needs a hardcoded secret or something

(Please remove hardcoded secrets before sharing)

There are a *bunch* of great g-commands (have a skim through **:h g** and see what you find) but the most life-altering for me were **g;** and **g-** & **g+**.

I’ve got good(?) news for you: https://github.com/andmarti1424/sc-im

And you can do this! https://normalmo.de/vimlife/

In Xcode’s Vim mode? What kind of things are slowing you down?

Having already learned it, I enjoy using it for editing prose, emails etc. but I’d say it’s not *as* useful in that context. If you have a spare half hour, try out vimtutor and see if you find it compelling.

Two prints with :q! Printed on them

A close up of a screenprint

A macro image of the halftone of a screenprint

‘There is always a way out’ is my first design making a screenprint. Made for the vim users among us. Or for those who just need a reminder on how to exit the editor.

Made with fluorescent pink and blue ✨ an edition of 10. Available in my little webshop! https://shop.wontfix.me/

#screenprint #vim

Apologies for the drive-by suggestion, but have you tried using Vim’s *cgn* for this? Sounds like it might be a bit closer to your current workflow than macros.