Richard wrote:
In article
Richard <legalize at xmission.com> writes:
What's the coolest TECO command sequence you
can write in 49 characters?
Additional: control characters like ^B (ASCII 2) count as 2 characters
for the purposes of counting towards the limit of 49.
This file (DATE.TEC) was tested under RT-11 as:
MUNG DATE,31-DEC-99
Of course, since the actual RT-11 command is only: DATE 31-DEC-99
using this "MUNG" version is useful only if it is important to keep a record
of what date was entered. Still not very cool, but a bit better since
any valid
date can be used. ALSO, the letters "TECO" appear in the 49 characters
which are an essential portion of the command sequence, being the name of
the file that is used, although ANY other 4 characters (other than TECO) can
be used instead. The 2 "J" characters in front of EG are useless and
only serve
to bring the total character count to 49. Without the 2 "J" characters and
reducing the file name to a single character reduces the TECO command
sequence to 41 characters, including the 3 pair of <CR><LF> characters.
Since the date is entered by the user, the user can abide by what the
operating
system requires. The 49 characters include the <CR><LF> at the end of each
line, especially since the <CR><LF> at the end of the first line is an
essential
part of the command sent to RT-11. If the <CR><LF> characters are not
counted, remove the "JJ" preceding the EG command, add the text string
"ITECO:$$" to the end of the the last line (in front of the
<CR><LF>) and
probably change the name of the file to "DATE" from "TECO". That
would
result in the second version and include the original request that the
string
"TECO:" be part of the 49 characters.
It is interesting how an idea can evolve after thinking about it for a
while.
Jerome Fine
________________________
J^UDDATE $GD^UR
$LGREWTECO.COM$
ECJJEG at TECO$$
________________________
J^UDDATE $GD^UR
$LGREWDATE.COM$
ECEG at DATE$$ITECO:$$
________________________
