4 ms·
They aren't smart or soft, they are typographically correct. On PC I have AutoHotKey bindings for German and English quotes, single and double, and I'm usually
by Tomte 4y ago
They aren't smart or soft, they are typographically correct.
On PC I have AutoHotKey bindings for German and English quotes, single and double, and I'm usually using them.
- flobosg 4y agoOn Linux I use Fcitx and Ctrl+Shift+Alt+U to open the Unicode character picker, while on Windows I have my fork of a character picker discovered a while ago (https://github.com/flobosg/character-picker https://github.com/flobosg/character-picker) bound to the same shortcut.
- somat 4y agoread up on the compose key it may change your life for the better. or it may be difficult to replicate on windows/wayland leading to additional stress in your life. or perhaps you enjoy your current setup, which does not sound half bad, although not as good as the compose key. Most linux desktops are different and more complicated but here is how I set mine up on openbsd. pick a key that is handy but you don't use much, for me this was the context menu key, on many european keyboards there is an altgr key set aside for this exact use case. in ~/.xsession add a line like "xmodmap -e 'keysym Menu = Multi_key'" create a file ~/.XCompose to setup your own compose sequences. mine looks like #load system compose files include "%L" <Multi_key> <w> <e> <b> : "\xf0\x9f\x95\xb8" # spiderweb read /usr/X11R6/share/X11/locale/en_US.UTF-8/Compose to get a feel for the existing compose sequences.
- anjbe 4y agoI do the same, except instead of xmodmap I use “setxkbmap -option compose:ralt” (plus a few other options) as described in the xkeyboard-config(7) manpage. It has some useful features: https://man.openbsd.org/xkeyboard-config.7 https://man.openbsd.org/xkeyboard-config.7
- flobosg 4y agoI am aware of the Compose key, but have yet to find a good key to map to it (I use AltGr for third and fourth level characters already). I’ll keep it in mind in case my setup breaks down in the future.
- smcameron 4y ago> they are typographically correct. According to an ancient convention. Conventions can be changed. It is not intrinsically, objectively superior to have two separate glyphs for a starting and ending quotation mark. I'd argue the opposite. It is needless complexity. Let us jettison it and embrace the simpler single glyph.
- Tomte 4y agoConvention doesn't mean bad. But sure, feel free to use ( for opening and closing parentheses.
- smcameron 4y agoDisingenuous argument is disingenuous. To make that argument properly, you must also argue for putting both quotation marks on the keyboard as first class keys. And you must retro-actively revise ASCII to include them as first class characters.
- Tomte 4y agoYou're one AHK script away from that.
- cortesoft 4y agoThey might be typographically correct, but they are incorrect for code, and cause so many issues. I'd rather have typographically incorrect quotes that work everywhere.
- Tomte 4y agoWhy would you type them for code? I'm not arguing for the mobile phone automatisms. I insist on separate keys for different quotes.
- elcapitan 4y agoIt's true that people wouldn't use them on their own, but there are a lot of cases (especially blog software, automatic ebook formatting etc), where code examples get messed up subtly by software changing code quotes to standard quotes, often invisibly. The same for minus signs vs dashes.
- notpushkin 4y agoYou might want to give Ilya Birman's Typography Layout a try: https://ilyabirman.net/typography-layout/ https://ilyabirman.net/typography-layout/