You could quite easily use a t420 keyboard in a t440 with a few pins masked which was the last traditional thinkpad keyboard.
Actually I may be getting the numbers wrong, it could be the t430 that I was thinking about. It's been rather a long time since I did any brain surgery on thinkpads.
> "git oldest-ancestor brancha branchb" does what it says.
The oldest (common) ancestor of two revisions would typically be the initial commit. I assume your alias really finds the last (most recent) common ancestor. But are you aware of the `git merge-base` builtin? Your alias looks an awful lot like it.
...okay, I can let this nonsense go today with very little impact, but if I do... will the team need to deal with it 100 times in the future? (And more broadly, by silence am I contributing to the evolution of a bad engineering culture ruled by poor understandings?)
It is very very difficult to know where to draw the line.
Three axes in my mind to take into account: Likelihood, impact, and complexity. The article seems to mostly be about likelihood and complexity. I'd place more importance on impact and complexity. It's worth saving a headache later if it's simple to do right now, however unlikely it is, as long as it doesn't create a maintenance burden before that point.
Wasn't reStructuredText the one where you can't make text a link if any of it is bold/italic/monospaced? IIRC, nesting of inline markup is generally not possible. It works in Markdown…
I had to scroll way too far to find this. All the arguments for RST are about how much more expressive the language is, how much care was taken in making it an abstract document tree. Yet there are simple trees you can't encode, even common ones that markdown handles fine.
I'm not using a language simply because it was aiming at something better, if it missed the mark.
Maybe Markdown doesn't allow arbitrary nesting of inline markup, but the combinations I actually wanted so far work. With reStructuredText, OTOH, I ran into limitations even though I didn't try to commit typographic atrocities.
I tried figuring out whether Firefox can be made to never open a new tab in response to a normal left click on a link. The advice I found is setting `browser.link.open_newwindow.restriction` to 0 and `browser.link.open_newwindow` to 1 in about:config [1]. But it works a little too well: clicking on a link outside of Firefox also no longer opens a new tab.
There's one more detail along the lines of theme changes in other tabs and theme preference changes from the OS/browser: activating the correct theme following history navigation. When I navigate to another page of the author's site, change the theme from light to dark, and then use my browser's back button, I get the light theme again. On my own site I use the `pageshow` event to fix this (https://github.com/meribold/meribold.org/blob/afe6885/_inclu...).
The extra effort is only needed on Firefox and Safari, though. Chromium already handles this somehow.