schmonz.com 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.
Advanced Programming in the #UNIX Environment
Week 5: The Editor
In this video lecture, we look at the required feature for a full-fledged programmer's editor and illustrate some of the core functionality by example of #vim. This includes basic motion commands, setting and moving to markers, using folds, and the integration with build tools, such as the compiler, debugger, and 'make', all of which we will cover in the next videos.
How has your editor usage changed in the age of AI and vibe-coding?
What are the things that you're using your trusted editor the most for these days?
Seriously, if #nvi got word wrap and rock-solid unicode support, I'd never give #vim a second look. 😄
I mean, syntax highlighting is pretty, I guess, and baked-in spelling checks is nice, but those two features (unicode and word wrap) are really the only ones missing from making nvi the perfect editor for me.
(Obviously not hating on vim. I think it's fantastic. But sometimes a basic pocket knife will do everything you need it do do, and you just don't feel the need to carry around a full swiss army knife.)
I'm never sure whether to enable vim's auto-indentation feature or not. It can be a bit annoying with some code that wasn't written so nicely. OTOH, consistency.
Is anybody using the VIS editor?
I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.
(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.
Sigh at ensloppification of random software you use. Soon you discover that #Vim maintainers consider it a good idea to use black text on blue background now. In dark theme.
I checked #evi afterwards. Packaging systems depend from software having version numbers. evi has simply not got any released versions at all, yet.
This is not something that is a #FreeBSD problem, really. Every packager, from Debian through the FreeBSD people to me, will face the same fundamental problem, and it's nothing that we can do anything about. It's entirely at the feet of the people who forked the software to stick a release version label on something.
https://codeberg.org/evi-editor/evi/tags
The VIM Classic people did their first version (8.3.0) back in June.
For the #HelixEditor I added a couple of `gq` keybindings that work like #Vim to reflow selected text:
[keys.normal.g]
q = ":reflow"
[keys.select.g]
q = ":reflow"
#NeoVIM on #Debian after I upgraded a Debian machine is coming up with some very poor colours when syntax highlighting is turned on.
It turns out that the default colour scheme is a lot plainer than it used to be in the days of syncolor.vim. Changing the colour scheme to something non-default like 'shine' shows that the syntax highlighting is all still working. It's just mostly picking from a palette of black and white in the default colour scheme.
I've been hit a couple of times by Control+Q and Control+W. The latter is habitual for either switching windows in VIM or erasing the last word in a terminal session.
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. ;)