From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 57949@debbugs.gnu.org
Subject: bug#57949: git head; unportable test(1) operator
Date: Tue, 20 Sep 2022 15:00:02 +0300 [thread overview]
Message-ID: <83tu52w919.fsf@gnu.org> (raw)
In-Reply-To: <2b1180d2e5dbd135d8bc@heytings.org> (message from Gregory Heytings on Tue, 20 Sep 2022 11:54:55 +0000)
> Date: Tue, 20 Sep 2022 11:54:55 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: 57949@debbugs.gnu.org
>
>
> >>> Makefile.in started using "==" as test(1) comparison operator.
> >>>
> >>> This is not portable, only bash supports it. POSIX mandates "=".
> >>
> >> Thanks, fixed!
> >
> > Gregory, why are there ZERO-WIDTH SPACE characters in the top-level
> > Makefile.in? What purpose do they server, and why cannot we do the same
> > with ASCII characters?
> >
>
> Their purpose is to make the text behave exactly like the "CC", "ELC",
> "GEN", "INFO", ... messages printed by make.
I don't think I understand -- what do you expect to happen, as
opposed to when these are removed?
> If it's problematic to have zero-width space characters there, they
> could be removed and/or replaced by something else.
Depending on how you view them, they could appear as "<U+200B>", in
inverse video, on a terminal's display. Which stands out and gets in
the way of reading.
next prev parent reply other threads:[~2022-09-20 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 7:08 bug#57949: git head; unportable test(1) operator Thomas Klausner
2022-09-20 9:22 ` Gregory Heytings
2022-09-20 11:51 ` Eli Zaretskii
2022-09-20 11:54 ` Gregory Heytings
2022-09-20 12:00 ` Eli Zaretskii [this message]
2022-09-20 14:20 ` Gregory Heytings
2022-09-20 15:24 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tu52w919.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57949@debbugs.gnu.org \
--cc=gregory@heytings.org \
/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/emacs.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).