|
Grex > Info > #47: Term cap Pico vision thing | |
|
| Author |
Message |
raven
|
|
Term cap Pico vision thing
| 
Jun 16 04:40 UTC 1993 |
How do I set up my term cap so I can use Pico? I've started using it ovt
over at m-net and I'm hooked. D put some arcane Unix coomand in
my .cfonce file or what? Inquiring minds want to know...
|
| 55 responses total. |
jared
|
|
response 1 of 55:
|
Jun 16 05:34 UTC 1993 |
you will want to have a
setenv TERM vt100 in your .login file, and a
define EDITOR pico in your .cfonce file.
|
tsty
|
|
response 2 of 55:
|
Jun 16 08:16 UTC 1993 |
At least have some TERM in your .login, but the .cfonce file contents
are good enough.
Can you do it yourself, or want it done?
|
davel
|
|
response 3 of 55:
|
Jun 16 11:47 UTC 1993 |
Is .login the proper file for people whose default shell isn't csh?
(For sh, it's .profile, I think. But raven shows /b, which I think
is just picospan, & I don't know what it uses as a login shell.)
|
remmers
|
|
response 4 of 55:
|
Jun 16 15:54 UTC 1993 |
The /b shell runs sh first, then launches bbs. So the proper place for
anyone with /b as their shell to make pico their default editor is in
.profile, which should contain the lines:
EDITOR=pico
VISUAL=pico
export EDITOR VISUAL
That ought to make pico the default editor for any program that allows you
to launch an editor, such as Picospan or mail. (Not sure if it's enough
for "elm", which may require you to set "pico" as both primary and visual
editor in your elm options file also. You can do this in elm by typing
"o" at the elm command prompt.)
|
raven
|
|
response 5 of 55:
|
Jun 16 19:48 UTC 1993 |
Well after a big hastle I managed to edit my .profile correctley.
I managed to erase something crucial and get bounced off the system.
Foutunatley tsty was very helpful and restored my .profile. Now I just
can't seem to get .login edited... Help this is an editor nightmare : (
I still get incomplete term cap entry and .login isn't showing up in
my dir...
|
davel
|
|
response 6 of 55:
|
Jun 16 21:57 UTC 1993 |
Unless you're going to use csh, you don't need a .login. Possibly I
see the problem in your .profile. Here are sections from yours & from
mine:
From my .profile:
if tty -s
then
# next two only apply to interactive shells
stty intr '^C' kill '^U' erase '^H'
eval `/usr/ucb/tset -s -m 'dialup:?ansi-new' -m 'su:?ansi-new'
"${TERM-ansi-new}"` MESG=mesg ; export MESG mesg y
fi
From your .profile:
...
tset=ansi-new
...
if tty -s
then
# next two only apply to interactive shells
stty intr '^_' kill '^X' erase '^H'
MESG=mesg ; export MESG
mesg y
fi
The line tset=ansi-new is not (I think) going to accomplish anything. It
just sets an environment variable, tset, & doesn't export it. Possibly
you want or need tset ansi-new (without the =). The equivalent line
in mine is the eval line, but that's because I want it to ask me for my
TERM variable.
I can't offer to edit your file for you. But try taking out the =.
|
raven
|
|
response 7 of 55:
|
Jun 17 05:22 UTC 1993 |
How do I edit my file with an incomplete termcap? I can;t post to use net
now, which I'm missing already. Oh woh is me... I'll take ANY editor if
I can get my ability to post to usenet again. Someone help me and I promise
I'll never mention editors again. Please explain in simple language.
Depressed clueless newbie : (.
|
raven
|
|
response 8 of 55:
|
Jun 17 06:42 UTC 1993 |
Steve repaired my .profile. I'm psyched i can use pico and usenet
now, too cool. My next purse is one of those Unix books for non-techie
types : ).
|
scg
|
|
response 9 of 55:
|
Jun 29 03:37 UTC 1993 |
Lately when I've tried to use Pico, it hasn't worked right. It just beeps
when I try to backspace, use the cursor keys, or tell it y or n when I try to
quit and it wants to know whether to save the file. It does, however, work
fine as the editor in Pine, it is just when I try to use it alone or as the
editor for something else that it gives me trouble. My term=vt100. Any idea
what would be wrong with it?
|
tsty
|
|
response 10 of 55:
|
Jun 29 06:27 UTC 1993 |
When you say "lately" does that indicate that you have been able to
do all the editing you wanted, anywhere you wanted, and stuff worked
just fine? Or something else?
And, if Pico has worked just fine everywhere 'before', can you pinpoint
any changes you have made anywhere?
|
scg
|
|
response 11 of 55:
|
Jun 29 15:14 UTC 1993 |
When I first started using it, several months ago, it worked fine. I didn't
use it for a couple of months, and then went back and tried to use it and it
didn't work. I might have made some changes then, but I don't remember what.
|
davel
|
|
response 12 of 55:
|
Jun 29 18:31 UTC 1993 |
I tried it out once, months ago, & it worked fine. I tried it again a
couple of days ago (after telling someone about it), & most of the
things on its little menu just beeped.
I just tried it again now, and it's not really "most". Of the 12 options
displayed at the bottom of the screen, the following produce a beep and
the message [ Unknown command ]: ^G, ^Y, ^V, ^K, ^U. Also, when I go to
exit, the options for saving are given as (y/n) but it insists that the N
be uppercase.
My TERM setting is ansi-new. I suspect from the timing that the OS upgrade
is involved in some fashion, but the gap was wide enough to include plenty
of other events as well.
I hope my friend hasn't tried it yet.
(vi is fine for *me*, thank you.)
|
popcorn
|
|
response 13 of 55:
|
Jun 29 22:28 UTC 1993 |
This response has been erased.
|
tsty
|
|
response 14 of 55:
|
Jun 30 03:56 UTC 1993 |
<<maybe I should try Pico too - heck, I like vi too ...>>
|
remmers
|
|
response 15 of 55:
|
Jun 30 13:22 UTC 1993 |
Hmm, very strange. Pico still works fine for me -- I use 'xterm' as
my usual termcap, but also tried 'vt100' and 'ansi-new' and experienced
no problems. Looked at scg's and davel's login initialization files,
and they look okay too.
|
remmers
|
|
response 16 of 55:
|
Jun 30 13:54 UTC 1993 |
After looking at davel's report of what works and what doesn't, I
think it's a parity problem. The control codes that don't work
all have ascii codes with ODD parity, and the ones that do have
EVEN parity. It appears that Pico is looking at all 8 bits of
the character when it processes a command instead of ignoring the
parity bit like it should.
So maybe your comm. program is sending even parity? If so, try
changing it to "none" and see if that fixes things.
|
davel
|
|
response 17 of 55:
|
Jun 30 14:03 UTC 1993 |
I found out something useful, but I have no idea whatsoever about what to
do about it. I'm running a 7E because Grex gives me garbage at 8N
(apparently setting the 8th bit on output). I went into Pico & got the
specified behavior. I entered a bit, then did ^G for help & got the
unknown command message. I then switched my settings to 8N and tried
^G again. I got help. After exiting help, I used ^X to exit, and when
it asked me whether to save, I said n (lower case) & it apparently
exited - I just got garbage, presumably from more ordinary Grex functions.
(In the course of resetting again I managed to hang up & had to call in
again, so I can't be *sure*.)
I don't know why at 8n Pico is apparently able to avoid setting that 8th
bit but most of Grex is not. I presume that on input Pico is interpreting
the parity bit as a data bit, whereas most Grex functions just strip it.
That's the extent of my understanding of what's going on. Possibly I would
need to use Mark or Space parity instead of Even to have it work both ways?
I really don't know what those two settings do.
In any case, presumably the commands that were recognized are the ascii
characters whose parity bits happened to come out 0. Good thing ^X was
one of them.
|
davel
|
|
response 18 of 55:
|
Jun 30 14:04 UTC 1993 |
John slipped in, with the same conclusion I reached.
|
remmers
|
|
response 19 of 55:
|
Jun 30 21:55 UTC 1993 |
Great minds run in the same channels, y'know.
|
scg
|
|
response 20 of 55:
|
Jul 1 00:22 UTC 1993 |
I tried N7, hoping that that would work in both, but that just made Pico
totally functionless. Is there anything that I could try to make it work
in both Pico and other grex things? E7 only works in other grex functions,
and 8N only works in Pico.
|
scg
|
|
response 21 of 55:
|
Jul 1 00:23 UTC 1993 |
Also, why would Pine, which uses Pico as the editor, work, while Pico alone
does not?
|
davel
|
|
response 22 of 55:
|
Jul 1 10:06 UTC 1993 |
Does pine actually call pico, or is pico the composer module extracted &
separately compiled (possibly with slightly different options or a slightly
different rev for that matter)?
|
davel
|
|
response 23 of 55:
|
Jul 1 10:16 UTC 1993 |
At least from a quick test, using SPACE parity seems to work. Again, I'm
not sure what this setting really means, so I make no guarantees.
|
davel
|
|
response 24 of 55:
|
Jul 1 10:20 UTC 1993 |
And Procomm's doc suggests using N81 and using their "translate table"
feature (which allows custom translation for incoming characters) to strip
the high bit off each character in the range 128-255. (That is, first you
have to enter the table values for each of those.)
|