On Mon, 7 Sep 2020 14:10:57 -0700 Marc MERLIN <marc_...@merlins.org> said:
> On Mon, Sep 07, 2020 at 01:10:07AM +0100, Carsten Haitzler wrote: > > aha! well that was my idea for "try another one that probably doesn't go > > trying to move its own window wherever it wants". i know xterm and > > terminology will be well behaved and leave it up to the wm to decide what > > to do with placement and not try and second guess the wm. > > > > > I'm not sure why, but it was lost/gone from some windows. i'll put it > > > back and hopefully that will take care of things. > > > > that's why it exists. to tell badly behaving apps to "get lost". :) > > Ok, now I found my problem and why I was relying on the restart E to > reset windows trick: > 2/3rds of my terminals cannot seem to remember 'prevent this window from > moving on its own'. > I clicked it, I have remember the locks for this window, then click ok. > After restarting E, 'remember the locks for this window' is still active > but 'prevent this window from moving on its own' is unchecked. > > I have no idea why E doesn't remember settings for these windows. > One issue is that they all run under one single process > sauron:~$ psg terminal > merlin 14391 0.9 0.0 1048084 62396 ? RNsl 13:47 > 0:10 /usr/libexec/gnome-terminal-server > > But they get started with their own role > (sleep 5; $TN $TNN window1 --role=window1 ) & > (sleep 5; $TN $TNN window2 --role=window2 ) & > (sleep 5; $TN $TNN window3 --role=window3 ) & > (sleep 5; $TN $TNN window4 --role=window4 ) & > (sleep 5; $TN $TNN window5 --role=window5 ) & > (sleep 5; $TN $TNN window6 --role=window6 ) & > (sleep 5; $TN $TNN window7 --role=window7 --tab ) & > (sleep 5; $TN $TNN window8 --role=window8 --tab ) & > (sleep 5; $TN $TNN window9 --role=window9 --tab ) & > (sleep 5; $TN $TNN window10 --role=window10 --tab ) & > (sleep 5; $TN $TNN window11 --role=window11 --tab ) & > > (sleep 5; $TN $TNN window2.1 --role=window2.1 --tab ) & > (sleep 5; $TN $TNN window2.2 --role=window2.2 --tab ) & > (sleep 5; $TN $TNN window2.3 --role=window2.3 --tab ) & > (sleep 5; $TN $TNN window2.4 --role=window2.4 --tab ) & > (sleep 5; $TN $TNN window2.5 --role=window2.5 --tab ) & > > (sleep 5; $TN $TNN window3.1 --role=window3.1 --tab ) & > (sleep 5; $TN $TNN window3.2 --role=window3.2 --tab ) & > > and the role shows up under window remember/identifiers > I see 'window role' checked, and I see 'window2.3' in the name. it could be a race where gtk/gnome terminal is setting role AFTER it shows the window... so it's a pure luck/race condition that by the time e responds to the map request and reads the window properties role may or may not be set by that time. that is a possible reason. as i mentioned already... try with another terminal that i'm pretty sure is doing things right and see if the issue happens there too. elimination of possible things. > See screenshot attached. > Any idea why I'm hitting some saving bug on this lock property? > > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > > Home page: http://marc.merlins.org/ -- ------------- 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
