Emdash fans!

[mausmalone@mastodon.social]

@mcc my word processor of choice (Libre Office Writer) doesn't auto-correct to em-dash until after you hit the second space.

[kanamauna@sauropods.win]

@mcc

Both sides because it is easier for my crap eyes to read.

[mirabilos@toot.mirbsd.org]

@mcc I voted yes, but normal spaces are just as wrong as no spaces. You need hair spaces (U+200A) of no less than ⅙ em width.

% em dash
\def\dash{\texorpdfstring%
 {\unskip\kern.16667em\relax\textemdash\penalty\exhyphenpenalty\hskip.16667em\relax}%
 { — }%
}%
% for footnotes, etc.
\newcommand{\Hair}{\unskip\kern.16667em\relax}%

This will define a \dash that eats the spaces you leave around and place the hair space instead.

(At the end/beginning of a line, you leave out the succeeding/preceding space, of course. I hope Tₑχ/LᴬTᴇΧ will DTRT there…)

[iamed2@mastodon.social]

@mcc
Reading these results is wild to me

Is there any style guide that recommends putting any amount of spaces around an em dash?

[mirabilos@toot.mirbsd.org]

@cr1901 @mcc @ThomasWaldmann he erred, though… em dashes need hair spaces around. (Some american house styles have it without, which causes the line to bleed into the surrounding letters; I recently did a screenshot of an example at 12 pt, and there was less than a pixel between them; this is inacceptable.)

[wyatt@soc.megatokyo.moe]

@mirabilos @mcc any idea how to type hair spaces with a compose key?

[mirabilos@toot.mirbsd.org]

@wyatt @mcc get http://mbsd.evolvis.org/MirOS/dist/mir/Keyboard/.XCompose then Compose+-+-+/ gives you a hair space, and (except in older Gtk+ applications like Firefox in bullseye, but not in trixie), Compose+-+-+= gives you the whole precomposed (hah) sequence. (search for “hair” in the file)

save as ~/.XCompose fwiw

[wyatt@soc.megatokyo.moe]

@mirabilos @mcc so it's not something in xkb proper, that's too bad.
I'll try it. I forget if fcitx plays nice with xcompose though

[mirabilos@toot.mirbsd.org]

@wyatt @mcc you’ll need to update your compose sequences, yes. The toolkits all (nowadays) use that file; input methods… are a different thing and sometimes have hardcoded lists embedded in their binaries, which also often differ from the standard X composes (I think even older Gtk+ also did that).

[wyatt@soc.megatokyo.moe]

@mirabilos @mcc actually it looks like my .XCompose already has Ω in it so I think that means fcitx won't interfere in this case.
I forgot I'd had to manually make a combination for it

[mirabilos@toot.mirbsd.org]

@wyatt @mcc … oh, yes.

$ fgrep Ω .XCompose                                                                                   
<dead_greek> <W>                        : "Ω"   U03A9 # GREEK CAPITAL LETTER OMEGA

That’d be tricky to type on average keyboards.

[wyatt@soc.megatokyo.moe]

@mirabilos@toot.mirbsd.org @mcc@mastodon.social for me it's compose O H

$ fgrep Ω .XCompose
<Multi_key> <o> <h> : "Ω" # OHM OMEGA

[mirabilos@toot.mirbsd.org]

@wyatt @mcc that’s indeed still free, I can add that

[tarnport@mastodon.green]

@mcc this is sooo harddd to answer.

[tarnport@mastodon.green]

@kqct @mcc we learned many rules that turned out not to be right or just! It's up to us now.

[tarnport@mastodon.green]

@mcc WWHD (what would Hemingway do?)

[mirabilos@toot.mirbsd.org]

@wyatt @mcc pushed to mirrors, thanks for your contribution to XFree86.

[mirabilos@toot.mirbsd.org]

@wyatt @mcc and with that I go back to my misery about hazel pollen exploding this weekend. Runny nose, teary eyes, achy chest, and all that.

[wyatt@soc.megatokyo.moe]

@mirabilos @mcc hahaha, thanks!
So now I can add xfree86 to my resumé i guess :)
It'll be above systemd (where I did a similarly minor contribution to a hwdb entry)

[mirabilos@toot.mirbsd.org]

@wyatt @mcc well XFree86 in its last remaining form inside the MirBSD CVS repo, but, yes I suppose. (The XFree86 servers seem to have been shut down.)