all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Igor Galić" <igalic@brainsware.at>
Cc: 34591@debbugs.gnu.org
Subject: bug#34591: 25.2; Color-mark a space in the second parts of an if(n)eq condition
Date: Fri, 22 Jan 2021 22:03:10 +0100	[thread overview]
Message-ID: <87a6t0wupd.fsf@gnus.org> (raw)
In-Reply-To: <1550654060.7350.0@smtp.fastmail.com> ("Igor Galić"'s message of "Wed, 20 Feb 2019 10:14:20 +0100")

Igor Galić <igalic@brainsware.at> writes:

> When editing a GNUmakefile, it would be very helpful if any space after
> the comma in the second condition was somehow marked:
>
>    ifeq ($(shell foo | bar && echo true), true)
>
> will never match. So it would be helpful if that could be signaled.

(I'm going through old bug reports that unfortunately got no response at
the time.)

I'm not quite sure I understand what you're referring to here, but if
the point is that "echo true" returns "true", and we're then checking
whether that's equal to " true" instead of "true", that doesn't seem to
be the case -- in my testing GNU make seems to just ignore spaces after
the comma.  Perhaps this depends on the make version?

Or do I misunderstand what the reported bug here is?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-01-22 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  9:14 bug#34591: 25.2; Color-mark a space in the second parts of an if(n)eq condition Igor Galić
2021-01-22 21:03 ` Lars Ingebrigtsen [this message]
2021-02-22 15:18   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6t0wupd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34591@debbugs.gnu.org \
    --cc=igalic@brainsware.at \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.