:set color=blue

That’s so evil, and given Enterprise’s cancellation mid season also: perfect

Excel mostly, csv wasn’t much of a standard and thus it’s horrible to work with. We can fix that with a parquet importer and exporter!

Friends don’t let friends use csv in 2024. Excel needs a good parquet importer and exporter today. Ya hearing Microsoft? Quit pissing around with recall and build something useful!

Keep them bottled up at least

What would you replace it with? There are lessons to be learnt from the web, but to “fix” it is much harder

Bonus trek for you!

Seems fine with anarchy to me

So Konsole rocks. Yakuake a great addition. But I’m a big KDE fanboy

Alacritty is also pretty fun, combined with openbox / LXDE

But for the $dayjob it’s Windows Terminal which is easily the best thing Microsoft has released in decades when combined with WSL

It’s more advice than a complaint. I run on one setup. Linux terminals. And neovim has to beat that for me to switch

For me vim is one of those things that just works. It’s ever present, reliable, and dependable. The simplicity of it mirrors the unix way and my usage of it is so closely wrapped in screen, /tmux, bash, gnu-coreutils, and a few terminals over the years that any change is going to have me asking ‘why?’ essentially. So a command line flag allows familiarity of existing tooling to really sing, and I suspect offers far more compatibility than the suggested fix too given the length of the windows addendum to the guide

And totally agreed about out in, I use Arch btw. And I’m not in a hurry to switch to nvim either, I tried and switched back pretty quickly. Pathogen is still an amazing plugin system, leveraging my git and bash knowledge to boot

Excellent, TIL. It should be bash scripts though. Setting strange write modes and obfusticating paths, combined with a set and a let (now having to go learn the difference) isn’t something I would recommend to anyone.

Add alias vim=nvim --vimrc-compatibility to your ~/.bashrc would be my prefered migration path

It broke vim compatibility with this one change. That is super easy to support for painless migration. A real no brainer imo. The docs don’t explain your easy fix either. The key to making change faster: make it easier for people

It fucks about with locations too much for my liking

Nope. Still on regular myself. Pry my .vimrc and .vim/plugins folder from my cold dead fingers

He ain’t wrong. Replacing X11 wasn’t a great idea and not invented here was all over Wayland, especially with the Mir proposals. SystemD also gets this accusation but people seem to like working in it/with it, and so doesn’t get the level of criticism now.

It will be really interesting to see if Wayland maintains momentum over the next few years, or if it’s own tech debt will cripple it. Ideally we want to see if we can bridge the Android divide in the GUI space imo, which Wayland may have more potential to do

Excellent. Am a good manager

Why would you quit vim?