Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Jul 2009 14:12:25 +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:  <3a142e750907010512x20667f5by864bbce6d2c7812@mail.gmail.com>
In-Reply-To: <permail-200907010954051e86ffa800003ad3-a_best01@message-id.uni-muenster.de>
References:  <3a142e750907010212t61001359md700e573147ea00b@mail.gmail.com> <permail-200907010954051e86ffa800003ad3-a_best01@message-id.uni-muenster.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7/1/09, Alexander Best <alexbestms@math.uni-muenster.de> wrote:
> oh. i see. is this hard to fix? maybe a problem report would be useful?

Not hard. Please report problem to freebsd developers because everything
points it is FreeBSD problem.

>
> cheers.
>
> Paul B. Mahol schrieb am 2009-07-01:
>> 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?3a142e750907010512x20667f5by864bbce6d2c7812>