From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Ricardo Wurmus <rekado@elephly.net>,
67038@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#67038: Inconsistent use of space before ellipsis
Date: Fri, 17 Nov 2023 16:47:18 +0100 [thread overview]
Message-ID: <87fs14nzzt.fsf@gnu.org> (raw)
In-Reply-To: <878r6xhjsv.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 16 Nov 2023 15:09:04 +0100")
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> Simon Tournier <zimon.toutoune@gmail.com> writes:
>> For consistency, I suggest the rule: ’word...’ and not ’word ...’
>>
>> Something like the patch attached.
>
> +1
+1!
> (match event
> […]
> (('download-started item uri _ ...)
> (when print-urls?
> (erase-current-line*)
> (format port (info (G_ "downloading from ~a ...")) uri)
> (newline port)))
>
> Should we keep this space? Perhaps keep it; it is clearer where the
> URI ends.
Yes, we should keep this one: somebody added it on the grounds that it
allowed them to click on URLs in their terminal and get the correct URL,
without the period.
Ludo’.
next prev parent reply other threads:[~2023-11-17 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:12 bug#67038: Inconsistent use of space before ellipsis Ricardo Wurmus
2023-11-16 9:43 ` Simon Tournier
2023-11-16 14:09 ` pelzflorian (Florian Pelz)
2023-11-17 15:47 ` Ludovic Courtès [this message]
2023-11-19 16:55 ` bug#67038: [PATCH] guix: status: Fix ellipsis inconsistencies Adriel Dumas--Jondeau via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs14nzzt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=67038@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).