From: Jon Cast <jcast@ou.edu>
To: cygwin@cygwin.com
Subject: Re: gzip.exe as symlink...
Date: Tue, 16 Jul 2002 18:51:00 -0000 [thread overview]
Message-ID: <200207170110.g6H1A1Z28086@d-ip-129-15-78-125.cs.ou.edu> (raw)
In-Reply-To: Message from Nicholas Wourms <nwourms@yahoo.com> of "Mon, 15 Jul 2002 14:02:14 PDT." <20020715210214.69438.qmail@web21003.mail.yahoo.com>
Nicholas Wourms <nwourms@yahoo.com> wrote:
<snip>
> Sigh, as usual the emacs camp always misses the point.
``As usual ... always''. Not simple or elegant. Not relevant, but
neither are your comments.
> You use a shell for file operations
So `vi foo.gz' works why?
> and you use an editor for editing.
Right. Not a viitor. Not an emacsitor. Those aren't even words!
> Why is there any need to muddle the two? Vi is simple and elegant,
And is an actual editor.
> whereas emacs is well...
Not an editor. It's a desktop environment under the delusion it's an
editor. It's still a better editor (no ugly i/a/e/etc. just to type
in text) and desktop environment (M-x customize is the best thing I've
seen) than anything else out there.
> rather bloated
For a desktop environment?
> and not very elegant.
How can something be more elegant than Lisp?
> Would you use a chainsaw to cut a diamond? I think not...
No. But I wouldn't precariously balance said diamond between my
fore-finger and tongue, either. I'd use a real tool to hold it.
> Cheers,
> Nicholas
Jon Cast
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-07-17 1:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 15:46 Robinow, David
2002-07-15 15:48 ` Nicholas Wourms
2002-07-16 18:51 ` Jon Cast [this message]
[not found] <rrschulz@cris.com>
2003-03-29 4:00 ` Mozilla 1.3 built on cygwin? Jeff.Hodges
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 18:50 files and directories distinction: Aldi Kraja
2002-07-16 19:34 ` Randall R Schulz
2002-07-16 19:37 ` Jon Cast
2002-07-15 16:33 gzip.exe as symlink Robinow, David
2002-07-15 16:13 Robinow, David
2002-07-15 16:27 ` Robert Collins
2002-07-15 2:20 gzip.exe as symlink breaks NTEmacs's jka-compr.el Matt Swift
2002-07-15 2:26 ` Robert Collins
2002-07-15 5:36 ` gzip.exe as symlink Max Bowsher
2002-07-15 5:38 ` Robert Collins
2002-07-15 12:41 ` Jon Cast
2002-07-15 14:47 ` Nicholas Wourms
2002-07-15 15:57 ` Robert Collins
2002-07-15 22:22 ` Max Bowsher
2002-07-15 9:21 ` Dario Alcocer
2002-07-15 12:02 ` gzip.exe as symlink breaks NTEmacs's jka-compr.el Jon Cast
2002-07-15 17:05 ` Gerrit P. Haase
2002-07-16 8:59 ` Matt Swift
2002-07-16 9:14 ` David Starks-Browning
2002-07-16 9:17 ` Nicholas Wourms
2002-07-16 10:21 ` Randall R Schulz
2002-07-16 19:27 ` Jon Cast
2002-07-16 19:43 ` Randall R Schulz
2002-07-16 19:51 ` Jon Cast
2002-07-16 20:12 ` Randall R Schulz
2002-07-16 20:14 ` Robert Collins
2002-07-16 23:05 ` Randall R Schulz
2002-07-16 23:42 ` Robert Collins
2002-07-17 0:53 ` Randall R Schulz
2002-07-17 0:58 ` Christopher Faylor
2002-07-17 0:59 ` Robert Collins
2002-07-16 20:36 ` Jon Cast
2002-07-16 23:54 ` Randall R Schulz
2002-07-18 17:08 ` Jon Cast
2002-07-16 19:49 ` Nicholas Wourms
2002-07-16 19:52 ` Jon Cast
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=200207170110.g6H1A1Z28086@d-ip-129-15-78-125.cs.ou.edu \
--to=jcast@ou.edu \
--cc=cygwin@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).