@PacoVelobs @Zenie @amelliug @eliasebner

A few points (as an Emacs user for over 40 years):

* evil and Emacs co-exist just fine. When in evil mode, you can still use most Emacs commands.

* I use evil mode only for text writing and editing (prose and code). I don't try to shoehorn evil/vim into other modes such as dired and gnus.

* The modal approach of evil helps avoid RSI issues (for me at least), not needing any key chording. This was my original motivation for trying evil mode.

Note: I was a vi user before I started using Emacs, back in Unix v7 days.

#emacs #evil #vim

@Zenie
Well, that's kind of my point.
I mean, it's better to embrace #emacs than to be frustrated by #evil's missing feature IF you're a proficient #vim user.
If you've been using #emacs for 31 years, I guess you don't need #evil at all.

Or maybe I'm missing something here ?

@amelliug @eliasebner

@amelliug And, as a hard-core #vim user who gave #emacs various tries, I urge you not to. Evil mode lacks many basic features and it's a really poor implementation. I'd recommend embracing the software as it is and not trying to badly replace your old one.
@eliasebner

I folded, I'm looking into emacs (as a vim user).

#emacs #vim #coding #programming

#NetBSD could use a #librewolf or #ungoogled-chromium package; as well as #evi / #vim-classic

#Vim is back!

#Neovim #DHH #AIslop

👋@vopam

https://lazybea.rs/vim-is-back

For a long while I fiddled a bit between #vim, #neovim, then plain. I was tired of fiddling with configs and differences between systems. Then I discovered the #Helix Editor. What an amazing experience 🚀 Just a little bit of configuration and it works like a charm. Yes, a few key combinations are different, but the transition is going smoothly. I also love the integration possibility for #Rust, which is of great help while learning the language.

Pour commencer, il faut préciser ce dont j'ai besoin : quel est mon usage d'un éditeur de texte ? Je crée/modifie principalement des fichiers Markdown (notes, supports de cours, textes longs comme des articles), mais aussi du balisage verbeux (HTML, XML, JSON), un peu de programmation (CSS, Python, JavaScript), et du non formaté (courriel). Je versionne la plupart des fichiers texte (avec Git). J'ai besoin d'identifier la fiabilité de mes textes (correction orthographique), de visualiser rapidement la structure (coloration syntaxique), et de pouvoir suivre les modifications (différences affichées directement dans l'éditeur de texte). Et je pense que c'est à peu près tout.
#vim

La première chose que je modifie ce sont les couleurs par défaut de l'interface. Cela peut sembler futile, mais cela (me) facilite la lecture de l'interface textuelle. J'utilise depuis pas mal de temps les thèmes de Catppuccin, il y a une déclinaison pour Vim : https://github.com/catppuccin/vim L'installation locale des thèmes Catppuccin est expliquée très clairement : le plus simple est de récupérer un seul fichier qui contient toutes les déclinaisons, incluant les colorations syntaxiques pour différentes syntaxes (j'y reviendrai plus tard).
En termes de configuration ça donne ça (les lignes commençant par " sont des commentaires) :

" activer toutes les couleurs
set termguicolors

" utiliser le thème Catppuccin Mocha
colorscheme catppuccin_mocha

#vim

Toujours dans les lignes. Par défaut les coupures des chaînes de caractères dans le cas de lignes dont la longueur dépassent la largeur du terminal sont brutales : ça coupe où ça coupe, donc en plein milieu d'un mot.
Pour éviter cela il est possible de passer un paramètre qui améliore les coupures, ce comportement me convient :

" coupe les lignes de façon plus élégante (au mot)
set linebreak

#vim

D'ailleurs si vous vous demandez où on peut trouver TOUTES les options qui peuvent passer dans ce fichier de configuration, il faut ouvrir Vim et ensuite c'est dans `:help options`. Et là 🤩

Et un petit rappel : toutes ces options peuvent être renseignées dans le fichier vimrc, mais peuvent aussi être modifiées dans le buffer courant, directement en utilisant la commande `:set`, par exemple `:set signcolumn=yes`. La modification sera valable uniquement tant que Vim est ouvert. Ce qui permet de tester des choses plus rapidement.

#vim

Je cherche alors quelques informations sur la gestion du _clipboard_ (presse-papiers en français) entre Vim et Wayland, et il existe plusieurs solutions. Je vois qu'il y a une extension tout à fait adaptée (https://github.com/jasonccox/vim-wayland-clipboard), mais je veux vraiment éviter d'ajouter des dépendances. En fouillant un peu il existe un re-mapping des commandes, mapping qui semble assez malin pour ne pas mettre le bazar ailleurs (merci à la personne qui a modifié le script original, c'est parfait pour mes usages : https://www.reddit.com/r/Fedora/comments/ax9p9t/comment/jbs8pom/), ce qui me semble un bon compromis (soyons honnête, je ne comprends pas tout). Ça tient en deux (longues) lignes, cool (la ligne qui commence par un " est toujours un commentaire) :

" gestion du copier-coller en dehors de Vim, compatible avec Wayland
autocmd TextYankPost * if (v:event.operator == 'y' || v:event.operator == 'd') | silent! execute 'call system("wl-copy", @")' | endif
nnoremap p :let @"=substitute(system("wl-paste --no-newline"), '<C-v><C-m>', '', 'g')<cr>p

#vim

Suite de mes pérégrinations dans la configuration de Vim ! Si j'ai déjà parlé de l'importance (pour moi) de modifier les couleurs par défaut de l'interface de Vim (et donc d'aller chercher un thème), il reste la question de la coloration syntaxique. Vim n'applique pas de coloration syntaxique tant qu'on ne le demande pas. Il s'agit donc tout simplement d'activer cette coloration :

" activation de la coloration syntaxique
syntax on

Mais attention : le _rendu_ de cette coloration dépendra du thème activé. Vim dispose de thèmes par défaut, et si un autre "colorscheme" est appelé c'est celui-ci qui est utilisé pour la coloration syntaxique (d'où le fait que l'utilisation de Catppuccin représente une dépendance non négligeable : 5 fichiers d'environ 600 lignes chacun).

#vim

Gratitude day 4: Vim

#SeptemberTheme #gratitude #blog #fediverse #mastodon #editors #terminals #vim
https://lazybea.rs/gd4-vim

🔹 Is there a non-slop fork of tmux?

(Similar to @nerdnextdoor 's #EVi as a fork of #vim ?)

EDIT: There is one! 💜

-> https://codeberg.org/opentmux/opentmux
by @thomasadam

#tmux #coding #programming #terminal #cprogramming

"I don't have enough time to learn Vim" - most people.

No. You don't have enough time to not learn Vim.

Once you start using Vim, something will really change in how you use your computer. It will become the most efficient way you edit text. You will learn to love text files. You will learn to love the extensibility of plaintext. You will learn to use command line programs. You will learn to optimise your whole system. Vim is where it all begins for you.

This needs saying more!

#vim #nvim ♥️

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

@gee L'est marrant ton éditeur. Ça ressemble pas à #vim, je connais pas...

Tabs vs spaces has always been a controversial topic. Thankfully, #vim isn't biased in any way.

To convert spaces to tabs, use `:set noexpandtab`, then `:retab!`.

Convert tabs to spaces with:

:set expandtab
:set tabstop=4
:set shiftwidth=4
:retab

Je commence un fil qui va décrire pas à pas ma configuration de Vim, from scratch. Les récents événements autour de Neovim m'ont convaincu qu'il m'est nécessaire de bien savoir ce dont j'ai besoin. Je retourne à Vim (historique de mes usages : Vim 2022-2024, puis Neovim 2025-2026), et plus précisément à Vim Classic (https://vim-classic.org). Tout cela est partiellement inutile ou totalement futile (rapport à l'actualité, toussa), MAIS ça me permettra de mieux maîtriser mon environnement d'écriture (et de moins regarder le monde s'effondrer). Je ne garantis pas d'aller jusqu'au bout, parce que tout de même c'est la rentrée universitaire (et qu'il y a d'autres/trop de priorités). Je vais prendre mon temps, et peut-être que ça fera un ou plusieurs billets de plus pour ma série sur Vim (dernier en date : https://www.quaternum.net/2023/04/21/vim-quelques-commandes-pour-ecrire-et-editer/).
#vim

@notNapoleon I don't know. Given the amount of #vim forks before #nvim took off, I don't see a future with a successful #neovim fork.
One thing you're right about is that I should look into RMS stand on stuff I care about.
@Jonizulo

@PacoVelobs @Jonizulo

I'm in the same boat. Mainline #vim and the various other forks still don't seem to have native LSP support, which is a requirement for me.

#emacs has the features I would need, but migrating because of the odious political opinions of a core maintainer onto a project that still has RMS as a core maintainer doesn't really feel like an improvement.

I'm hoping we see some reasonable response from the rest of the #neovim team, but I'm not holding my breath. If a community fork with a sensible code of conduct actually gets off the ground, that's probably where I'll end up.

@Jonizulo I'm seriously considering the #emacs switch because of the late events. Even after ~15 years of heavy #vim then #nvim usage, it looks better than other alternatives.

@pmakholm As a long-term #vim and then #neovim user, I can't imagine sticking to a #vi-like editor without the #nvim features and ecosystem TBH.
So I'll, very seriously, add #emacs to your list.

After the "fun" I had in the Neovim Github tracker this week, I poured a ton of love back into my old vimrc.

I also updated my website theme to pair up with the new vim colorscheme I'm enjoying.

And lastly, I redirected my financial support for Neovim back into Vim.. I even own some of the official merch. I'll drop it off at a donation center the next time I go to the dump.

Life goes on, man.

#neovim #vim

I have donated to #neovim, used this editor for many years. I can also drive-by mob, swirl from one mindless vomit-party to another, like the pacific garbage patch. Guess I'm nuanced like that.

So what's your favourite editor with #vim motions? I still use #vscode, but also classic vim more and more just because it's everywhere. Also been looking at #zed maybe.

I can’t understand why justinmk won’t remove a stupid endorsement from a white supremacist from the website of #neovim

I think I give #vim-classic another try or try again to do my general editing in #emacs (and not only for my org-files). I tried #helix but after my vacation it feels hard again.

@glyph I don't understand why would #vim need a successor. It works perfectly well and is still developed.

[lien] eh: a minimalist vi-like editor - Lobsters (codeberg.org via r1w1s1) #gik #cli #vim

I have this #firefox extension called #vimium.
Of course, I'm a #vim nerd and I thinks it's awesome.

But here is why it's also great to have it even if you don't use vim : press `f` and have all the clickable links showed to you.
Looking for this "Continue without accepting" dark pattern ? Here it is. Want to unsubscribe from this list you never subscribed ? Here it is.

"Accessibility" for the ables in those dark ages.

Also : fuck you if you coded those dark patterns.

@tuban_muzuru Yeh I asked on #vim and someone there suggested scrollbind - it's good! It would be even better if it could do line diff (ie without clever alignment) - but it does handle those big files easily!

Now it needs to percolate through to the quarterly package repo, which'll take another month and a half, but at least that doesn't need any manual intervention.

https://www.freshports.org/editors/vim-classic/

#VimClassic #vim

@monospace I use $_ often. The other one not really because my shell is configured with: set -o vi and not emacs like many by default

#vim rulezzz

@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.

[Veille 📣] Chapter 1: Introduction and Installation - LazyVim for Ambitious Developers
https://lazyvim-ambitious-devs.phillips.codes/course/chapter-1/

Tutoriel sur l’utilisation de LazyVim pour NeoVim.

Lien vers cette entrée dans ma veille : https://liens.declosure.ch/shaare/mvV8WA
Toute ma veille est disponible ici : https://liens.declosure.ch/
#neovim #tutoriel #vim #LazyVim
#links #liens #veille

#linux #commandline #vim
Wenn dass der Sven Guckes noch gesehen hätte ...

Alt...

A person turning off a fuse.

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

@omgmog while you could have done:

vim scp://user@myserver[:port]//path/to/file.txt

😏

#vim

Oyez Oyez !

Vimistes, NeoVimistes, voir même Vistes ou EVistes ? Emacsists, Nanoïstes, Edistes...

À #Grenoble, le mardi 27 octobre à 19h à #LaTrubineCoop se tiendra un évènement de renom : un #TupperVim https://tuppervim.org/ !

Ne préparez rien, venez avec un truc à qui miam ou qui glou et pointez vous au bon endroit https://www.openstreetmap.org/node/2782756987#map=19/45.184322/5.721137 à la bonne heure.

#vi #vim #nvim #neovim #evim

I've been using #vim daily for personal and professional reasons for almost two decades now.
Yesterday, I "sharpened the saw".

Of course, I know more about the tools than 15 years ago. But I find beauty in the fact that I still learn valuable ways to enhance my workflow a couple of times a year.

It's not about discovering a new thing.
But about finding a way to better use it.
I like to be better than my last week self.

#nvim #neovim #quickfixlist #locationlist

Grab a stretch of unicode while inside #vim

:py3 import vim;vim.current.buffer.append(" ".join(chr(i) for i in range(945,970)))

α β γ δ ε ζ η θ ι κ λ μ ν ξ ο π ρ ς σ τ υ φ χ ψ ω

@slothrop

Not sure whether you want to tell a story or are looking for an actual solution here.

But reading the doc about the various registers #vim and #nvim work with might help you a lot.

```
:help registers<CR>
```

Sharing for lulz 🤣 #linux #vim #unix

Alt...

In this meme we see an elderly veteran in a dress uniform looking emotional and on the verge of tears, with the text that reads: "Me, having fought in the Vim–Emacs wars, seeing juniors vibe-code in Cursor”.

I just discovered that you can give #neovim the URL to a remote file and it will automagically fetch it. How long has that been a thing and why did I not know about it earlier ?

#nvim #vim #today_i_learned

New blog post: "The motion that changed everything"

➜ https://monospacementor.com/2026/06/the-motion-that-changed-everything/

#Learning #Vim

After reading @rl_dane's post, I wanted to share how I manage my #bookmarks, and add some quick #notes using #neovim.

#editors #vi #vim #shell #fediverse #bsd #linux
https://lazybea.rs/ils-bookmarks-and-notes

@hisgolu Added a link to your post.

I do use those two quite frequently too.

I ❤️ #vim

@rl_dane

Was surprised to find vim-classic@testing available in Alpine Linux today.

apk del vim && apk add vim-classic all the things!

#Linux #AlpineLinux #vim

C'mon #vim folk, REPRESENT!!

@hyde

#vi #nvi #neovim #nvim

So far for June's carnival, I got only ... @rl_dane 😔

Any #vim #neovim user that would like to write about it?

#opensource #linux #CLI #Shell #editors #mastodon #fediverse #bsd #programming #terminal

Couldn't seem to get #VimClassic to compile on #FreeBSD.

But then I realized the only thing I used it for is sncli, because it does something funny with the terminal when it hands it off to nvi, such that the cursor becomes invisible. But then, it's just a !reset to fix it, so I might as well just stick with nvi. ;)

#vi #vim #nvi #TextEditors #PlainText

#OverUnder 070 with @edphones

He shares his thoughts about #Podman, #Ubuntu, the #Cloud, #Thunderbird, and, #Cucumbers.

he also replied to @elena's question.

And, we got a recommendation for two #books. And, for the first time, one about #vim ... Finally!!

#bloggers #bookstodon #book #blog #fediverse #bloggers #mastodon

https://lazybea.rs/ovr-070

@JesseSkinner This is actually the main point of the #TupperVIm, local meetings around #Vim and derivatives.
We always start by re-explaining how to move efficiently before diving into advanced stuff.

Learning vim motions is so over-focused on the hjkl arrow keys at first, but it's funny because once you learn the rest of the motions, you barely use the hjkl keys at all, because there are better/easier ways to move around. #vim

What are your "uncommon" Vim/Neovim shortcuts?

For example, I have a shortcut that displays the MDN documentation of the HTML tag under my cursor.

#Vim #Neovim

@rl_dane

Fun fact: The :x command was added to ex/vi in 1980 because :wq did too much. Horton copied the name from hed.

https://github.com/dspinellis/unix-history-repo/blob/BSD-4_3-Snapshot-Development/usr/src/ucb/ex/ex.news#L382

@rettichschnidi

#ex #vi #vim #nvi #nex #hed #BSD

Bon, il y a combien de forks de Vim depuis que l'IA a été invitée dans le logiciel d'origine ?

Je vois Vim-classic, EVI, mais encore ?

Et deux questions se posent :

1) lequel suivre ?

2) Quid des prochaines versions de Vim dans les distributions GNU-Linux ? Quel Vim proposeront-elles, ou proposent-elles déjà ? Réalisé avec ou sans IA ? (Et ça vaut pour tous les logiciels d'ailleurs.)

#VIM #iA

Dear #vim, darlin',

If you're gonna read my \.exrc, do me the kindness about not complaining about valid ex/#vi options! XD

rld@Intrepid:~$ vim
Error detected while processing /home/rld/.exrc:
line    4:
E518: Unknown option: iclower

Press ENTER or type command to continue

(I know, I know, just use a .vimrc. I'm gonna. ;)

(Also, just FYI, I haven't reverted to vim. I use vi and ed most of the time, and jump into vim for a very few use cases, which escape recollection at just this moment 😆)

@rettichschnidi @adi

I was very fond of :up[date], which saves only if changes were made, but that's #vim (and descendants)-only, not #vi.

I'll see if my muscle memory allows me to rewrite ":q; ok then, :wq" as ":x" instead. 😄
(I'm a creature of habit ;)

[lien] Vim Classic is a Vim Fork for People Who Want Their Editor AI-Free #gik #vim #ai

Submitted the patch to include vim-classic in the #FreeBSD ports collection:

bugs.freebsd.org/bugzilla/show…

Now waiting for it to be added.

If you can't wait, you can grab the patch to add it from the bug ticket and compile it for your system. If you don't want to install the ports collection, patch it and build it yourself *AND* you trust me to not be malicious: I'm temporarily making binary packages available for 14.3 and 15.0:

mirror.sonologic.net/vim-class…

#vim #VimClassic

New #blog #post: Vim Carnival Entry: "The Motion that Changed Everything."

https://rldane.space/vim-carnival-entry-the-motion-that-changed-everything.html

1224 words

cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn

(I will happily add/remove you from the chorus upon request! :)

Thanks to @hyde for the blog concept, and immediate apologies if you get trapped in a #hellthread! 😄

#rlDaneWriting #blost #vi #vim #nvi #editor #VimCarnival #TheMotionThatChangedEverything #modal #ADHD

@fabi1cazenave Hourra, le TupperVim est sauvé : le choix demeure donc entre #Vim et #NeoVim ! (voire Kako..., non ; ou Ema..., non).
Bref, il ne reste « plus » qu'à organiser ledit #TupperVim du fameux « lundi 21 juillet » (dixit & sic le site). ;-) </format=taquin> (OK, désolé, jesors)

Drew Devault has just updated his #Vim fork, “Vim Classic”, now in version 8.3.

Like Vim, but without the compatibility-breaking VimScript9, and without any AI-generated code. A sane maintenance process. This is the legacy Vim deserves.

https://vim-classic.org/news/vim-8.3-released.html

Woohoo! The first release, 8.3.0, of vim-classic (the non-slop fork of VIM) has been releases today!

vim-classic.org/news/vim-8.3-r…

I'm working on a #FreeBSD port in my spare time.

#vim

#vim pros:

I want to open a zip file that does *not* have a .zip suffix with vim's nice browsing mode. Is this from within vim the only way to achieve this?

:call zip#Browse("/full/path/to/file")

Unfortunately there is no tab completion in that string 😑

And yes, I could use symlinks:

> ln -rsf myfile.notzip{,.zip}
> vim myfile.notzip.zip

But come on...

[Quotation] "After fifteen years with #Vim and #Neovim, I honestly cannot imagine my career with a different editor at the center of it." by Caio Bianchi, in "A Love Letter to Neovim", 2026-05-26, at https://caio.ca/blog/a-love-letter-to-neovim
And of course, this means text #format tool.
Via @jpmens and cc @fabi1cazenave (for the next TupperVim).

#Vim carnival this month: "The motion that changed everything".

Write about it on your #blog, and send me a link that I will add to this post

#editor #neovim #terminal #shell #opensource #linux #BSD #mastodon #fediverse
https://lazybea.rs/vim-carnival-202606

I had Debian 13 on a 2009 Macbook Pro, which was really a too heavy load for this old machine. So I tried to remove the graphical desktop environments (I had tried several) and descended into a dependency hell ... and now I can report that it is possible to fuck up a system using the regular dselect/apt package management tools. In the end I had deinstalled the Wi-Fi drivers, the dhcp client, so no cable connection either, and even the "sudo" utility. That was the point where I gave up and did a fresh install.
I followed this blog post https://veronicaexplains.net/my-first-writerdeck/ by @veronica and now have a basic text-mode Linux computer, even with my own UI font (https://www.kutilek.de/sudo-font/) #Debian #Linux #Vim #TUI

So I was writing this ed(1) wrapper editor. To have fancier search and custom commands, all with a nice immediate Web GUI.

And then I realized nvi(1) exists.

#vi #vim @ed1conf

Trying out #nvi-1.81.6 on #Debian as my primary editor on my work box for a bit.

At first, I was sad that I could no longer

some_command |vi

like you can with (neo)?vim, but then I realized you could just as easily

vi <(some_command)

Hmmm, the lack of line selection mode is a bummer. This might have more pain points than I was anticipating. XD

Maybe I should try #vim-tiny?

#vi experts (and #vim / #nvim #NeoVim ),

What's the difference between the 0 command and the | command?

Is it just that | can take a numeric argument?