A bit OT: vi in telnet session

A bit OT: vi in telnet session

[Andreas Zielke]

Hi *,

I guess this posting is a bit off-topic, but I don't know any news-
group that would be more appropriate. (If you do, please tell me.)

When I telnet to a machine (running SunOS 5.7), using the telnet-
program that comes with 1.1.4 Cygwin an start vi I get this error-
message:

bash-2.03$ vi
cygwin: Unknown terminal type
Visual needs addressable cursor or upline capability
:

Is there a simple solution (like setting TERM to something else)
to this?

Thanks,
  Andreas

-- 
Andreas Zielke          mailto:andreas.zielke@sdm.de
sd&m AG                 http://www.sdm.de
software design & management
Thomas-Dehler-Str. 27, 81737 Muenchen, Germany
Tel +49 89 63812-562 Fax -490


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: A bit OT: vi in telnet session

[Vikas]

Andreas Zielke wrote:
> When I telnet to a machine (running SunOS 5.7), using the telnet-
> program that comes with 1.1.4 Cygwin an start vi I get this error-
> message:
> 
> bash-2.03$ vi
> cygwin: Unknown terminal type
> Visual needs addressable cursor or upline capability
> :

execute "bash$ set TERM=vt100" and done!
You can even set TERM to "linux" or "vt103".
check whether your telnet client supports it.
vi won't execute untill it knows the terminal type.
One way is the environment variable and the other way is through
command line like "bash$ vi -t vt100".

-- 
/*
** http://www.programmingParadise.com
*/
#Vikas Yadav, India
//PGP key: http://www.programmingparadise.com/misc/vikas.pgp
'E-mail:vikas@programmingparadise.com

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: A bit OT: vi in telnet session

[Vikas]

Ops!
I gave a wrong command line. It is "vi -T vt100". Capital 'T'.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

setting TERM=cygwin in non-cygwin unix [Was: Re: A bit OT: vi intelnet session]

[Jeffrey Juliano]

On Mon, 21 Aug 2000, Andreas Zielke wrote:

> I guess this posting is a bit off-topic, but I don't know any news-
> group that would be more appropriate. (If you do, please tell me.)

It can't hurt to get the answer into the mail archive.  This might even be
a FAQ from people learning unix via cygwin.

BTW, the answer applies no only to telnet, but also to ssh, rlogin, etc.


> When I telnet to a machine (running SunOS 5.7), using the telnet-
> program that comes with 1.1.4 Cygwin an start vi I get this error-
> message:
> 
> bash-2.03$ vi
> cygwin: Unknown terminal type
> Visual needs addressable cursor or upline capability

The quick answer is to set your TERM to vt100 or something else that's
pretty close.

The better answer is to make your non-cygwin unix machines aware of the
cygwin TERM type.  There are two ways to do this, depending on if your
unix machine uses termcap or terminfo.

You can get general info about termcap and terminfo by typing 'man
termcap' and 'man terminfo'.  Follow the see-also links for documentation
on the helper programs, including one that converts between termcap and
terminfo sytle information.  Read the manpages; everything you need to
know is there. You may want to ask your sysadmin if your systems use
termcap or terminfo. But they probably use terminfo.

If you use termcap, then you need to add a cygwin entry to the termcap
file.  If you use terminfo, then you need to add a cygwin entry to the
terminfo/c/ directory.

In my environment, we have solaris, irix, hpux, and linux machines.  I
don't have root privilege, so I do this in my home directory and set
TERMINFO env var to point to ~/terminfo.  I've placed into that dir the
terminfo files for any terminal I use.  It looks like this:

~/terminfo/c/cygwin
           i/iris-ansi
           i/iris-ansi-net
           v/vt100
           x/xterm

plus a few others.  Then, my startup files do a

   export TERMINFO=~/terminfo

If you want to be clever, you can set TERMINFO only if your term-type
isn't in the system-wide termfino directory.  That way you ensure that you
use the correct `xterm', if they differ among platforms.

-jeff


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

setting TERM=cygwin in non-cygwin unix [Was: Re: A bit OT: vi intelnet session]

[David Starks-Browning]

On Monday 21 Aug 00, Jeffrey Juliano writes:
> On Mon, 21 Aug 2000, Andreas Zielke wrote:
> 
> > I guess this posting is a bit off-topic, but I don't know any news-
> > group that would be more appropriate. (If you do, please tell me.)
> 
> It can't hurt to get the answer into the mail archive.  This might even be
> a FAQ from people learning unix via cygwin.

The Cygwin FAQ is not a UNIX primer.  However, given that the default
TERM=cygwin is unlikely to be known on most other UNIX systems, it
probably merits an entry.  (If it doesn't already have one...)

BTW, pointers to UNIX primers might indeed be good FAQ fodder.
But someone else will have to provide them.  It's been some years
since I began using 'man' instead.

Cheers,
David (Cygwin FAQ maintainer)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: setting TERM=cygwin in non-cygwin unix [Was: Re: A bit OT: vi intelnet session]

[Jeffrey Juliano]

David Starks-Browning wrote:
> 
> The Cygwin FAQ is not a UNIX primer.

I agree.

> However, given that the default TERM=cygwin is unlikely to be known
> on most other UNIX systems, it probably merits an entry.

As a datapoint, rxvt tells you how to do this in its documentation.  The
authors realized that a significant number of users won't just happen to
know what to do without a little help.  I don't see that as being too
different from the cygwin terminal description.  Actually, cygwin is a
little more obtuse because the recommended thing is not to set TERM.


> BTW, pointers to UNIX primers might indeed be good FAQ fodder.

Probably a good idea.  Or at least a section telling people to look in
the man/info pages before asking on the list.  But in this case, the
answer is as simple as "man term" on the two platforms I just tried. 
Given an appropriatly worded section in the FAQ (and if I knew enough to
look at the FAQ), I'd feel pretty silly if I asked in a public forum how
to find documentation about my term without first trying "man term". 
Now, "I tried `man term' but it was too much for me to digest" is another
matter--my opion would depend on your level of experience and wether or
not the FAQ points to unix primers.

Feel free to use my earlier email or derive from it to write a FAQ entry,
if you feel it's appropriate.

-jeff

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: A bit OT: vi in telnet session

[Neil Lunn]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

>From: Andreas Zielke <andreas.zielke@sdm.de>
>To: cygwin@sourceware.cygnus.com
>Subject: A bit OT: vi in telnet session
>Date: Mon, 21 Aug 2000 11:14:50 +0200 (Westeuropäische Sommerzeit)
>
>Hi *,
>
>I guess this posting is a bit off-topic, but I don't know any news-
>group that would be more appropriate. (If you do, please tell me.)

Yup! Off-topic all right

alt.unix, alt.solaris, comp.os.unix, comp.os.unix.misc, comp.unix.solaris

>
>Is there a simple solution (like setting TERM to something else)
>to this?
>

Yup! ansi, vt100 etc, etc. Anthing but cygwin, or create an entry for 
termcap!



________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: A bit OT: vi in telnet session

[Earnie Boyd]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

--- Andreas Zielke <andreas.zielke@sdm.de> wrote:
> Hi *,
> 
> I guess this posting is a bit off-topic, but I don't know any news-
> group that would be more appropriate. (If you do, please tell me.)
> 
> When I telnet to a machine (running SunOS 5.7), using the telnet-
> program that comes with 1.1.4 Cygwin an start vi I get this error-
> message:
> 
> bash-2.03$ vi
> cygwin: Unknown terminal type
> Visual needs addressable cursor or upline capability
> :
> 
> Is there a simple solution (like setting TERM to something else)
> to this?
> 

Why didn't you try your suggestion?  After telnetting, export TERM=<something
in the SunOS terminal database>.  You could try xterm, ansi, linux, vt100,
vt200, etc.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com