From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: Makefile mode comment color didn't notice backslash continuation
Date: 04 Feb 2003 09:00:32 +0800 [thread overview]
Message-ID: <87lm0woo5r.fsf@jidanni.org> (raw)
In-Reply-To: p5fzr5t7j8.fsf@lemming.engeast.baynetworks.com
P> Personally I believe this is wrong as well, but suggest a different
P> solution: none of this text should be colorized as a comment.
hmm, indeed, this is Makefile mode, not shell-script mode. On the
other hand, one could say that me making a fuss about this ended up in
'emacs taking its toys and going home', leaving me with less colors
than i started. however it is probably better. however maybe there
should still be a makefile-show-shell-comments-too variable one could
turn on so I won't run out of things to find bugs in :-)
P> In the above example _none_ of that text is a makefile comment, because
P> the entirety of any line beginning with a TAB is considered a command
P> script, and make does not do any comment processing on command script
P> lines (it can't, actually).
P.S. if there is no TAB on the last line, it is indeed not colored, as
to your specs...
P> In short (too late...) the font-locking in makefile mode should ignore
P> everything except make variables for colorization in a line that begins
P> with a TAB (that's what make does, after all...)
I think you mean makefile mode need not bother itself with any detail
of lines beginning with tab, i.e. the only comment color in
$ cat Makefile
e=z #ppp
z:
echo $e
f=g date
would be #ppp
--
http://jidanni.org/ Taiwan(04)25854780
next prev parent reply other threads:[~2003-02-04 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1311.1044140204.21513.bug-gnu-emacs@gnu.org>
2003-02-03 20:48 ` Makefile mode comment color didn't notice backslash continuation Paul D. Smith
2003-02-04 1:00 ` Dan Jacobson [this message]
[not found] ` <mailman.1370.1044327576.21513.bug-gnu-emacs@gnu.org>
2003-02-04 4:16 ` Paul D. Smith
2003-02-04 16:14 ` Dan Jacobson
2003-02-06 5:24 ` Dan Jacobson
2003-02-04 7:36 ` Eli Zaretskii
[not found] ` <mailman.1355.1044305370.21513.bug-gnu-emacs@gnu.org>
2003-02-13 19:46 ` Alexander Pohoyda
2003-02-01 20:38 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lm0woo5r.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
/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.