@b0rk_reruns Thanks for posting these. I'm learning so many useful tips from them.

@b0rk_reruns

Wait! It gets better!

On MacOS, you also have access control lists AND extended attributes! (GAG!)

@b0rk_reruns I’ve been on Unix/linux systems since my early 20s AND I still need to look up the permissions commands. Thank you for this.

@b0rk_reruns

Each section has an intro page. Different systems may have different numbers for sections. "man 2 intro" "man 4 intro", etc

@b0rk_reruns ... leading to the age-old question "why is this the only system on which the help command isn't spelled h-e-l-p?"

@b0rk_reruns Someone really needs to explain Cache-Control max-age and If-Modified-Since to whoever looks after pulling in podcast feeds at #Apple and #Amazon and #Spotify!

https://www.earth.org.uk/RSS-efficiency.html

@b0rk_reruns
I use
set -o errexit -o nounset -o pipefail
Because it is easier to understand.
Also, it took me ages to remember which option is which option is which and `set -eu` is not very intuitive.

@b0rk_reruns if you're scripting rather than tapping raw bash into the terminal, this should give the same behaviour

"#!/bin/bash -e -u -o"

@b0rk_reruns Good job in learning Linux concepts!

@b0rk_reruns ctrl-u deletes backward until beginning of line,

@b0rk_reruns I also use `Ctrl+U` a lot to clear the current input.

It works great, specially if you misstype a password field and want to start over, which happens to me quite often.

@b0rk_reruns@social.jvns.ca "so I put version control in your version control, so you can control the version of your version control"

@b0rk_reruns How could I miss out on dig -x ... thanks! Glorious :-)

@b0rk_reruns having an explainer that shows "explain plan" for a sample query could be a logical follow up. One could argue that it's too complex for your audience. But you have the skill to present complex things in a way people can actually understand.

@b0rk_reruns the ORM I use allows composing query concepts in any order technically, but in practice it almost always starts from a "from" base concept (like, DV[:some_table] is "SELECT * FROM some_table", but filtering with WHERE and only some cols could be DB[:some_table].filter(some_col: 'value').select(:col1, :col2)). Might be one of the unconscious reasons I like it, since it maps to this better mental model of building SQL statements

This is syntax that rdbms clients could support. It’d also help with column name completion if you start with FROM.

@b0rk_reruns
@b0rk

@b0rk_reruns ip has a colour option? Why didn't I know that before...

@b0rk_reruns
Nice! Is there an IP v6 version of it?

@b0rk_reruns And not many people know why it's called the 'sticky' bit ...