|
|
| Author |
Message |
| 25 new of 172 responses total. |
remmers
|
|
response 125 of 172:
| 
Feb 22 05:19 UTC 1997 |
The motion to allow unregistered reading of Grex conferences via
the World Wide Web failed: 16 for, 24 against. See item 54 in
Coop for more detail.
|
valerie
|
|
response 126 of 172:
|
Feb 22 21:27 UTC 1997 |
This response has been erased.
|
tsty
|
|
response 127 of 172:
|
Feb 24 09:16 UTC 1997 |
what i have preferred to explain, getting out of help chat, is to
use ctrl-c instad of ctrl-d. true, both work, but ctrl-c is a safer exit.
|
davel
|
|
response 128 of 172:
|
Feb 24 12:42 UTC 1997 |
How so?
|
valerie
|
|
response 129 of 172:
|
Feb 24 14:11 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 130 of 172:
|
Feb 24 14:12 UTC 1997 |
This response has been erased.
|
e4808mc
|
|
response 131 of 172:
|
Feb 24 14:31 UTC 1997 |
Or the wrong one, perhaps :-(.
|
janc
|
|
response 132 of 172:
|
Feb 24 17:10 UTC 1997 |
Re #127: This is definately matter-of=taste territory, but I've always
felt control-D is a cleaner way to exit that control-C. Control-D means
"end of text" and is received by a program as a termination of the input
stream. Control-C is an interupt, almost alike hitting ctrl-alt-del on
your DOS box (though a little less harsh than that). It's an abnormal
exit condition. We written programs should handle both properly, but
I've seen cases where exiting with control-C causes programs to stop
without quite finishing up the last command you issued. On the other
hand, I've also seen programs that go into infinite loops if you try to
stop them with control-D (though that requires *really* poor
programming).
|
scott
|
|
response 133 of 172:
|
Feb 24 17:24 UTC 1997 |
control-D can also log you out, which is why some don't like using it.
|
n8nxf
|
|
response 134 of 172:
|
Feb 24 22:28 UTC 1997 |
Yea, that happens to me when there is a significant delay in the system's
responce.
|
tsty
|
|
response 135 of 172:
|
Feb 25 09:14 UTC 1997 |
...and ctrl-d is sometimes intercepted and acted upon *upstream* from
where you want the desired action to take place, therefore, ctrl-c
is what my recommendation has been.
and, isn't it also true that 'interrupt' is *designed* to stop a
process even if that process is not naturally funished?
|
valerie
|
|
response 136 of 172:
|
Feb 25 22:29 UTC 1997 |
This response has been erased.
|
remmers
|
|
response 137 of 172:
|
Feb 26 12:57 UTC 1997 |
Voting is now underway on a new proposal to allow read-only
access to Grex conferences by unregistered users. Type vote
at a Unix shell prompt or !vote at a bbs or menu prompt for
further info or to cast a ballot. See Item 55 in the Coop
conference for discussion of the proposal
Note that while any user can cast a ballot, only votes by voting
members in good standing will be counted in determining the
outcome.
Voting ends at the end of the day (EST) on March 12.
|
tsty
|
|
response 138 of 172:
|
Feb 26 15:51 UTC 1997 |
what i type is:
use your interrupt, ctrl-c, unless you changed it.
what is the problem with windows and ctrl-c? new info to me.
|
mta
|
|
response 139 of 172:
|
Feb 26 19:46 UTC 1997 |
Dunno what the problem is exactly, TS, but I can't get a Ctrl+C to work. It
simply has no effect. (I didn't know it was a windows problem, though. It
seems recent.
|
scg
|
|
response 140 of 172:
|
Feb 26 20:54 UTC 1997 |
Are you using Windows Terminal?
|
remmers
|
|
response 141 of 172:
|
Feb 27 14:21 UTC 1997 |
Right -- Windows Terminal (the comm. program that comes with MS
Windows 3.1) by default doesn't pass control characters on to
the remote host. One can change this in one of the pull-down
menus. Very poor choice of default on Microsoft's part, and a
source of endless confusion.
|
valerie
|
|
response 142 of 172:
|
Feb 27 16:44 UTC 1997 |
This response has been erased.
|
tsty
|
|
response 143 of 172:
|
Feb 28 11:15 UTC 1997 |
gawk - windows terminal. sheesh. mta i have a much better solution
for you. we'll be intouch.
|
davel
|
|
response 144 of 172:
|
Feb 28 12:04 UTC 1997 |
Well, the price is right ...
|
janc
|
|
response 145 of 172:
|
Mar 1 14:10 UTC 1997 |
I remember someone having problems with write not sending their message.
They'd do a "write whomever", type the message, and hit control-C. When the
system was slow, the message never got sent. This is because write was still
starting up and hadn't actually read their message when it got the interupt,
so it exited without ever sending it. This won't happen with control-D,
because it isn't an interupt, it is just input. The program won't be stopped
by the control-D until it reaches that point in the input stream.
|
davel
|
|
response 146 of 172:
|
Mar 1 15:04 UTC 1997 |
Isn't that what tel is for?
|
dang
|
|
response 147 of 172:
|
Mar 1 19:16 UTC 1997 |
You can't send multiple lines with tel, just a wrapped single line.
|
valerie
|
|
response 148 of 172:
|
Mar 2 16:25 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 149 of 172:
|
Mar 3 04:02 UTC 1997 |
This response has been erased.
|
