I salute you, who can remember Vim’s copy paste commands without using a cheatsheet.

In case you haven’t heard yet …

https://groups.google.com/g/vim_announce/c/tWahca9zkt4

Bram Moolenaar has died. 😢

@prologic@twtxt.net Alright, there’s some erroneous markdown parsing going on, I reckon. In my original twt I have a code block surrounded by three backticks. The code block itself contains a single backtick. However, at least for rendering, yarnd shows three backticks instead (not sure if my markdown is invalid, though):

Sigo batallando para aprender (neo)vim. Como que no es intuitivo y uno está acostumbrado a las formas fáciles. Seguiré practicando

This looks promising - https://lapce.dev

vim inspired and “lightning-fast”. still in its early days.

@movq@www.uninformativ.de Ah, I see. I mean, it is not biggie, as normally I just reply to people, so that part works beautifully. A vi/vim script would work, but it is not universal. What if I use joe, or Emacs, or nano? Meh, jenny is awesome as is, thank you for it! ☺️

And I lost a whole story writing it in Vim by not creating a new folder first. FFS

$ cd gopherhole && vim notes/.

Vim really has the best commands for typo-fixing: r, a

Pondering: https://stackoverflow.com/questions/1236563/how-do-i-run-a-terminal-inside-of-vim

I feel like I only scratched the surface of what Vim really is capable off.

Been keeping myself busy installing and configuring vim-airline and geeknote.

@f117zz5 it’s never too late for vim