"Although dragging could be done by relative movements. Setting an absolute position does appear to be impossible in Wayland."
If it was really impossibble, then how the Gnome shell or any window manager can position *itself*?
We see, that the diverse components of the diverse window managers does not float around in an uncontrolled way, but *somehow* they are able to tell to Wayland where to position that components.
The gnome-terminal should be able to do the same, either directly ask Wayland, or indirectly ask the window manager, in return of the --geometry argument.
Hence it is confirmed, that the problem in question is
1: either a severe bug of the windows manager itself
2: or a severe bug of the applications receiving the --geometry arguments.
I am extremly upset of keeping this bug report on the level of "opinion".
There are so uncomfortable problems around the terminal windowing since 21.04,
or the too thick capture bar of a terminal wastes the vertical space
that I seriousely consieder to change to other distro. My work depends heavily on the comfort of character terminals I became used to in the late 80's, and since 21.04 the level of comfort reached a treshold of pain.
And now, I can not achieve that this serious bug is taken seriously.
This bug crosses the basics of the windowing standars hold already for decades.
Perhaps one of the iconic feature of a windowing system is that an application can position the other windows.
This was possibble already in the mid 80's!
I simply do not understand what is going here around the Wayland, while on the other hand it seems to be a very promising progress in the technology of the windowing system. But why it is a so big issue to position a window by an other application?
"Although dragging could be done by relative movements. Setting an absolute position does appear to be impossible in Wayland."
If it was really impossibble, then how the Gnome shell or any window manager can position *itself*?
We see, that the diverse components of the diverse window managers does not float around in an uncontrolled way, but *somehow* they are able to tell to Wayland where to position that components.
The gnome-terminal should be able to do the same, either directly ask Wayland, or indirectly ask the window manager, in return of the --geometry argument.
Hence it is confirmed, that the problem in question is
1: either a severe bug of the windows manager itself
2: or a severe bug of the applications receiving the --geometry arguments.
I am extremly upset of keeping this bug report on the level of "opinion".
There are so uncomfortable problems around the terminal windowing since 21.04,
https:/ /bugs.launchpad .net/ubuntu/ +bug/1925823
https:/ /bugs.launchpad .net/ubuntu/ +bug/1928317
https:/ /bugs.launchpad .net/ubuntu/ +bug/1916890
https:/ /bugs.launchpad .net/ubuntu/ +bug/1888098
https:/ /bugs.launchpad .net/ubuntu/ +bug/1288655
or the too thick capture bar of a terminal wastes the vertical space
that I seriousely consieder to change to other distro. My work depends heavily on the comfort of character terminals I became used to in the late 80's, and since 21.04 the level of comfort reached a treshold of pain.
And now, I can not achieve that this serious bug is taken seriously.
This bug crosses the basics of the windowing standars hold already for decades.
Perhaps one of the iconic feature of a windowing system is that an application can position the other windows.
This was possibble already in the mid 80's!
I simply do not understand what is going here around the Wayland, while on the other hand it seems to be a very promising progress in the technology of the windowing system. But why it is a so big issue to position a window by an other application?