Post by @gumnos@bsd.cafe

R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou:
@rl_dane @polymaths.social
Public en

Minor quibble, but for the life of me, I cannot figure out why I cannot produce a valid em dash ("—", a.k.a. 0xe28094 or U+2014) on #NetBSD, except with mate-terminal. I've tried (u)xterm, alacritty, and lxterminal, and they all either give me a junk character, or an en-dash followed by a hyphen. When I press the compose key and hit the hyphen three times, it immediately attempts to produce an en-dash after the first two hyphen presses, and then gives me a plain hyphen on top of it.

I've checked the Compose file, and it's set up correctly (as far as I can tell).

I think #OpenBSD has the exact same problem, but I haven't tried installing mate-terminal to find out.

cc: @gumnos

Replying to @rl_dane@polymaths.social
Robin Palotai
@robinp @mastodon.social
Public en

@rl_dane @gumnos maybe it is just built-in protection to prevent looking like AI-generated text.

Replying to @robinp@mastodon.social
Tim Chase
@gumnos @bsd.cafe
Public en

@robinp

The bots can have my em-dashes and en-dashes when they pry them from my cold dead hands. I've been using them properly for decades and no clanker is going to deprive me of proper typography. 😉

@rl_dane

1 like
The origin reports likes but does not publish who liked this post.
Refresh interactions
Replying to @gumnos@bsd.cafe
R.L. Dane :Debian: :FreeBSD: :OpenBSD: :NetBSD:🍵 :MiraLovesYou:
@rl_dane @polymaths.social
Public en

@gumnos @robinp

PREACH BRAH