snac.daltux.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Ich hab die #IDE gewechselt 😇 Bin von #neovim auf #helixEditor umgestiegen. Sehr spannend 😀 Viele Tastenkürzel sind (für mich) intuitiver und die Einrichtung ist bei Weitem mit viel weniger "Gefummel" verbunden. Mal schauen...
:wq
It's not arbitrary—it's hardware history. The ADM-3A terminal had arrows printed directly on those keys.
ESC was also where Tab is now. Vi wasn't designed for ergonomics, it was designed for the keyboard that existed.
EDIT OK thanks to @r1w1s1@snac.bsd.cafe I'm now at 39 lines long. 🤣
.kshrc side by side in vim and vi. I do like a splash of color and do enjoy the command completion though so I guess I will tinker with n(vi) further. #viuIf you're an nvi user what other tips or hacks are there that I should know about ? I don't suppose there is some magical way to theme it ?Undo the last change made to the file.
If repeated the u command alternates between these two states.
The . command when used immediately after u causes the change log to be rolled forward or backward depending on the action of the u command.
uIf you're an nvi user what other tips or hacks are there that I should know about ? I don't suppose there is some magical way to theme it ?Undo the last change made to the file. If repeated, the u command alternates between these two states. The . command, when used immediately after u, causes the change log to be rolled forward or backward, depending on the action of the u command.
Well fucking shit motherfuckers. Vim & Neovim are both contaminated with LLM slop.
I mean, I can just use ed. Or roll back Vim to an old version and never let it update? Fuck.
I do have a new Mac coming, so I could just commit to BBEdit, tho that's less optimal for code editor. Assuming siegel hasn't done something stupid?
Ha ha I could finally switch to emacs with vile binds and then NOTHING will work.
Fucking fuck darkest fucking timeline.
https://hachyderm.io/@AndrewRadev/116175986749599825
#vim #butlerianJihad
Because of slop concern, @drewdevault is forking Vim to make Vim-classic with the laudable goal of "not changing anything"
https://drewdevault.com/2026/03/25/2026-03-25-Forking-vim.html
What’s funny is that I’m, at the same time, toying with "vis", which is Vim without a lot of things I don’t use (tabs, file browsing, network, GUIs…).
https://www.brain-dump.org/projects/vis/
In the removed list, the only thing I use heavily is EX mode. So I must investigate how they replace it.
#vis is much more than light-#Vim.
I would argue that it is much more powerful than any #Vi-compatible editor because of the extreme power of structured regular expressions (from #Plan9 sam(1) http://doc.cat-v.org/bell_labs/structural_regexps/se.pdf) and native support for multiple selections.
Den Artikel Feier ich, aber #vim habe ich bisher nie länger als ein paar Tage nutzen wollen.
Wer nutzt vim lieber als andere Editoren?
Vim spielerisch lernen: Fünf Spiele für den sicheren Umgang mit dem Texteditor | c't Magazin https://www.heise.de/ratgeber/Vim-spielerisch-lernen-Fuenf-Spiele-fuer-den-sicheren-Umgang-mit-dem-Texteditor-11174558.html
In #tmux, a "horizontal split" pane window places the panes side-by-side via "Ctrl+b %" or ":split-window -h".
In #Vim, it's a "vertical split" by executing either "Ctrl+w Ctrl+v" or ":vsplit".
No wonder I'm always confused.
Is it a horizontal split because the windows/panes or horizontally placed, or a vertical split because there is a vertical line separating the windows/panes?
Drew DeVault has started a fork of Vim 8.2 he calls "classic": https://drewdevault.com/2026/03/25/2026-03-25-Forking-vim.html
The goal as I understand it is both to avoid AI slop, but also some newer features that may still be young enough to require active maintenance. He's expressed the intent to keep up with security issues and bugfixes, but otherwise avoid new features.
It could be a good option depending on how much you use post-8.2 functionality.
Do I need to move away from gVim/#Vim? I'm not sure, but we're in this game to try new things, right?
Is it worth it to move from Vimscript to Lua?
Feature freezing vimscript and implementing Kuroko scripting?
https://codeberg.org/NerdNextDoor/evi/issues/46
That's a no from me then. Think I'll just be sticking to what I know which is Vim.
I've been scouring the web for peoples opinion on #EVi and I'm seeing a lot of unfair assumptions and judgement for a project forked 3 days ago.
Don't mind if I vent for a second? Please read.
🧵
New post: Neovim Crash Course for Sysadmins
Not a beginner's guide. This covers the things you still get wrong after years of Vim - efficient navigation, why your paste lands in the wrong place (and the one-key fix), YAML indentation workflows, quick macros, and what Neovim's LSP actually gives you for infrastructure work.
Written for people who edit configs and playbooks all day.
https://blog.hofstede.it/neovim-crash-course-for-sysadmins-the-20-that-solve-80-of-the-pain/
EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.
hard-forked vim at release 9.1.0 (Jan 2024)
https://codeberg.org/NerdNextDoor/vim
maybe we can get a group of people behind this??
Fuck AI.
Made a pull request to small-hack/open-slopware to add #VIm to the list.
https://codeberg.org/small-hack/open-slopware/pulls/38/files
Until this is resolved, I'll be using console Vim, which does ship with Bluefin Stable.
I generally prefer gVim because I use the system clipboard a lot, and it's slightly easier with a GUI app. I also use the mouse a bit. That's the kind of Vimmer I am.
I can make it work with console #Vim, and that's probably better for me in the long run.
I would have moved to #Neovim GUI #Neovide, but my .vimrc does not work, and it would be a heavy lift to re-create it.
#tersoftware atrasado mas a galera aqui já explodiu com informações sobre #neovim e #vim então decidi trazer um editor que tenho usado especificamente pra arquivos grandes e finalmente um editor com vim motion que n precisa de um plugin e a UI é realmente intuitiva.
Ele também tem algumas coisas bem legais de agente de AI.
O ruim é a falta de extensão, pessoal é bem cuidadoso pra n virar a casa da mãe joana (vscode).
Sim estou falando do Zed.
Ah tem arquivos de log que no neovim por causa do tresitter demora séculos pra abrir enquanto no zed abre em um tapa. Tudo bem que é uma puta idiotice tentar abrir arquivo .lcov de cobertura de teste de projeto gigante...
Ah e ele é bem malandro pra lsp, mcp e agents sendo tudo built in, e já tem debugger funcional pra Python e Node/Deno.
Eu uso #neovim pq funciona mas o #zed é o que tem me empolgado, vi até que estão trabalhando em preview pra jupyter notebook
#TerSoftware (Editores de texto)
Vim
Não sou desenvolvedor, mas adotei este editor pela ergonomia e universalidade dos atalhos em outros softwares que adotam suas convenções (os "vim-like"). Um exemplo é o Obsidian, que conta com uma configuração "Atalhos de Teclado Vim". Além disso, se o seu navegador usa as teclas "J" e "K" para descer/subir a página e "/" para abrir uma pesquisa, isso foi inspirado no Vim.
Abaixo, um vídeo tosco e sem som que fiz para demonstrar como o Vim funciona:
vi, ou vim ou, recentemente na minha máquina, debxp do export EXINIT='source ~/.config/nvi/nexrc'
EXINIT is the standard ex/vi init variable, works across nvi and traditional vi implementations.
Just make sure ~/.nexrc and ~/.exrc don't exist, otherwise nvi reads those first and ignores EXINIT. #Vim #nvi #XDG
Thank you for your reaction. We both love the choice we have in the flavour of Vim we can run.
When I started with BBS debugging and management many, many decades ago, I felt blessed that with the Waffle BBS port to dos a port of vi was also included. It did not help me on the Amiga 500 I {still} have, but of course there was a vi implementation on the Amiga too. I did not know that Bram (had written / was writing VIM already).
The POTS phone lines were horrific in my country (SR / SA) so vi was the only usuable editor to work on the BBS back and front end, since I only had a 2400BPS modem on that machine.
In the beginning I mostly used `:i` entered my text in config files and <ESC> as fast as possible to make sure crappy characters did not get into my files, then did `:wq` to exit
When I later learned about Bram Molenaar's awsome creation of VIM I was hooked.
IMHO everyone should learn VIM / vi basic editing since vi will always be installed on a Open Source OS.
I can understand why you love neoVIM. What's important is that you have choice and a smooth workflow covering decades
Have fun!
#Vim #VimMasterRace #neoVIM #tips #tricks #handy #features #Vi #EMACS #editor #text #freeBSD #ghostBSD #BSD #Linux #OpenSource #POSIX
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
I'm like the very worst #vim user. I've used it for a quarter century and maybe understand a tenth of its abilities. XD
I'm absolutely addicted to the vi-style modal controls for editing, as it feels like a superpower, like you're becoming one with the editor. Everything else about vim/neovim seems rather inscrutable to me, and I honestly found WordPerfect 5.1 (1989) easier to use. :/
Honestly, the people who write #TUI applications for linux and other Unixy OSes should seriously look at 1980s #DOS applications. They were actually easier to use, learn, and master, and I'm saying that as someone who hated DOS. XD
#Vim 9.2 Is Out with Comprehensive Completion, #Wayland Support, Diff Mode Improvements, and More https://9to5linux.com/vim-9-2-is-out-with-comprehensive-completion-wayland-support-and-more
Amongst other changes Vim now adheres to the XDG Base Directory Specification, using $HOME/.config/vim for user configuration.