|
|
| Author |
Message |
| 25 new of 603 responses total. |
remmers
|
|
response 100 of 603:
| 
Sep 13 17:00 UTC 1994 |
Well, your id serves as your email address. People all over the world
can now reach you at vor@cyberspace.org.
|
suzie
|
|
response 101 of 603:
|
Sep 15 15:10 UTC 1994 |
This is a test.
|
suzie
|
|
response 102 of 603:
|
Sep 15 15:11 UTC 1994 |
This is another test.
|
suzie
|
|
response 103 of 603:
|
Sep 15 15:49 UTC 1994 |
This is yet another test.
|
powerfox
|
|
response 104 of 603:
|
Sep 18 07:17 UTC 1994 |
This is a test responce in responce to a responces test, make sence?
Didn't think so... what is Jeopardy...??
|
imaman
|
|
response 105 of 603:
|
Sep 21 03:41 UTC 1994 |
Is that all you guys do here is talk about the word test?(Raises an eyebrow,
like Dr. Spock. :)
|
remmers
|
|
response 106 of 603:
|
Sep 25 13:21 UTC 1994 |
All kinds of tests are fair game here, including true/false, multiple
choice, fill in the bla@#}}xDokxd}}}[#$!@
^HConnection hosed by foreign klutz.
^HWhich host?
|
popcorn
|
|
response 107 of 603:
|
Sep 25 15:02 UTC 1994 |
This response has been erased.
|
fazz
|
|
response 108 of 603:
|
Oct 12 14:54 UTC 1994 |
this is yet another test!
|
poontang
|
|
response 109 of 603:
|
Oct 15 01:43 UTC 1994 |
hee hee can i test, too?
|
carson
|
|
response 110 of 603:
|
Nov 9 13:06 UTC 1994 |
here's a test.
|
carson
|
|
response 111 of 603:
|
Nov 9 13:07 UTC 1994 |
thankfully, it didn't work. :)
|
nephi
|
|
response 112 of 603:
|
Nov 21 14:32 UTC 1994 |
This is a test. This is only a test. In the event on an actual emergency...
|
remmers
|
|
response 113 of 603:
|
Nov 22 07:08 UTC 1994 |
...absolutely nothing would have been done.
|
lintott
|
|
response 114 of 603:
|
Nov 30 23:32 UTC 1994 |
well well .....
|
popcorn
|
|
response 115 of 603:
|
Dec 1 15:40 UTC 1994 |
This response has been erased.
|
remmers
|
|
response 116 of 603:
|
Dec 2 02:09 UTC 1994 |
Is that a test question? Is it a timed test?
|
popcorn
|
|
response 117 of 603:
|
Dec 2 16:29 UTC 1994 |
This response has been erased.
|
qieopta
|
|
response 118 of 603:
|
Dec 7 21:16 UTC 1994 |
Is this a test? I'm confused.
|
nephi
|
|
response 119 of 603:
|
Dec 10 10:46 UTC 1994 |
This a test of my ability to edit.
I can edit! I can edit! Yay!!!
Okay, Valerie. I typed "set term=ansi". Is this permanent? Should I do
anything else in addition to what I've already done?
Also, when I press the <delete> button, P appears on my screen, and when
I press the <insert> button @ appears. Why is this? What can I do to
keep this from happening?
|
nephi
|
|
response 120 of 603:
|
Dec 10 11:10 UTC 1994 |
Well, I just logged out and back in and guess what...
my editor does *not* work now. *How* disappointing! Well, I guess I
will go back to the newinfo conf. and see what I did wrong....
Yeah, I know, I am just about to reset my terminal type. You don't have
to remind me!
|
remmers
|
|
response 121 of 603:
|
Dec 10 12:34 UTC 1994 |
To make it permanent, put the line "set term=ansi" in your .login file.
|
nephi
|
|
response 122 of 603:
|
Dec 10 12:41 UTC 1994 |
Well, after an hour of fiddlin' with stuff, I have figured out a way to
get my terminal type set properly (automatically even!) every time I log
in, and it had nothing to do with what was written in the newinfo conf.!
The stuff that was written in the 'changing your terminal type' item had
nothing to do with *me*, anyway, as I couldn't even *find* a line that
said anything *like* "eval `/usr/ucb/tset".
Anyway, the way I fixed my terminal was that I used the unix command
"set term=ansi" which I picked up somewhere at random. Then I came back
to picospan and typed "edit .login". I scrolled to the bottom and typed
"set term=ansi". When I logged out and back in again, I found that I
could use my editor, pico!
This may not have been the best or cleverest way to change my terminal
type, but I'm still proud that I was able to change it since so many
people told me that I couldn't do it because my terminal type was set
to dumb.
Finally, if anyone sees any fault to what I did, please tell me so that
I can change it and will know better for the future.
*Finally*, finally, what is the best terminal type for me to have? My
terminal will emulate vt100, vt220, vt320, pc-xt, pc-at1, pc-at2, 705,
and 605. It is set at 705 right now, if that means anything. What
problems might be associated with any of these for a person that has
to telnet here? What terminal type (that will work) will let me do the
most?
P.S. I decided to enter this in the test conf. because I thought that
since it was an out of the way place that was still checked by the
people that can answer my questions, no one would be bothered while I
rambled on and on and on and on and on and on and on and on and on and
on... ad nauseum.
|
nephi
|
|
response 123 of 603:
|
Dec 10 12:42 UTC 1994 |
I did it before you said it, honest. it just took me a long time to
enter the response. 8*)
|
remmers
|
|
response 124 of 603:
|
Dec 11 16:01 UTC 1994 |
Have you discovered the "info" conference yet? It's devoted to "how
to use grex" questions like this. Anyway, congrats on figuring out
on your own how to do this.
Re best terminal type: I don't know what pc-*, 605, and 705 terminal
types are. If they work okay with a term type of "ansi" on Grex, that
means they must be ansi-compatible terminals of some sort, but I'm not
familiar with those names.
You will probably notice very little if any difference among the terminal
types ansi, vt100, vt102, vt220, vt320. If you log in over a dialup
line at a low baud rate (<= 2400), the last 3 would give you somewhat
faster screen updating in text editors than vt100 would, but over the
internet link you probably wouldn't notice. The vt220 and vt320 terminals
have more advanced features than vt102, but there's little if any software
on grex that actually uses those features. Emulating a vt220 and setting
your term type on grex to vt220 should work fine; that's what I often do.
|