Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!rjf001!mudos!mju
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: problem with 'myless'
Message-ID: <70ie12w164w@mudos.ann-arbor.mi.us>
Date: 14 Apr 91 17:21:17 GMT
References: <16660007@col.hp.com>
Organization: The Programmer's Pit Stop, +1 313 665 2832
Lines: 25

mikek@col.hp.com (Mike Karin) writes:
> I tried using myless as posted on c.b.i.p a day or so ago.  I found a
> little problem when I inadvertantly invoked less with no parameters.  What
> happened was that the machine would only echo characters typed from the
> keyboard and it was impossible to get out of the program without doing
> a warm boot (ctl-alt-del).  

Sounds like "myless" is doing the same thing that "less" does under
Unix when you invoke it with no parameters.  It acts as a filter,
reading from stdin and writing to stdout.  This is designed to
facilitate using it in a pipeline; unfortunately, when you invoke it
in a non-piped environment, stdin and stdout are both the keyboard.

If you have BREAK turned on (BREAK ON from the DOS prompt), you should
be able to hit Ctrl-Break to kill it, unless myless is trapping it.
You should also be able to feed it a ^Z on stdin, which is EOF under
DOS, to make myless think that it's reached the end of the input,
which should let you quit.  I suppose you could also try typing enough
characters to fill up 25 lines, at which point you'll get the ":"
prompt from less, and you can hit "q" to quit.

--
Marc Unangst               |
mju@mudos.ann-arbor.mi.us  | "Bus error: passengers dumped"
...!hela!mudos!mju         |