From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Makefile mode's sh comment non-exactness
Date: Mon, 30 Aug 2004 09:59:50 -0600 [thread overview]
Message-ID: <41334EF6.5020201@yahoo.com> (raw)
In-Reply-To: mailman.532.1093712523.1998.bug-gnu-emacs@gnu.org
Dan Jacobson wrote:
> Makefile mode's colors show that it thinks this
> cd $?.d && sed /^#/d ../$?|wget -w 2 ...
> is a comment starting at #.
It may be, depending on how one reads the GNU make manual (Makefile
Contents):
| * `#' in a line of a makefile starts a "comment". It and the rest of
| the line are ignored, except that a trailing backslash not escaped
| by another backslash will continue the comment across multiple
| lines. Comments may appear on any of the lines in the makefile,
| except within a `define' directive, and perhaps within commands
| (where the shell decides what is a comment). A line containing
| just a comment (with perhaps spaces before it) is effectively
| blank, and is ignored.
The POSIX Single Unix Specification for the make command (see the
Rationale) is clearer:
| Early proposals stated that an "unquoted" number sign was treated as
| the start of a comment. The make utility does not pay any attention
| to quotes. A number sign starts a comment regardless of its
| surroundings.
> Yes I could use
> cd $?.d && sed '/^#/d' ../$?|wget -w 2 ...
> but then my friends would think I was silly.
But then the shell would at least execute the sed command.
--
Kevin Rodgers
next parent reply other threads:[~2004-08-30 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.532.1093712523.1998.bug-gnu-emacs@gnu.org>
2004-08-30 15:59 ` Kevin Rodgers [this message]
2004-08-27 5:26 Makefile mode's sh comment non-exactness Dan Jacobson
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=41334EF6.5020201@yahoo.com \
--to=ihs_4664@yahoo.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).