lyda

I've been using vimwiki now for two months thanks to this video. Also vim-calendar. Fantastic. It's been amazing.

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.