Tim Pope

The core of this is that empty text objects in Vim behave weird. If you press `di]` on an empty pair of brackets, for example, it doesn't update the register...

Why not just have 2 different targets? There's no shortage of them. A concise prompt does sound slick.

I read it but I don't have time to fix it.

I like the idea, typing `\r` feels awkward, and I'm not sure what `o` is a mnemonic for.

So `fo+=a` is super aggressive. If you type something, it messes up text. If you paste something, it messes up text. If you indent something, it messes up text. Why...

Appears to only happen when the word in question gets wrapped, but yeah, a valid bug.

Ages ago this was a feature. See 06b055ef2f8d8c9e8189b26c3a9d6e5b63ed904d. I ended up removing it because just opening the root URL was absurdly low value. Version number ups that value a teensy...

There's an experimental feature where it will prompt you for the file to create with `:set confirm`.

Yeah it does still work, but only for things defined as projections (which can be confusing, and why I still consider it experimental).

Can't reproduce. What are the values of `'shiftwidth'` and `'softtabstop'`?