Dr Ivan D. Reid

On 13 Mar 2006 05:26:43 -0800, TOG @ Toil,
chateau.murray @ btinternet.com , <chateau.murray@btinternet.com>
wrote in <1142255744.968038.4850@i40g2000cwc.googlegroups.c om>:

> Anybody else got tools they just *like* using?

TECO. :-)

--
Ivan Reid, Electronic & Computer Engineering, ___ CMS Collaboration,
Brunel University. Ivan.Reid@[brunel.ac.uk|cern.ch] Room 40-1-B12, CERN
GSX600F, RG250WD "You Porsche. Me pass!" DoD #484 JKLO#003, 005
WP7# 3000 LC Unit #2368 (tinlc) UKMC#00009 BOTAFOT#16 UKRMMA#7 (Hon)
KotPT -- "for stupidity above and beyond the call of duty".

Austin Shackles

On or around Mon, 13 Mar 2006 20:16:03 +0000 (UTC), "Dr Ivan D. Reid"
<Ivan.Reid@brunel.ac.uk> enlightened us thusly:

>On 13 Mar 2006 05:26:43 -0800, TOG @ Toil,
> chateau.murray @ btinternet.com , <chateau.murray@btinternet.com>
> wrote in <1142255744.968038.4850@i40g2000cwc.googlegroups.c om>:
>
>> Anybody else got tools they just *like* using?
>
> TECO. :-)

prevert.

I did actually find a system with a working TECO on it (VMS thing, I think),
and managed to create and save a 1-line file.
--
Austin Shackles. www.ddol-las.net my opinions are just that
"Quos deus vult perdere, prius dementat" Euripedes, quoted in
Boswell's "Johnson".

Dr Ivan D. Reid

On Mon, 13 Mar 2006 22:11:24 +0000, Austin Shackles <austinNOSPAM@ddol-las.net>
wrote in <7frb12p4if4376k71qruukfkoipv1egne7@4ax.com>:
> On or around Mon, 13 Mar 2006 20:16:03 +0000 (UTC), "Dr Ivan D. Reid"
><Ivan.Reid@brunel.ac.uk> enlightened us thusly:

>>On 13 Mar 2006 05:26:43 -0800, TOG @ Toil,
>> chateau.murray @ btinternet.com , <chateau.murray@btinternet.com>
>> wrote in <1142255744.968038.4850@i40g2000cwc.googlegroups.c om>:

>>> Anybody else got tools they just *like* using?

>> TECO. :-)

> prevert.

<Proud!>

> I did actually find a system with a working TECO on it (VMS thing, I think),
> and managed to create and save a 1-line file.

Tja; VMS, or RT-11 (or RSX-11M) more likely. I actually didn't
like it much (standard joke was to type in your name and then guess how
TECO would interpret it, though I rather suspect vi could be subjected to
the same test). But it came in handy when I had to programme in C on a
PDP-11 equipped with only a Teletype interface. I quickly learnt the
key sequence to convert all upper-case letters (as entered from the
terminal) to lower case (as required by the language and the libraries).

--
Ivan Reid, Electronic & Computer Engineering, ___ CMS Collaboration,
Brunel University. Ivan.Reid@[brunel.ac.uk|cern.ch] Room 40-1-B12, CERN
GSX600F, RG250WD "You Porsche. Me pass!" DoD #484 JKLO#003, 005
WP7# 3000 LC Unit #2368 (tinlc) UKMC#00009 BOTAFOT#16 UKRMMA#7 (Hon)
KotPT -- "for stupidity above and beyond the call of duty".

Mark Olson

Dr Ivan D. Reid wrote:

> On 13 Mar 2006 05:26:43 -0800, TOG @ Toil,
> chateau.murray @ btinternet.com , <chateau.murray@btinternet.com>
> wrote in <1142255744.968038.4850@i40g2000cwc.googlegroups.c om>:
>
>> Anybody else got tools they just *like* using?
>
> TECO. :-)

You are ODD.

--
'01 SV650S '99 EX250-F13 '86 GL1200A '81 CM400T
OMF #7

Champ

On Mon, 13 Mar 2006 22:47:30 +0000 (UTC), "Dr Ivan D. Reid"
<Ivan.Reid@brunel.ac.uk> wrote:

>>> TECO. :-)
>
>> prevert.
>
> <Proud!>
>
>> I did actually find a system with a working TECO on it (VMS thing, I think),
>> and managed to create and save a 1-line file.
>
> Tja; VMS, or RT-11 (or RSX-11M) more likely. I actually didn't
>like it much (standard joke was to type in your name and then guess how
>TECO would interpret it, though I rather suspect vi could be subjected to
>the same test). But it came in handy when I had to programme in C on a
>PDP-11 equipped with only a Teletype interface. I quickly learnt the
>key sequence to convert all upper-case letters (as entered from the
>terminal) to lower case (as required by the language and the libraries).

"The problem with these editors is that Real Programmers consider
"what you see is what you get" to be just as bad a concept in Text
Editors as it is in women. No the Real Programmer wants a "you asked
for it, you got it" text editor - complicated, cryptic, powerful,
unforgiving, dangerous. TECO, to be precise.

It has been observed that a TECO command sequence more closely
resembles transmission line noise than readable text. 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. "


--
Champ