dr4g0n

No need for `xargs` in this case, `find` has been able to take care of this for quite some time now, using `+` instead of `;`:

    find . -type f -exec perl -p -i -e 's#foo#bar#g' {} +

It doesn't correspond to how _you_ say dates; I would write 11/03 for the date, and say "the eleventh of March", so it's internally consistent.

Not trying to argue one way or the other, just adding some extra context.

I have a similar problem due to the whole "gmail.com" vs. "googlemail.com" thing that came about in Europe in the earlier days of Gmail.

When I got my gmail account, Google gave me a "googlemail.com" address, due to a pre-existing trademark in Europe. These days the "gmail.com" suffix works for my account, but I've already set everything up with the "googlemail.com" form and saw no reason to switch. Sometime in 2016, someone started using the "gmail.com" version to sign up for stuff, and I repeatedly nearly fell for this exact problem... It's made more difficult by the fact that Google clearly _want_ me to use the "gmail.com" form, and refer to it by that address in many places, despite me opting to use the long form in settings.

I don't think the person using my email address is being malicious, I think it's by mistake, but I have no means to contact him to fix the problem.

Do be aware though that this only works if HISTCONTROL is set to 'ignorespace' or 'ignoreboth' (for bash anyway).

For zsh, you need to have HIST_IGNORE_SPACE set.

It's not exactly hard to do by hand:

    git add ...
    git commit --fixup $SHA
    git stash
    git rebase -i --autosquash $SHA~
    git stash pop

I was really thrown by the ligatures in some of the command snippets (diff and lostfiles).

Why do things manually have to be marked as dependencies? Is that because they were manually installed at one point, or does Arch's package manager not properly track dependencies?

This has reminded me of my old MP3 player, I think it was made by Archos, that had two shuffle modes: "shuffle" & "random".

The "random" mode would happily play songs from the playlist multiple times, even directly after one another; "shuffle" on the other hand would never play a song more than once per playlist. When I first got it I was fascinated by this difference – I still wonder why they included both modes.

You can just pull from someone's local copy, a git checkout is just like a remote (bare) repository that happens to have a tree.

A version control system with the feature set git has is necessarily complicated, this is not a bad thing. Forcing the complexity on the user is a bad thing, but git does not do this except when it is necessary to. Using git at a basic level is not hard.

This essay is not attempting to explain how to use git, it is explaining how git itself works and how changes are physically tracked. There's no need for a basic user to know this information, but if someone wants to dig into git and understand how it works, this essay is a nice guide. Explaining how SVN or any other version control system works at this level of detail would also be complicated.

> If you spot a USB flash drive cemented into a wall or kerb, you may have stumbled across a Dead Drop, part of a global art project borrowing tricks from the world of espionage

Or, you might have stumbled across 240VAC wired to a USB connector.

> The so-called “ow zone” is a zone that is hard to reach with your thumb, like corners of the screen.

The image that goes along with this point demonstrates the areas that are hard to reach for right-handed users, ignoring that ~10% of people are left-handed and have trouble reaching the opposite corners. Your design shouldn't assume that two particular corners are bad and the other two are fine, all four corners should be used for uncommon options only.