@hottradwife #vimtutor terminal app was the one who thought me #vim

https://vimschool.netlify.app/introduction/vimtutor/

most important thing how to leave vim

ESC and then :q for quit without saving, :wq is write quit

"Just remember: if you need to move between words or lines, you need to switch back to Normal Mode by pressing the ESC key.
To save the file, type the ESC key to switch back to Normal Mode then type :w. The most important: to quit vim, type :q while in Normal Mode."

Alternatively Press Esc, then type ZZ (capital Z, twice)

That saves changes and quits.

https://docs.oracle.com/cd/E19253-01/806-7612/editorvi-9/index.html

IT History - Yank & Blank | Dem hoergen Blog

#vim #emacs #geschichte #computer
hyperblog.de/hoergen/posts/202…

Die historischen Ursprünge zweier alltäglicher Computerkonventionen: Warum der Kopierbefehl in Vim und Emacs yank heißt und warum die Leertaste in Browsern weiter blättert.

I like Vim. I've used it for about two decades. I still don't know what easily half of its functions and buttons do. I really enjoy it.

But one thing that does bother me is that given the enormous density of features, and there being only so much room on the keyboard, when hitting the wrong key it is extremely likely to do something I didn't want to do, rather than merely not doing anything at all.

Usually it's hitting u for undo or o for insert new line when I meant to hit i for "go into ordinary typing-in-text mode".

Maybe I should learn to use those little lines on the F and J keys to position my hands properly, rather than guessing.

#vim

Ça y est, j'ai désactivé les flèches en mode normal dans nvim. Obligé de passer par h j k l pour me déplacer !

Maintenant, c'est dans un éditeur classique que ça va se compliquer ! 😂

Je mets en place une gym nvim quotidienne pour m'exercer et intégrer l'ensemble des raccourcis, ou du moins un plus grand nombre !

#neovim #vim

@bertrand Heu, je consomme extrêmement peu de vidéos donc je ne suis pas une source fiable.
Mais globalement pour #vim il faut faire l'effort de détecter les actions répétitives et longues (plus de six ou sept touches) et chercher une automatisation. Se forcer quelques semaines le temps que ça rentre "dans les doigts" et recommencer.
Une à une, pas plusieurs à la fois.

Petit rafraîchissement de mes commandes Neovim avec ce tuto vidéo, très bien fait : https://youtu.be/EPQG2u6Ctew

Constat honnête : j'utilise toujours les mêmes raccourcis et j'oublie les astuces. J'avais oublié que % saute de la parenthèse ouvrante à la fermante, et que . répète la dernière action.

Les macros, c'est l'exemple typique : puissantes, bien pensées, et je ne les utilise jamais. Il faut que je m'y force, je suis sûr que le gain est réel.

#Neovim #Vim

ICCF Holland Annual accounts 2024 https://lobste.rs/s/sd9ypu #pdf #vim
https://iccf-holland.org/jaarrekening2024_EN.pdf

I have like zero respect left for developers who use LLMs to write or maintain their software.

I don't even care for the reasons why they use this unethical piece of... technology.

Technology trained on data they don't own. Technology owned and shaped by fascists. Technology that sends its crawlers around the globe to suck every bit they can find to dump their models into big f***ing corp data centers. Data centers that are polluting the air with their big ass gas plants.

But hey! "Leave ethics aside". "That's how software development works today!".

I'm so sick of this and about everyone supporting this industry.

If you feel targeted, you are welcome. I have zero respect for you or your software garbage. I just wish you the worst.

#ai #llm #floss #linux #vim #gohugo #foss #fckai

For my next needless workflow optimisation, I bought mouseless.click lifetime because...fellow vim user... 😂

#vim #mouseless #linux

I've used #Emacs nearly every day¹ of my life since mid-1991. The thing is, I had to use #vi (well before #vim existed) for ≈3 months before I got Emacs — just enough time to be editor bilingual.

Also, IMO doing root stuff in Emacs is ill-advised (yes, I know #TRAMP exists), so I always use vi in a root shell.

¹ It's been 12,800 days since I downloaded #GNU Emacs 18.56 (which took ≈6 nights via #Usenet comp.sources). I suspect I used Emacs about 11,300 of those 12,800 days.

Cc: @FoxFunction

In light of the Helix editor getting a scheme based plugin system maybe even before next year, I've decided to deep dive on it a little.

I love how hard my Vim muscles carry me. Most Helix motions already feel natural. Inverting selection and action is easy to adapt to.

Helix has damn near all my boxes ticked with zero plugin dependency. The things I am missing are just shell abstractions like :vimgrep and quick fix lists (just use sed). So, I get closer to the shell.

#vim #HelixEditor

Books couldn't teach me #Vim effectively because the tool is too contextual (shell, version, scripting language). I ended up learning best by actually using it daily, integrating it with my shell, and writing plugins. But I think the deeper issue is that books can't account for constant evolution: #Vim9 updates, Neovim's ever-growing plugin landscape, different shells, scripting variations. So here's my question: is this a book problem, a Vim problem, or both?

I'm also exploring flashcards for learning #Vim9script syntax https://github.com/sevehub/Awesome-Flashcard-Decks/tree/main/decks/text-editors . How do you approach learning Vim , or any other complex CLI tool, in a way that actually gets you to power‑user level?

What actually sticks?
#vim #neovim #vim9script #lua #bash #powershell

Oh great, another article attempting to unravel the mysteries of #productivity, only to regale us with tales of a #Facebook engineer's legendary #hacks. 🙄 Apparently, if you want to be like Bob, all you need is a custom #Vim setup and the magical ability to transform #caffeine into code. ☕💻 Spoiler: productivity is still an illusion, but at least we got some sweet emoji usage out of it. 🙃
https://frantic.im/mirage/ #myths #engineer #coding #HackerNews #ngated

In #vim, gU is an *Uppercase* command. gu is a uowercase command

Fast #scheme programming with #vim (vim-classic) and no extras
needed, not even Quack. ~/.vimrc for Chicken Scheme:

colorscheme koehler
au BufNewFile,BufRead *.sld setl filetype=chicken
let g:is_chicken = 1
let g:lisp_rainbow=1
set guioptions -=T
au BufNewFile,BufRead *.scm setl makeprg=csi\ -quiet\ %
map <F5> :make<cr>

Edit any .scm file, then press F5.

getting back to writing some #Rust and feeling like I'm starting to get into the flow. I think the breakthrough was stopping struggling with IDEs yelling at me after every character I type with squiggles and highlights, and just coding in #Vim for now.

Working on implementing a #CRDT for my binary tree-shaped #PKM outliner.

Took some time to learn about #P2Panda as I'd like to use it for #P2P offline-first outline syncing.

#RustLang #OfflineFirst

Underrated #vim advantage: when using vim mode in every other editor, you don't have to learn new keybindings all the time. Shortcuts are always the same. Weird and counterintuitive, but consistent