From: Maxime Devos <maximedevos@telenet.be>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 48501@debbugs.gnu.org
Subject: [bug#48501] [PATCH] daemon: Replace Unicode single quotes with poor simulacra.
Date: Tue, 18 May 2021 19:13:56 +0200 [thread overview]
Message-ID: <0ec7123db2721333ebe103200e42a266c4015d03.camel@telenet.be> (raw)
In-Reply-To: <20210518163405.3618-1-me@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
Tobias Geerinckx-Rice via Guix-patches via schreef op di 18-05-2021 om 18:34 [+0200]:
> The correct ‘ and ’ are not considered word boundaries by some(?)
> terminal emulators like Alacritty, making double-click selection
> tedious. Avoid them in untranslated strings like it's 1992.
N months later, while Tobias Geerinckx-Rice is asleep, a new patch appears:
Typographically Correct via Guix-patches [...]
> It isn't 1992 anymore; the proper ‘ and ’ quotation marks are now
> well-supported in software. Use the typographically-correct ‘ and ’
> in the English translation instead of the unrelated characters ` and '.
>
> [...]
FWIW, double-click seems to work well in Emacs, Gnome Terminal.
Instead of working-around bugs, can ‘we’ fix the bug in Alacritty?
Or at least, open a bug report?
Unfortunately, GitHub's TOS and Privacy Policy were ... not great
last time I checked, though I can't find the ‘badness’ anymore except
for some weird section on ‘idemnity’. In any case, there is an #alacritty
channel:
<https://github.com/alacritty/alacritty/blob/master/CONTRIBUTING.md#contact>
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-05-18 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 16:34 [bug#48501] [PATCH] daemon: Replace Unicode single quotes with poor simulacra Tobias Geerinckx-Rice via Guix-patches via
2021-05-18 17:13 ` Maxime Devos [this message]
2021-05-21 10:28 ` Ludovic Courtès
2021-05-21 14:23 ` Thiago Jung Bauermann via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0ec7123db2721333ebe103200e42a266c4015d03.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=48501@debbugs.gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.