From: "Gary R. Van Sickle" <g.r.vansickle@att.net>
To: <cygwin-talk@cygwin.com>
Subject: RE: Rationale for line-ending recommendation?
Date: Sat, 20 Dec 2008 07:07:00 -0000 [thread overview]
Message-ID: <ADD6D7BDCF774FE38D1A7B9423E17F49@DFW5RB41> (raw)
In-Reply-To: <gihqkp$2un$1@ger.gmane.org>
> From: Andrew DeFaria
>
> Gary R. Van Sickle wrote:
> > Another one who believes what their calendar tells them?
> Another one who doubts the calendar and can't do math...
> > Then riddle me this Andrew: If this were in fact the 21st
> century (AKA
> > "The Future"),
> But you see that's the thing. It's not AKA "The Future" - it's now.
Nope. In "The Future", AKA the 21st Century, software is able to read plain
text files without problems. Users of that software spend exactly zero time
worrying about what particular format those plain text files may be in.
> You're just sleeping...
On the contrary, I'm one of the few who have awoken themselves to the fact
that all is not as the Vast Bi-Partisan Calendar Conspiracy(tm) would have
you belive.
> > why would we be be discussing software which is able to
> understand one
> > text file format, but not a second ever-so-slightly different text
> > file format?
> What do you mean "we" Kemosabe?
Smith, and Wesson, and me.
> > Now, if y'all shall excuse me, I have to go pick up my brand new
> > nuclear turbine-powered flying car.
> Yeah right...
Ah heck, now do I fill 'er up with Regular or Ethyl Plutonium?
> --
> Andrew DeFaria <http://defaria.com>
> Is God willing to prevent evil, but not able? Then he is not
> omnipotent.
> Is he able, but not willing? then he is malevolent. Is he
> both able and willing? Then whence cometh evil? Is he neither
> able nor willing? Then why call him God?
What does God need with a starship? Nobody knows. Maybe the text file
explaining it all had the wrong line endings.
--
Gary R. Van Sickle
parent reply other threads:[~2008-12-20 7:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gihqkp$2un$1@ger.gmane.org>]
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=ADD6D7BDCF774FE38D1A7B9423E17F49@DFW5RB41 \
--to=g.r.vansickle@att.net \
--cc=cygwin-talk@cygwin.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.
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).