Dang no way? I had a terrible experience with them (tbf it was half a decade back at this point). We were in line to check in, something like 1.5hrs before a one hour flight. The line was agonizingly slow (only 2 of like 5 check-in counters were staffed), and when we got to the counter they said we were too late, missed the window for the flight. We only had carry-ons, were 3min late for their arbitrary window, and the plane still wasn't scheduled to leave for an hour or so.
We were clearly in line before their deadline, were certainly going to make it to the gate before they even opened for boarding, had no checked bags, and they made us buy new tickets. The cherry on top was that they ran flights every hour, so we bought the ticket for the next hour but the gate agent let us on the original flight we had- so they basically just forced us to pay double for our flight.
SkyTeam in general has superb service. I have in the past decade flown Delta, Air France, KLM, and Aeromexico, and all have curbstomped my American Airlines and British Airways experiences.
The service on the plane isn’t a big deal, but in my experience strongly resembles the service off it.
I have most of my shell history back to 2005(?).
Each terminal gets its own new history file.
99% of the time, I never look at it, but when I do need to look at it, it has been great. My boss once asked me: "What args and screening file did we use when we made that one-off DB 4 months ago?" Was able to check and confirm it was correct.
Or for personal use: "Where did I move that folder of pictures?"
I opted for a single history across all sessions on any given host: On my main machine, the first of 54,434 entries is timestamped 2020-08-22:12:39, while on the machine on which I do most development at the moment (it varies from product to product and release to release), the first of 34,771 entries is timestamped 2023-05-08:11:34.
For the curious, the salient .bashrc bits are:
function _setAndReloadHistory {
builtin history -a
builtin history -c
builtin history -r
}
# preserve shell history
set -o history
# preserve multiline commands...
shopt -s cmdhist
# preserve multiline command as literally as possible
shopt -s lithist
# reedit failed history substitutions
shopt -s histreedit
# enforce careful mode... we'll see how this goes
shopt -s histverify
# timestamp all history entries
HISTTIMEFORMAT='%Y-%m-%d:%H:%M '
# not the default, we like to be explicit that we are not using defaults
HISTFILE=~/.bash_eternal_history
# preserve all history, forever
HISTSIZE=-1
# preserve all history, forever, on disk
HISTFILESIZE=-1
# record only one instance of a command repeated after itself
HISTCONTROL=ignoredups
# preserve history across/between shell sessions...
# ...when the shell exits...
shopt -s histappend
# ...and after every command...
PROMPT_COMMAND="${PROMPT_COMMAND:+$PROMPT_COMMAND; } _setAndReloadHistory"
EDIT: Remembered just after submitting that since I am on MacOS, I ran the command
touch ~/.bash_sessions_disable
back on August 22nd, 2020, to prevent Terminal from saving per-session information. I've never cleaned out ~/.bash_sessions, suppose I should, but it hasn't been updated since that day.
For those who would like to read more about staying in power as a dictator, or for that matter any kind of political leader, I found "The Dictator's Handbook: Why Bad Behavior is Almost Always Good Politics" [1] a good read on the topic.
Of note is the required number of supporters can be quite low when you have a government supported by resource extraction.
