unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Pfeiffer <dapfy@t-online.de>
Cc: occitan@esperanto.org, emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: makefile-mode font-lock bugs and annoyances
Date: Thu, 09 Jun 2005 20:49:15 +0200	[thread overview]
Message-ID: <42A88F2B.1060308@t-online.de> (raw)
In-Reply-To: <m3ekbbhibd.fsf@kfs-l.imdomain.dk>


[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]

la 09.06.2005 13:37 Kim F. Storm skribis:

>Miles Bader <miles@lsi.nec.co.jp> writes:
>  
>
>>It's a fact of life that many, many, people use the name "Makefile" for
>>GNU-make-only makefiles, and if anything this practice has spread
>>greatly in recent years (I think I've only seen "GNUmakefile" used once
>>or twice in my entire life!).
>>    
>>
>
>The default for emacs should be to treat ALL makefiles as GNU makefiles.
>  
>
Emacs own makefiles are not GNU make, being auto* based it uses plain 
make as do many other GNU projects.  Other like bison or omniORB do 
indeed use GNUmakefile.  I think I'd rather try to parse the file and 
see what's in it.

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

-- 
lerne / learn / apprends / lär dig / ucz sie;    Esperanto:
                              http://lernu.net/


[-- Attachment #1.2: Type: text/html, Size: 1491 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

  reply	other threads:[~2005-06-09 18:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <wczmu0kci6.fsf@xpc14.ast.cam.ac.uk>
     [not found] ` <42A7ECDC.1000302@t-online.de>
2005-06-09  9:32   ` makefile-mode font-lock bugs and annoyances Miles Bader
2005-06-09 11:37     ` Kim F. Storm
2005-06-09 18:49       ` Daniel Pfeiffer [this message]
2005-06-09 22:20         ` Kim F. Storm
2005-06-09 22:33           ` Daniel Pfeiffer
2005-06-10  8:30             ` Kim F. Storm

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=42A88F2B.1060308@t-online.de \
    --to=dapfy@t-online.de \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=occitan@esperanto.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).