public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Earnie Boyd <earnie_boyd@yahoo.com>
To: Geoff Hart <ghart@siemens-psc.com>, cygwin@sourceware.cygnus.com
Subject: Re: xterms and vi
Date: Tue, 31 Aug 1999 23:49:00 -0000	[thread overview]
Message-ID: <19990810234737.25494.rocketmail@web117.yahoomail.com> (raw)
Message-ID: <19990831234900.OqXps9BjXpJox11H3E7WwI8OuxcZX36jPvkK_0IECYo@z> (raw)

--- Geoff Hart <ghart@siemens-psc.com> wrote:
> >>I've got the X11R6.4 client libs downloaded and installed, and am trying
> to
> >>run vi within an xterm.  The problem is that programs like vi (and ftp)
> >>don't do their I/O in the xterm, they do it in the DOS window associated
> >>with the xterm.
> >>
> >>I've set CYGWIN32 (and CYGWIN) to be 'binmode tty', and have an entry in
> my
> >>termcap file for xterm (although the symptom appears no matter what type
> of
> >>terminal I've set TERM to be).
> 
> >It sounds like you've forgotten to use cygwin versions of ftp and vi.  It's
> >unlikely that windows-only versions of those programs will work with the
> >CYGWIN=tty scheme.
> 
> Why is that unlikely?  I mean, can we make an "xterm" which acts both as a
> tty for Cygwin tools, *and* as a DOS console window for DOS applications?
> 

Windows doesn't understand the UNIX terminal structures.

Try a recent snapshot of the cygwin1.dll.  SET CYGWIN=notty and see what
happens.  I think you'll be surprised.  The terminal emulation has been
rewritten.

Note: Make the appropriate backups before installing.  Strangeness has been
noted with interactive bash or sh starting another interactive bash or sh
process which Chris is pulling his hair out trying to fix.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
_____________________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

             reply	other threads:[~1999-08-31 23:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-10 16:47 Earnie Boyd [this message]
1999-08-10 17:49 ` Glenn Spell
1999-08-10 21:36   ` Chris Faylor
1999-08-31 23:49     ` Chris Faylor
1999-08-31 23:49   ` Glenn Spell
1999-08-10 17:52 ` Suhaib M. Siddiqi
1999-08-10 21:44   ` Chris Faylor
1999-08-31 23:49     ` Chris Faylor
1999-08-31 23:49   ` Suhaib M. Siddiqi
1999-08-11 10:48 ` Geoff Hart
1999-08-31 23:49   ` Geoff Hart
1999-08-31 23:49 ` Earnie Boyd
  -- strict thread matches above, loose matches on Subject: below --
1999-08-10 15:08 Geoff Hart
1999-08-31 23:49 ` Geoff Hart
1999-07-15  6:38 Ryan L McFall
1999-07-15  7:17 ` Suhaib M. Siddiqi
1999-07-31 18:34   ` Suhaib M. Siddiqi
1999-07-15 11:52 ` Chris Faylor
1999-07-16  8:10   ` Ryan L McFall
1999-07-31 18:34     ` Ryan L McFall
1999-07-31 18:34   ` Chris Faylor
1999-07-31 18:34 ` Ryan L McFall

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=19990810234737.25494.rocketmail@web117.yahoomail.com \
    --to=earnie_boyd@yahoo.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=ghart@siemens-psc.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).