Windows isn’t Unix and as someone who has spent a career coding for Unix and Unix-like systems, Windows just isn’t useful to me. I’m perfectly happy with Linux, FreeBSD, OpenBSD or even OS X or whatever it’s called this week. The code I write generally runs on any of those and things behave as expected.

I’ve never really used Windows, but I have had to deal with the problems caused by developers using Windows. EOL chars, not putting a trailing EOL char in a file (postconf no like that), a lack of understanding of various Unix things. It’s kind of tedious to deal with, but that’s more the devs than Windows.

This is amazing!

One quick tip: sort -u films.txt > films2.txt

If you only include the filename you could just feed it to vlc.

That’s a pretty shitty outcome. And the LoucheBear character doesn’t seem to contribute anything of value, just ignorant abuse.

All the more reason to buy your computers from companies that support Linux in the first place - like Slimbook and System 76.

It happened due to Microsoft disabling an Internation Criminal Court lawyer’s Office 365 account. This has spooked EU officials that a rogue US administration could harm it and there’s a stronger push now for digital sovereignty.

My solution to this is to make my vimwiki remote be the wiki repository for my primary vcsh homedir repository on my own gitlab. So I can edit it in there.

Long ago I tried a cygwin based openssh server in Windows. Permissions were a real issue.

And then

git ci -am "Addressed performance issue in flurbin module

The flubin module was designed as a successor to the flurbar module
which took in...
[...500 line essay on the history, problem and solution deleted...]

Hopefully this will fully fix the issue discussed."

for a one character change that adds an additional, and unrequired, semicolon.

Just because you can do something…

js console: document.querySelector('.pointers').hidden=true

ls /usr/share/man/man?/* will show you all the man pages on your system. I used to pick ones at random.

Originally there were a number of manuals. Manual 1 had user commands. Manual 2 had system calls. Etc. You can type man NUMBER intro to read about that manual. You can also use man -k or appropos but I’ve also just used grep. These days they’re compressed so zgrep.

The mouse pointer background is kinda a dick move. Good article. but the background is annoying for tired old eyes - which I assume are a target demographic for that article.

Good answers. I like these. I like the more than one command in a file, that will work. And yes, should have read the source!

Well, nix would be an entire operating system. This is just for a build system to specify the versions of the tools to use.

I love that fossil exists. I would never use it, but I’m glad cranks have something to work on.

I have never heard proper reasoning for squashing commits. I don’t think sanitized history is useful in any context. Seeing the thought process that went into building something has been repeatedly useful in debugging things. It’s also useful to me as a software engineering manager to help folks on my team get better. I could care less how “pretty” git log looks, but I care a hell of a lot about what git diff and git blame tell me. They help me figure out where issues actually are and how they came to be.

This is yet another reason not to squash commits.

I use vcsh to manage my home directory - including but not limited to dot files. Written a number of posts on it over the years: https://phrye.com/tags/vcsh/

Projects like that make me want to create a uucp network and so I can email a bang path address to get my patch.