Je ne pensais pas que le site de VIM était resté dans les années 2000 😅 !
https://www.vim.org/
I can't wait for vim.pack. I've been using vim-pathogen for fifteen years. #vimhttps://neovim.io/doc/user/pack.html#vim.pack
Stefano Marinelli
boosted
Stack Overflow Survey 2025, Developer tools, Category IDE: #emacs isnt even listed 😪 But #vim is on place 5. Even newcomer #zed seems to be more popular than #emacs.
https://survey.stackoverflow.co/2025/technology#most-popular-technologies-dev-envs-prof
Me learning vim.
I think I have to switch #Vim completion plugins soon. Choosing between nvim-cmp and vimcomplete, probably gonna go with nvim-cmp. This is gonna be like a whole Saturday afternoon project.
What #libre#IDE (integrated development environment for programming code) would y'all want to coalesce around using, supporting, and developing? Asking especially for coding websites and applications with #PHP, #JavaScript, #CSS, and #HTML but #Python, #Elixir, #Rust, and #Go would all be great for us @agaric too.
emacs will do all of this without shame on whatever system.
alcinnz
boosted
Learn Vim progressively
https://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/
Learn Vim progressively
https://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/
Hey fedi friends, what are the differences in USES and config options listed at #freshports for a #FreeBSD #port? I am familiar with USE in #Gentoo #Linux, which seem to be the config options here? For #Gentoo it is very common to use different USE settings for a packages, but for #FreeBSD I read from porter's handbook there are not many USE items and they looked different from the term in #Gentoo. I am still trying to wrap my head around what is happening that whenever I try to build a port, like #vim or #git in tiny flavors, I constantly noticed #Perl #Bash #lua #Rust #Python and all other seemingly unrelated stuff get pulled in. #BSD #RunBSD #Unix #FOSS
Recently started learning #morsecode , although it's completely useless to me. Sometimes it helps to understand why things developed like they did when you go back in time, when remote communication started. And I love having a #lowtech fallbacks.
It's like learning #ed in order to understand concepts of #vim.
I just upgraded #OpenBSD from 7.1 all the way up to 7.7 one release at a time in a #KVM VM running on my laptop #Debian. At first #tcsh and #vim were giving coredumps. I realized I did not even run #pkg_add even once so I did a doas pkg_add -u. After that all is fine and everything was like before. #OpenBSD is truely awesome!
#BSD #UseBSD #RunBSD #unix #FOSS
I've been using Tridactyl[1] for a long time now for keyboard-driven vi bindings in the browser and yesterday decided to check out the alternatives, thinking maybe they provided some interesting features too.
I looked them all up: Vimium, Vimium C, Vimmatic, SurfingKeys and the result is: I am in awe of how advanced Tridactyl is in comparison to all of them.
Native messaging*, comprehensive ex command mode for commands and settings with live-previewed completions; hint-based visual selection, copying and focus; support for local filesystem text-based configuration; binding sequential browser actions to custom commands; tab group commands; actually launching (neo)vim to edit text areas; ...to name a few!
* do bear in mind the security implications of native messaging, as noted by the developers themselves, but you can have most of the functionality without it
The more I think about it, the more it seems to me that in this day and age with all the modern threats having a text editor that is capable to not only connect to the Internet, but also install some code packages from repositories (and probably do dependency resolving) is a recipe to catastrophe. Sooner or later.
It's probably one thing when you use a curated list of half a dozen addons that you can even personally peruse (or even contribute to). It's a whole other thing when you use some huge "distro" with probably hundreds of packages that also receive constant updates you cannot possibly control.
It's mostly about #Emacs, of course, but #vim is fully capable of it too. I won't even mention the likes of #VSCode.
We had a fair share of supply chain attacks in the recent years (npm, pip, even xz in some way). No reason to think no one's gonna use this channel of attack.
Maybe it's just my fibs. But there is some uneasy feeling about the fact that you edit, perhaps, extremely private, personal or sensitive texts while your editor runs some background code doing who knows what. It's one thing to trust people who wrote vim or Emacs and a whole other thing to trust a hundred other unknown parties at the same time.
Dumb #vim trick:
Have a bunch of files open in multiple windows and want to jump to the first (or last) line in all of them?
:windo 1
or
:windo $
and done.
If you use tabs instead of windows, you could use :tabdo instead.
or you can jump to the next instance of /pattern/ in all open windows/tabs with
:windo /pattern
:tabdo /pattern
or the first/last (assuming you have 'wrapscan' set) with
:windo $/firstpattern
:windo 1?lastpattern
So #Fediverse, tell me - are there any Mastodon clients you really like for the desktop? Specifically, I am hoping for something with a GUI, linux native, and has support for vim motions. The stretch goal would be something cross-platform.
I'll just download a test a bunch if I have to, but hoping one of you can save me the effort, because so far my search-engine-fu is not yielding any results regarding vim-motions. (which I concede is a bit of a long shot)
I’ve been exploring a more minimalist approach in my tools lately, and part of that includes trying to use nvi more often instead of Vim. To make the transition easier (for myself and anyone else interested), I put together a simple nvi quick reference:
https://4c6e.xyz/nvi.html
It’s not meant to be exhaustive, just a practical guide to help get things done with a lighter touch.
#nvi #vi #vim #minimalism