Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Jul 2009 11:12:27 +0200
From:      "Paul B. Mahol" <onemda@gmail.com>
To:        Alexander Best <alexbestms@math.uni-muenster.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: strange ee behaviour
Message-ID:  <3a142e750907010212t61001359md700e573147ea00b@mail.gmail.com>
In-Reply-To: <3a142e750907010154n8b2417dw4d480876c89ddbca@mail.gmail.com>
References:  <3a142e750906301603i4088580djed9ce24713dfc541@mail.gmail.com> <permail-20090630233631f0889e8400002bfd-a_best01@message-id.uni-muenster.de> <3a142e750907010154n8b2417dw4d480876c89ddbca@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7/1/09, Paul B. Mahol <onemda@gmail.com> wrote:
> On 7/1/09, Alexander Best <alexbestms@math.uni-muenster.de> wrote:
>> i'm running xorg-7.4.2 and x11-wm/awesome on HEAD (r195173). when i run
>> ee
>> in
>> the debugger and open another xterm the debugger says "Program exited
>> normally.". so it's not a program crash i guess.
>>
>> Paul B. Mahol schrieb am 2009-07-01:
>>> On 6/30/09, Alexander Best <alexbestms@math.uni-muenster.de> wrote:
>>> > hi there,
>>
>>> > i'm experiencing this strange `ee` behaviour lately. when i open
>>> > `ee` in an
>>> > xterm and open another xterm `ee` simply exits. if i try to enter
>>> > commands
>>> > which output to sdtout/stderr like `ls` on the xterm window ee was
>>> > running
>>> > on
>>> > the output is a mess.
>>
>>> > i'm running r195173 (HEAD).
>>
>>> Can't reproduce. Which X environment do you use?
>
> Actually I can, if I resize xterm window, ee will exit.
> You really should mentioned that you use awesome at first place.

Problems is that ee doesnt handle SIGWINCH properly.
ee on FreeBSD is linked with ncurses but new_curse.c from contrib/ee is
only file that mentions SIGWINCH and that file is not part of
usr.bin/ee/Makefile

-- 
Paul



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750907010212t61001359md700e573147ea00b>