Re: A check for 'break' or ^C would help a lot
Gary H (garyh@sco.COM)
Mon, 27 May 1996 13:39:54 -0700
- <w2jc@ritz.mordor.com> wrote:
|Having accumulated a newsgroup in Yarn 0.89 with over 12,000 articles,
|I thoughtlessly pressed SPACE thinking I would load them in and clean
|out the spams and garbage at least. Ouch! 3 hours later the '386 was
|still exercising the disk drive, and ^C nor ESC nor any other trick I
|could think of would BREAK the process. FIFTEEN hours later, the process
|ended properly -- and of course then exercised all the stop/break commands
|from much earlier, so the entire time was a waste!
|
|CHIN... the point of my tale here is to ask (beg) that maybe you could
| embed a check for ^C or some other break code into such loops,
|so that one could get out if they do something dumb and want to save the
|half day processes for some time later.... purty pleeeze!
Jim,
I would have to agree with you here. I have the yarn-list on my laptop.
When I accidently press space, I can get into the article selection level
(hope I'm using the right term) in a matter of a few seconds. There is
a few thousand messages here. Anyways, what bugs me is when I hit escape
to get back to the folder selection area (again, not sure if I'm using
the right terms), YARN will lock up for 10 minutes counting the number of
unread articles. This is annoying. I did this two times in a row in the
same session and I just got pissed at myself, walked out of my room and
came back 10 minutes later. It would be nice if there was a "^C" check
when YARN is looping or seq. of keys that can be used to break the loop.
Gary
Ps. I am using .90