From: "Brooks, Stephen" <stephen.brooks@intervoice-brite.co.uk>
To: "'Bruce Dobrin'" <dobrin@imageworks.com>,
cygwin mailing list <cygwin@cygwin.com>
Subject: RE: Terminal settings for rsh/telnet to remote
Date: Wed, 15 Aug 2001 00:30:00 -0000 [thread overview]
Message-ID: <7D90C72D2739D311B4DA0090279361BD0195ED99@itmailman1.man.brite.co.uk> (raw)
You can always try "eval $(resize)" to set the terminal size correctly. TERM
needs to be set to xterm....
> -----Original Message-----
> From: Bruce Dobrin [ mailto:dobrin@imageworks.com ]
> Sent: 14 August 2001 20:24
> To: cygwin mailing list
> Subject: Terminal settings for rsh/telnet to remote
>
>
> (using cygwin 1.3.2)
>
> Hi,
>
> I know I've seen similar things like this before in this
> list, but none of
> the solutions seem to be working for me....
> Does anyone have a suggestion as to how I can get the rxvt or cygwin
> terminal or something else to work correctly when rsh-ing to
> UNIX? Am I
> doing something wrong (probably)? Could anyone steer me in the right
> direction?
> I've been trying for quite some time now to use cygwin
> terminal and/or rxvt
> and/or xterm for rshelling to the Irix, sun, and linux boxes
> in my facility.
> I thought rxvt would be the answer, but I still go through
> hell trying to
> edit files on the remote system. In rxvt (x11 and
> standalone), and xterm
> usually, I end up with either spurious characters, improper cursor
> placement, or only half a page, not always initially, but
> eventually.
> Or, if I work through these problems, and log out of the
> remote machine,
> then the local session is screwy (often refusing to scroll).
> as long as I
> don't launch vi or man, I'm usually ok...
>
> examples of things I've tried are: in a local rxvt window:
>
> (on local cygwin box)
> setenv TERM rxvt-cygwin
> tset -s rxvt-cygwin
> rsh (UNIX or Linux box)
> setenv TERMINFO ~/.terminfo (previously setup using
> terminfo-src-5.2-4)
> setenv TERM rxvt-cygwin
> tset -s rxvt-cygwin
>
> results here are a bit better than using xterm, but I still
> have a hard
> time getting through a file using vi.....
>
> I searched out google "terminal setup rxvt site:cygwin" an
> "ncurses remote
> terminal site:cygwin" and many permutations of those without
> coming up with
> a solution that seemed to work. What am I doing wrong?
>
> thanks for your time:
> Bruce Dobrin
>
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-08-15 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 0:30 Brooks, Stephen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 12:24 Bruce Dobrin
2001-08-14 12:32 ` Mark Paulus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7D90C72D2739D311B4DA0090279361BD0195ED99@itmailman1.man.brite.co.uk \
--to=stephen.brooks@intervoice-brite.co.uk \
--cc=cygwin@cygwin.com \
--cc=dobrin@imageworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).