I love Vim. But it isn't perfect, unfortunately.
And one part that is particularly confusing when setting up for the first time is indentation.
This guide strives to cover what options are relevant, what they do, how they interact, and how to set them up for most popular indentation styles.
Vim has 5 options relating to (manual) indentation:
| #!/bin/bash | |
| if [ $# -lt 2 ]; then | |
| echo "usage: $0 <infile> <outfile>" | |
| echo "use TARGET environment variable to set target size (default: 128)" | |
| exit 1 | |
| fi | |
| convert -trim +repage "$1" "$2" | |
| read -r w h <<<"$(identify -format '%[fx:w] %[fx:h]' "$2")" |
Clickbait title: Improve your Git experience with this one weird trick StackOverflow hates
If you're reading this guide, it's because you're either wondering about, or have actively run into a problem with, Git's handling of line endings. Maybe you're a Windows user, or someone working on the same repository as you is, or you do development across operating systems, or you're working with tools that break operating system convention, or...
NOTE: This requires Windows 11 to work fully. If you're on Windows 10, you won't have working systemd. If you're on an older version of WSL, you should try https://github.com/yuk7/ArchWSL or https://github.com/sileshn/ArchWSL2 instead.
Jan 28 2021
I seem to have a real infatuation with unconvential programming challenges. Whenever I get to do something completely new that is at the same time simple enough to take no more than a day or two, but also far enough 'out there' that just looking up the solution is out of the question, my brain really seems to light up.
So, after rewatching [Tom Scott's video about the FizzBuzz interview question][fizzbuzz-yt], I figured a fun brain teaser would be to try and implement FizzBuzz in [Befunge][befunge], an esoteric programming language I am quite fond of.
Without much fanfare, here it is: