This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: CR/LF problems after upgrade
- From: "Cary Jamison" <Cary_Jamison at Symantec dot com>
- To: cygwin-talk at cygwin dot com
- Date: Thu, 18 Jan 2007 18:47:11 -0700
- Subject: Re: CR/LF problems after upgrade
- References: <20070112055257.55D3083C6F@pessard.research.canon.com.au> <31DDB7BE4BF41D4888D41709C476B6570416963D@NIHCESMLBX5.nih.gov> <eolmpg$at7$1@sea.gmane.org> <eom212$mtt$1@sea.gmane.org> <20070117214739.GA18681@trixie.casa.cgf.cx> <eop4i5$t3c$1@sea.gmane.org>
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
Shankar Unni wrote:
> PS Real programmers can (could? by definition?) read punched cards by
> holding them up to the light. Oh, and at normal (human) reading
> speeds, too.
Nah, real programmers use TECO - here's proof!
http://www.pbm.com/~lindahl/real.programmers.html
One guy I worked with wrote a TECO macro to open all the source files on the
system and replace a system call in them! I think it looked something like
a bunch of cartoon cusswords.
Or, to quote from the above article:
It has been observed that a TECO command sequence more closely resembles
transmission line noise than readable text[4]. One of the more entertaining
games to play with TECO is to type your name in as a command line and try to
guess what it does. Just about any possible typing error while talking with
TECO will probably destroy your program, or even worse-- introduce subtle
and mysterious bugs in a once working subroutine.
Cary