X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4978E71D.3040200@gmail.com>
Date: Thu, 22 Jan 2009 21:37:33 +0000
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: environment problems mixing mintty and xterm
References: <20090122162349 DOT GA2796 AT ingber DOT com>
In-Reply-To: <20090122162349.GA2796@ingber.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Lester Ingber wrote:
> However, if I run mintty from my xterm window I have some problems.
> 
> For example, say I have open xterm (from startxwin.csh) with
> xterm +tb -j -sb -geometry 80x84-6+0 &
> this sets LINES set to 84.
> 
> If I have set up .minttyrc with
> Rows=100
> then after I go to my mintty window and back to my xterm, my xterm window
> is messed up, e.g., top rows under `less` are off the screen.
> 
> There is no such problem, when running xterm, if I open an additional
> mintty window as a Windows shortcut since it seems to open independently
> -- without taking on the environment variables in my xterm window.

Thanks for the problem report, although I'd prefer to get these via the 
issue tracker at http://code.google.com/p/mintty/issues/ .

Unfortunately I haven't been able to reproduce the problem. A Unix 
process only receives copies of its parent's environment variables and 
it cannot change the originals, so the problem isn't caused that way.

Window size changes are signalled to the child process through a call to 
ioctl() on the child's pseudo terminal (pty), which triggers a SIGWINCH 
signal in any processes controlled by that pty. Perhaps something is 
going awry there.

Does the LINES variable in the xterm change immediately after invoking 
mintty, when you change mintty's size, or only after exiting it? What 
command line are you invoking mintty with?

Andy


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/