unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 46052@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#46052: Colons fooling GNUmakefile mode
Date: Sat, 23 Jan 2021 19:23:40 +0200	[thread overview]
Message-ID: <83r1mb4ler.fsf@gnu.org> (raw)
In-Reply-To: <87im7nlmx9.fsf@gmail.com> (message from Kévin Le Gouguec on Sat, 23 Jan 2021 15:58:58 +0100)

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: jidanni@jidanni.org,  46052@debbugs.gnu.org
> Date: Sat, 23 Jan 2021 15:58:58 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I'm not sure a target line cannot possibly start with a TAB.
> 
> I'll admit to not being an expert in makefile syntax; I do find this
> entry in (info "(make) Error Messages") encouraging though:
> 
> > 'recipe commences before first target. Stop.'
> > 'missing rule before recipe. Stop.'
> >      This means the first thing in the makefile seems to be part of a
> >      recipe: it begins with a recipe prefix character and doesn't appear
> >      to be a legal 'make' directive (such as a variable assignment).
> >      Recipes must always be associated with a target.
> 
> While that phrasing doesn't rule out subsequent targets from starting
> with a TAB, empirically that seems to be the case:

I didn't say a _rule_ can start with a TAB, I said a rule's _line_
could start with a TAB.  For example (indentation added for
readability):

  foo \
	  bar: baz






  reply	other threads:[~2021-01-23 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 13:27 bug#46052: Colons fooling GNUmakefile mode 積丹尼 Dan Jacobson
2021-01-23 13:48 ` Kévin Le Gouguec
2021-01-23 14:00   ` Eli Zaretskii
2021-01-23 14:58     ` Kévin Le Gouguec
2021-01-23 17:23       ` Eli Zaretskii [this message]
2021-01-23 17:59         ` Kévin Le Gouguec
2021-01-23 18:26           ` Eli Zaretskii

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=83r1mb4ler.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46052@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=kevin.legouguec@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/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).