[warra]

When I connect to my school's server to access files, I tried using pico but when I type "pico filename.ext", I just get the error message "Incomplete terminfo entry". Whats the problem?

[Thinine]

You sure that's Darwin? I've never gotten a "Incomplete terminfo entry." error in the 5 years I've been using OS X. What are the contents of your .profile or equivalent?

[warra]

well i use jellyfissh to connect to the server which uses Darwin. So i guess by saying I use the terminal is more appropriate.

Thanks for the quick reply btw.

[nonhuman]

Just use emacs.

[larkost]

So... you are using JellyFish to connect to another computer (a server at your college), and it is then telling you that your account there has some settings problems.

This is probably not a Darwin issue at all (unless the server is running Darwin or MacOS X), and is one you need to talk to your tech support there about.

[warra]

Originally Posted by nonhuman

Just use emacs.

I can't use emacs through Darwin either, but yea, I guess I'll talk to one of the admins here. Thanks

[nonhuman]

Originally Posted by warra

I can't use emacs through Darwin either, but yea, I guess I'll talk to one of the admins here. Thanks

Does emacs give you the same error? Can you do anything at all?

If you're just using ssh, why not go in through the terminal?

[[APi]TheMan]

I agree, try it through Terminal.app... I've never used JellyFissh, but it sounds like you may have some environment variables screwed up (those things are usually set automatically, so it's probably not something you did).

Try connecting to the server through ssh in the terminal instead:

Code:
[theman@thefro: ~]$ ssh -l theman some.server.edu

[rwhiffen]

Jellyfissh simply envokes terminal.app with the ssh string entered. It's not jellyfissh that's doing it.

For example, when I run my freeshell.org book mark, it opens terminal.app and runs:
ssh -c 3des -2 -l rwhiffen tty.freeshell.org -p 22;exit

What I think you need to find out is what is the value of $TERM when you get logged in. Next time you're logged in type .

Code:
echo $TERM

and let us know what it says your TERM variable is set to. I suspect it's getting set to xterm or some other terminal type the host doesn't quiet like (check the preferences when you have the ssh session open). Depending on your shell, you should be able to set TERM to vt100 and try that. For eample:

in sh, bash and ksh:
.

Code:
TERM=vt100;export TERM

in csh and tcsh would be
.

Code:
setenv TERM vt100

And then try pico. vt100 is pretty generic and should get you on your way. Alternatively, you could run iTerm instead of terminal.app:
http://iterm.sourceforge.net/

Very slick OS X terminal app. Supports tabbed terminal sessions and a few other goodies.

Let us know what you find,

Cheers,

Rich