Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <00c601bf1b2e$e0819ee0$5a288018@ne.mediaone.net>
From: "Arthur  Goldhammer" <agold1@mediaone.net>
To: <cygwin@sourceware.cygnus.com>, "Joe Kraska" <jkraska@bbn.com>
References: <199910201904.MAA08315@ESCHER.SD.BBN.COM>
Subject: Re: rxvt and vim together
Date: Wed, 20 Oct 1999 15:11:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From the rxvt readme:

bugs:
- native-console accesses (ReadConsole(), WriteConsole()) are not supported.
    (read: vim doesn't work)

Maybe this explains the behavior you see. -- Art


----- Original Message -----
From: Joe Kraska <jkraska@bbn.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Wednesday, October 20, 1999 3:08 PM
Subject: rxvt and vim together


>
> From a bash window I start rxvt, and the window pops up
> just fine. I then run vim (the non gui version) from this rxvt
> window, but then the weirdest thing happens. The vim
> editor appears in the *bash* window. It boggles my mind,
> and perhaps has something to do with the rxvt not properly
> grabbing a tty entry or some such. Has anyone encountered
> this before? I would like to use rxvt exclusively, but this
> precludes this for the time being.
>
> Joe Kraska
> San Diego
> CA
>
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


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