mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: "John D. Coleman" <jdc843@sccoast.net>
Cc: hjl@gnu.ai.mit.edu, linux-kernel@vger.kernel.org,
	elenstev@mesatop.com, gnu@gnu.org
Subject: Re: I have a question about packages of programs
Date: Mon, 26 Aug 2002 16:27:13 +0200	[thread overview]
Message-ID: <20020826142713.GU1529@louise.pinerecords.com> (raw)
In-Reply-To: <3D69AA46.52A2E895@sccoast.net>

> Because my first project is going to be a major
> overhaul of the make and/or automake programs. That ./configure
> --prefix=whatever -- src=here command-line-only-interface has got to go.

Rik was more than polite in his response to this paragraph.
My comment would be more to the point of "Don't judge stuff
until you've understood it."

> Having to read upwards of ten or more different documents, scattered in
> what could be several subdirectories, just to find out what all of the
> configure switches are is a real pain in the butt. Is anyone out there
> using anything other than a CRT/monitor with Linux nowadays to compile
> programs ?

Yes. Serial terminals, telnet sessions, hercules monitors serving as
secondary heads, ... And believe it or not, lots of people prefer the
classic VGA 80x25 textmode to do their work even on high-end 21" screens.
In fact anyone who's tried to convince me that having white background
all over the userland (Hello MS Visual C GUI) is actually _ergonomic_
failed miserably. (Ever had a headache from staring into high res graphics
with bright backgrounds? Suppose you've had, just like everyone else.)

T.

  parent reply	other threads:[~2002-08-26 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  4:10 John D. Coleman
2002-08-26 14:07 ` Rik van Riel
2002-08-26 14:27 ` Tomas Szepe [this message]
2002-08-26 15:32 ` Phil Jackson
2002-08-26 19:41   ` Gerhard Mack

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=20020826142713.GU1529@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=elenstev@mesatop.com \
    --cc=gnu@gnu.org \
    --cc=hjl@gnu.ai.mit.edu \
    --cc=jdc843@sccoast.net \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®