Rejection sensitivity may be the reason I detest to-do lists. The lists inevitably languish and slowly turn into a perpetual reminder of who I haven't become, i.e. a rejection from past-me.
It's unclear what device attestation does here. You can print a fake check and take whatever picture you want. If it's using dead pixels or something as a device fingerprint, you get those dead pixels. You can also fake dead pixels, of course. Authenticating the phone's OS doesn't authenticate the camera, or what the camera's looking at. It's a signal, maybe, but the weak link in "a napkin with the right numbers and scribble on it is a money transfer" is probably not whether someone has root on the device that's taking a picture of the napkin.
Are you saying they should always be present? Or only when the condition takes multiple lines; i.e. do you take issue with the ifs in zone_name_pref too?
Personally I think the indentation does a good enough job here.
Easy is almost an understatement; it's Alt+Hyphen. [Edit: My bad that's en-dash, can't tell the difference in this monospaced text field. Em-dash you have to hold shift.]
I guess on Windows it's Alt+0,1,5,1 on a numpad. Or you copy+paste from Character Map.
Generally spaces around em-dashes is a question of style, not pre- or pro-scribed by any specific typographical rule. One nice middle ground is a hair space ( ), although it’s a pain to insert.
> spaces around em-dashes is a question of style, not pre- or pro-scribed by any specific typographical rule
Writing and publishing style guides like Hart's Rules (Oxford Style Guide) & Chicago manual of style have the 'em' dash use as a parenthetical closed or "no spaces" dash.
In British use – Hart's Rules – writers will choose the 'en' dash with spaces as a parenthetical dash, where US writers/publishers choose the closed 'em' dash for the same thing.
Imo, there is a conflation of 'en' dash and 'em' dash going around due to the ease of smart-dashes auto-correction turning (--) into 'em' dash with the 'en' dash and non-auto-correct 'em' dash needing a key-combo.
Common everyday typing online, I think people will simply use what is convenient and "good enough" -- a single hyphen dash as an 'en' dash or 2-hyphen dashes that may or may not auto correct into an 'em' dash. I prefer mixing spaces with a 2-hyphen dash 'em' dash, but I'm not a published writer so I enjoy doing wild things like that
I configured my Markdown renderer to replace ` -- ` with " — ". Hopefully those narrow spaces make it through HN's rendering — it's much easier when your tooling can do the job for you.
Or you've had WinCompose installed for years and type Compose+hyphen+hyphen+hyphen. — is easy to type that way. The same works for Linux with a compose key enabled, WinCompose is a program to give Windows a compose key, and comes with default sequences including those found by default in most distro's XCompose list.
I was convinced Firefox didn't support rendering partial HTML at all, but it turns out it just waits for two separate chunks to arrive before rendering. Queer.
