|
Grex > Coop6 > #38: Change default picospan mailer to pine? | |
|
| Author |
Message |
| 25 new of 60 responses total. |
rcurl
|
|
response 25 of 60:
| 
Jan 9 17:55 UTC 1995 |
I think the problem is - where is the mode of the distribution? It
appears to be vt100, so "dumb", necessary or optional, is out on a tail,
and a pain to more people than not. However, what is being talked about
are *defaults*: I believe anyone would be able to choose what they want,
still. (I am a vt100 user, and much prefer pine to mail, and always
recommend pine to newusers - none of whom have complained. But still,
I understand your problem.)
|
davel
|
|
response 26 of 60:
|
Jan 10 12:02 UTC 1995 |
If you're calling in from a dumb terminal (which is most unlikely, in the
sense of "dumb" in question!), do you tell Grex that it's type dumb?
|
popcorn
|
|
response 27 of 60:
|
Jan 10 14:15 UTC 1995 |
Rane and Davel are exactly right in #25 and 26.
|
tsty
|
|
response 28 of 60:
|
Jan 10 15:19 UTC 1995 |
many preferences are born from exposure. I agree that the default
termtype should be vt100. Most of the terminals even, are vt100
emulators. The instance of a truely dumb terminal is pretty rare.
They can emulate something (well, my RS model 100 can't, but ...).
Pine/elm whatever might take some time to get up and running *IF*
you have something against which to compare it. If you already
have some experience, then you most likely can make your own
adjustments.
Frankly, I've been using a little bit of PIne just to get used to
it - it's not all that bad for time. Still, i also prefer mail.
Maybe there could be an intelligence switch in newuser, default
to mail if the termtype has been selected as dumb, and pine if
the termtype has been selected as someting visual.
|
popcorn
|
|
response 29 of 60:
|
Jan 10 23:11 UTC 1995 |
Yup, at the staff meeting the other day, someone suggested setting
new people's mailer to "default-mailer". I'll be writing a script called
"default-mailer" which looks at your terminal type and runs "mail" if
you have a dumb terminal, or "pine" if you have a non-dumb terminal.
|
brenda
|
|
response 30 of 60:
|
Jan 11 00:46 UTC 1995 |
For some reason, some unix systems won't let you into pine if your
terminal is set to ansi. I haven't had any problems here, but
it could be something worth listening for.
|
remmers
|
|
response 31 of 60:
|
Jan 11 11:36 UTC 1995 |
That's because on many Unix system, the "ansi" termcap definition is
very limited -- doesn't specify all the capabilities that pine needs
in order to run. The "ansi" termcap on "grex" is a more powerful
home-grown description that's adequate for pine.
|
davel
|
|
response 32 of 60:
|
Jan 11 12:11 UTC 1995 |
Author! Author!
|
tsty
|
|
response 33 of 60:
|
Jan 13 12:20 UTC 1995 |
<<sounds like a call for remmers to take a bow>>
|
sidhe
|
|
response 34 of 60:
|
Jan 26 19:30 UTC 1995 |
Actually, I have used the dumb terminal many times over the past
two weeks, I'll have you know, and, no, it isn't capable of any form
of emulation; it's a pager unit <a keyboard that's hooked up to a phone
line, that has a one-line tall by 40-character wide display> It is a
DUMB terminal! It is also the only thing that I can use at the locale in
question.
|
remmers
|
|
response 35 of 60:
|
Jan 26 20:38 UTC 1995 |
Hmmm, you're right, it *is* hard to do full-screen stuff on a
one dimensional display.
|
lilmo
|
|
response 36 of 60:
|
Jan 26 21:10 UTC 1995 |
That COULD present some problems... :-)
|
lilmo
|
|
response 37 of 60:
|
Jan 26 21:12 UTC 1995 |
And over the Internet, I am effectively using a "dumb terminal", even though
I have a VGA screen, and ANSI, etc...
|
popcorn
|
|
response 38 of 60:
|
Jan 27 03:08 UTC 1995 |
Why? You should be able to tell Grex you're using an ansi terminal.....
|
sidhe
|
|
response 39 of 60:
|
Jan 27 14:44 UTC 1995 |
Some net providers aren't very tolerant of "adjusting" things like
that.
|
popcorn
|
|
response 40 of 60:
|
Jan 27 15:16 UTC 1995 |
It shouldn't matter. If your terminal does ansi, you can tell Grex you're
using an ansi terminal, without needing to tell your net provider anything
about what type of terminal you're using.
|
sidhe
|
|
response 41 of 60:
|
Jan 29 03:36 UTC 1995 |
That's all well and good, but that hasn't been my experience. Sorry,
don't mean to throw it back at you like that, but I do not posses any
comprehension as to WHY it won't let me, it just *doesn't*
|
ajax
|
|
response 42 of 60:
|
Jan 29 04:15 UTC 1995 |
I'm in the same boat...dunno why, but when I telnet in through msu-gopher,
my vt100 emulation stops working for a couple codes. Probably something
to do with my 60-line screen, but I dunno...some problems I just accept :).
|
carson
|
|
response 43 of 60:
|
Jan 29 11:23 UTC 1995 |
I've been in this boat *often*, but I can never remember how to get out
of it. Often when coming in over the net, Grex won't *ask* what sort
of terminal the user is using, unless it can't figure it out at all. If
it can figure it out, but doesn't have a termcap for it, SOL.
mdw sent me mail re: this, but it's on a disk somewhere. I affectionately
titled it "everything you ever wanted to know about 'tset' but were
afraid to ask." hopefully he can re-explain it here.
|
popcorn
|
|
response 44 of 60:
|
Jan 29 13:16 UTC 1995 |
Re 41: Sidhe - What did you type (what command did you use, and at which
prompt?) to try to set your terminal type to ansi?
|
chelsea
|
|
response 45 of 60:
|
Jan 29 14:28 UTC 1995 |
Local access through merit hasn't worked for me for weeks now.
A few lines after the Grex login - nadda. I had heard mju had
sent mail to the Merit folks about this problem.
So from a U of M machine I'm jumping to the MSU gopher where
I use vt100 emulation just fine, as long as I'm at 8N1.
At 7E1 I have the same problem ajax mentioned.
|
sidhe
|
|
response 46 of 60:
|
Jan 30 03:33 UTC 1995 |
Valerie- !tset ansi.
I'm glad to see that the problem isn't just with *my* hardware <a
definite fear>, but I hope this can be resolved soon.
|
popcorn
|
|
response 47 of 60:
|
Jan 30 04:57 UTC 1995 |
You might try editting your .profile file (type "!pico .profile") and
adding a line at the end that says "TERM=ansi; export TERM" (without
the quotation marks. That should force your terminal type to ansi no
matter where you log in from. You might also want to put a # in front
of the line that goes "eval ...tset..." so that if you ever log in to
Grex on a dial-in you don't get a prompt for your terminal type.
Note that if anything goes really wrong when you're editting your .profile
and you can't get back in to Grex, you can log in as "trouble" to send
e-mail to the staff asking someone to fix your .profile.
|
sidhe
|
|
response 48 of 60:
|
Jan 31 14:25 UTC 1995 |
Any password for "trouble"?
|
pegasus
|
|
response 49 of 60:
|
Jan 31 16:18 UTC 1995 |
Could someone be so kind as to give me step by step instructions for
logging into Grex from U-M? This would have to be from the viewpoint
of a student. I'm trying to get people in the SCA logged on to Grex for
use of the Rialto Conference, and need these very detailed instructions.
I'd be happy if they were emailed, to lessen drift. <g>
Pattie
|