This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: base-[files|password] for 1.7


On Tue, Jul 29, 2008 at 01:59:54PM -0400, Christopher Faylor wrote:
>On Tue, Jul 29, 2008 at 05:18:32PM +0100, John Morrison wrote:
>>On Tue, July 29, 2008 3:57 pm, Corinna Vinschen wrote:
>>> On Jul 29 10:31, Christopher Faylor wrote:
>>>> On Tue, Jul 29, 2008 at 02:29:19PM +0200, Corinna Vinschen wrote:
>>>> >Chris, is there any good reason NOT to call send_winch_maybe on
>>>> >a key event?
>>>>
>>>> It only makes sense when there is a mouse event.
>>>
>>> I don't understand that.  Mouse events typically don't happen.  I can
>>> use the mouse as much as I want in a console window running vim, vim
>>> never gets the SIGWINCH.
>>>
>>>>   It would make more
>>>> sense to move the handling of SIGWINCH into the signal handler so that
>>>> the above works transparently.  I'll look into doing that.
>>>
>>> That would be a nice addition.
>>
>>So I don't need to add anything to /etc/profile?
>
>Adding the kill -WINCH still makes sense.  It will at least get things
>working for xterm and rxvt.

Ok.  I'm confused.  If I perform a "kill -SIGWINCH <pid>" on a bash
which is opened in a console window, the right number of lines shows up.
They also show up when you change the size of the window.

So it seems like this is working correctly without any Cygwin
modifications.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]