I think this was needed years ago, or perhaps in an environment I
had years ago. Doesn't seem to be necessary in environments I use
lately (iTerm on Mac OS X).
Homebrew runs `brew update` before every fucking brew command? No
thank you. Also, after reading `man brew` I found there are some
other options to tweak for security and performance, like disallowing
HTTPS→HTTP redirects and using less cores to compile stuff (running
four make jobs on a system with two real cores? WTF, Homebrew?).
I noticed a blog post pointing out that resized images usually end
up looking a bit dim or blurry. He suggested some different unsharp
settings, and they do produce an image with more detail.
See: https://even.li/imagemagick-sharp-web-sized-photographs/
This sometimes results in a bit of overhead in image size but allows
images to be loaded in a much more user-friendly way.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
I prefer pkgsrc, but the packages are only updated once per quarter,
so if something is broken you won't get a fixed version for a few
months, or if you want some new upstream release you have to wait.
Installed homebrew manually in /opt/brew because of Mac OS X's system
integrity protection since 10.11.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
These are needed by password store (pass) when editing passwords,
and they are not part of the user's PATH by default.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
Easier to use different nodejs versions and have "global" packages
that don't need root to install.
See: https://github.com/creationix/nvm
Signed-off-by: Alan Orth <alan.orth@gmail.com>
Stripping metadata from the image saves 20–50KB, and the only reas-
on I kept it in the first place was for the color profile (which is
unnecessary on the web anyways).
Signed-off-by: Alan Orth <alan.orth@gmail.com>
gm's manpage says RGB is the default so there's no need to specify
this. Furthermore, the W3C says that sRGB is the default color space
for the web anyways, so it's pointless to embed a color profile.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
pkgsrc doesn't provide a `vimdiff` wrapper, and it's just `vim -d`
anyways, so we can just alias it and then use the vim from pkgsrc.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
The coreutils in pkgsrc 2015Q2 is broken for now, so we can't use
dircolors. Instead, manually hardcode the LS_COLORS, which was gen-
erated from dircolors on a system with coreutils using:
$ dircolors -b ~/.dircolors.ansi-dark
... and then export CLICOLOR=1.
Signed-off-by: Alan Orth <alan.orth@gmail.com>
