Hi everybody,
I can confirm the latest upstream fixes made signalling work again.
Thanks @Carsten!
Kind regards,
Marc
Am 2020-09-02 14:26, schrieb Carsten Haitzler:
On Wed, 02 Sep 2020 13:55:03 +0200 "Marc (default)"
<m...@osknowledge.org> said:
It is correct that my xterm also goes full black when this happens. To
me it sounds related. Have you tried to resize using the mouse?
terminal apps in a terminal are another matter and they rely on
SIGWINCH -
update and rebuild efl and signal blocking will be fixed. it blocks
then
unblocks again before exec.
Kind regards,
Marc
Am 2020-09-02 13:25, schrieb Al Poole:
> I have something similar.
>
> With terminology. Using tmtui (as an example). Resize the window, the
> terminal does not update it goes black. I spoke to Billiob about it,
> but it
> seems it might be related to this?
>
> On Wed, Sep 2, 2020 at 10:57 AM Carsten Haitzler <ras...@rasterman.com>
> wrote:
>
>> On Wed, 02 Sep 2020 09:53:41 +0200 "Marc (default)"
>> <m...@osknowledge.org>
>> said:
>>
>> > Hi Carsten,
>> >
>> > I use the git master code just FYI.
>>
>> Then update and build again I fixed that to unblock again a few days
>> ago..
>> I
>> thought you were sticking to releases?
>>
>> > I can reproduce the resizing bug almost 100%. Anything I could do to
>> > debug the pixmap issue?
>>
>> Well
>> 1. reproducing it reliably every time
>> 2. start adding lots of printfs to find out what is going on in
>> e_pixmap.c,
>> e_comp.c, e_comp_x.c ... specifically where it gets the pixmap of a
>> window,
>> gets damage updates. reality is i don't know every point where it
>> should
>> have
>> some debug so adding it all in preemptively is just insane. you add as
>> you
>> go
>> and narrow down what you want to look into. logging also costs
>> performance
>> and
>> if it was always on it'd fill your disk up pretty quickly so it's the
>> kind
>> of
>> thing that gets logging added when needed.
>>
>> > Kind regards,
>> > Marc
>> >
>> > Am 2020-09-02 09:30, schrieb Carsten Haitzler:
>> > > On Wed, 02 Sep 2020 08:22:32 +0200 "Marc (default)"
>> > > <m...@osknowledge.org> said:
>> > >
>> > >> Hi everyone,
>> > >>
>> > >> I can no longer use CTRL+C in xterm. It just shows "^C" but does not
>> > >> quit the process. Could that somehow be related to any EFL /
>> > >> Enlightenment changes? I'm using the current git code.
>> > >
>> > > I don't think it would.
>> > >
>> > > Sure - changing ~/.Xmodmap and changing keyboard layout might change
>> > > what keys
>> > > are produced but "^C" is a typical sign that a control and C is
>> seen...
>> > > you can
>> > > text with xev. The issue is probably either xterm or terminfo/termcap
>> > > related
>> > > or the process.
>> > >
>> > > It could also have to do with ignoring the SIGINT that is sent by the
>> > > terminal
>> > > to the process that is running. As you don't use git master you won't
>> > > be
>> > > affected by a recent change in execcing that blocked signals at the
>> > > fork point
>> > > (the exec didn't reset the signal blocks so i added an unblock before
>> > > exec).
>> > > That code was in efl master for a few days at most, but again -
>> > > wouldn't apply
>> > > to you.
>> > >
>> > >> Another strange thing that has been around for some time is the fact
>> > >> that I cannot "type" into an xterm when it is resized by ie. ALT+F2 to
>> > >> expand to the screen width. When I type nothing is displayed at first,
>> > >> but it is actually captured so when I hit ENTER the command gets
>> > >> executed. Once I hit ALT+F2 again and the xterm is resized to its
>> > >> previous, origininating window size the output gets visible. But:
>> when
>> > >> I
>> > >> resize the window by CTRL+ALT+mouse-grab to any size (wether to the
>> > >> screen width or just a little bit in any direction) the contents are
>> > >> immediately visible.
>> > >
>> > > I have seen this - somehow the pixmap isn't being updated. a resize to
>> > > get a new
>> > > pixmap by name then works. I don't know why. It's basically rare and
>> > > happens
>> > > once every few weeks to me so it's essentially impossible to track
>> down
>> > > because
>> > > of that.
>> > >
>> > >> xterm version is 357.
>> > >>
>> > >> Thank you for any feedback on this.
>> > >>
>> > >> Kind regards,
>> > >> Marc
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> enlightenment-users mailing list
>> > >> enlightenment-users@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>> > >>
>> >
>> >
>> > _______________________________________________
>> > enlightenment-users mailing list
>> > enlightenment-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>> >
>>
>>
>> --
>> ------------- Codito, ergo sum - "I code, therefore I am"
>> --------------
>> Carsten Haitzler - ras...@rasterman.com
>>
>>
>>
>> _______________________________________________
>> enlightenment-users mailing list
>> enlightenment-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>>
>
> _______________________________________________
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
