ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gilbert van den Dobbelsteen <gilbert@panter.soci.aau.dk>
Cc: Hans Hagen <pragma@wxs.nl>, <ntg-context@ntg.nl>
Subject: Re: make files
Date: Mon, 11 Jun 2001 07:53:20 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0106110751360.7136-100000@panter.soci.aau.dk> (raw)
In-Reply-To: <20010609093514.0D5C852352@bart.math.muni.cz>

> >
> The <tab> syntax is make-specific. It is very very supid. The GNU make
> only adds some types of rules to ``standard'' make (e.g., some kind of
> `wildcards', more comfortable ways to handle filenames). Nevertheless
> the <tab> syntax will survive everything.

Borland make used to be less restrictive, I hate tabs too.
>
> 				D.A.
>
> P.S.: Some `too-inteligent' text editors convert your tabs into spaces
> (and the user doesn't know that option is set). If your Makefile doesn't
> want to work and there is no reason why, check this.
> It happened to me...

There is only one stupid way to solve this: use vi. It is great, and greatly
impossible (I still hate it, and love it).

Gilbert.


  parent reply	other threads:[~2001-06-11  5:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08  8:31 Hans Hagen
2001-06-08  8:53 ` Marc van Dongen
2001-06-08  9:00 ` Gilbert van den Dobbelsteen
2001-06-08  9:25 ` Taco Hoekwater
2001-06-08  9:38   ` Marc van Dongen
     [not found] ` <Pine.LNX.4.30.0106081058490.20802-100000@panter.soci.aau.d k>
2001-06-08  9:36   ` Hans Hagen
2001-06-08  9:56     ` Marc van Dongen
2001-06-09  9:35     ` David Antos
2001-06-10 20:20       ` Hans Hagen
2001-06-11  5:53       ` Gilbert van den Dobbelsteen [this message]
2001-06-11 11:12         ` Marc van Dongen
2001-06-08 17:25 ` Berend de Boer
2001-06-09  9:34 ` Uwe Koloska
2001-06-10 20:10   ` Hans Hagen
2001-06-11  7:21     ` Berend de Boer
2001-06-11 11:09     ` Marc van Dongen

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=Pine.LNX.4.30.0106110751360.7136-100000@panter.soci.aau.dk \
    --to=gilbert@panter.soci.aau.dk \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    /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.
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 NNTP newsgroup(s).