For a while now, I’ve been wondering how to combine entr
(which automatically runs commands on file changes)
with the way I setup project validation (both for CI/CD and for local developer usage) with Makefiles.
The best thing I got so far is the
validate_continously target in
What’s the simplest way of encrypting a folder in Linux?
gpg, it seems.
I finally integrated isort into my toolbox.
I think that the job of changing code files belongs to the editor (or an IDE),
so I made Vim run
while the import order enforcement in a project is done via Makefile
(which can be run the same way by developers and the CI/CD pipeline).
I’ve created a script that should 1 set up a fresh Manjaro with all the software and configuration that I want in a workstation. It can also update the setup on being rerun. Now I have two laptops that behave and look the same 2, and it’s easy for me to maintain that state. Oh I wanted that for a long time :)
I’ve put a tweaked version of my previous post (Moving a Linux installation to a new drive and encrypting it) up on Manjaro forums as a tutorial. You can check it out here.
I needed to change out the drive in my light laptop for a bigger one. Of course I didn’t want the hassle of OS reinstallation 1, so I decided to move my Manjaro installation from the drive to the other. My install was, regrettably, unencrypted 2 - I wanted to fix that during the move.
Finally doing some scripting today. I noticed that there are some python-virtualenv-related commands I run often (in my tmux-based “IDE”), so I automated them away to shave off some keystrokes.