Since I was upset with Kmail always opening in fullscreen, I decided to let go of fixing things, and instead force it to do what I want through `Alt
f3` "configure special window settings".
So I just do that, and click OK, in the dialog, and then the screen flashes as it usually do in that specific situation, and then the "settings" window is gone, just as it does nowadays, and then I go in "settings" and "windows rules", in order to set the specific parameters I want it to assume, and then:
dah-dah! Nothing. Nothing it registered at the name "Kmail", or "Kmail2" as the dialog called it.
I already have four of them, three of them long standing, and one newly created, for firefox, which was stubbornly opening in very small window, and that I had to tame (as a matter of fact it started behaving like a bad application a few week ago too).
Anyway, I usually know how it works.
The long standing are emacs konsole and okular and are of the "application" persuasion.
The new one is of "window settings" sort.
Anyway, following these directions, it doesn't work, doesn't do anything;
but it duly flashes the screen, showing it did do some real work in the configure window setting line.
Weird.
I tell you if I have more data.
Chris
PS: I did `rm -rf ~/.kde4`, in order to remove all easy and safe to remove settings and config things, as I've been recently suggested to do, some
times before the above thing.
Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and then
did the action taking a snapshot of the windows properties, and then
selected "force" for the window size.
That sequence of action has just no effect at all.
Really it just seems as though, kmail2 is using another window manager altogether.
Is it?
Like it is using old components and is not integrating well with kwin?
Hey,
Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and then did the action taking a snapshot of the windows properties, and then selected "force" for the window size.
That sequence of action has just no effect at all.
Really it just seems as though, kmail2 is using another window manager altogether.
Is it?
Like it is using old components and is not integrating well with kwin?
the special window settings are only inside kwin and have nothing to do with the application you configure. That's why you can also modify GTK applications or tk applications. But on the other side there is this state storage of the windows, that may interfere in here. Have a look inside ~/.config/kmail2rc there you see this State keys, that represent the geometric representation of the windows. I would suggest to delete those
keys from kmail2rc, when kmail is not running.
hefee
On Wednesday, January 27, 2021 5:57:23 PM CET Sandro Knauß wrote:
Hey,
Now, since the constant opening of kmail2 in full screen mode is quite a pita, I went in system settings and created the rule from there, and
then
did the action taking a snapshot of the windows properties, and then selected "force" for the window size.
That sequence of action has just no effect at all.
Really it just seems as though, kmail2 is using another window manager altogether.
Is it?
Like it is using old components and is not integrating well with kwin?
the special window settings are only inside kwin and have nothing to do with the application you configure. That's why you can also modify GTK applications or tk applications. But on the other side there is this state storage of the windows, that may interfere in here. Have a look inside ~/.config/kmail2rc there you see this State keys, that represent the geometric representation of the windows. I would suggest to delete those keys from kmail2rc, when kmail is not running.
Thanks a lot for the suggestion, doing that asap.
hefee
Hey Norbert,
Should we cherry-pick the relevant fix commit https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd 43 2cc50432fefdb
Yes we should cherry-pick this one.
[2] https://bugs.kde.org/430521
Should we cherry-pick the relevant fix commit https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd43 2cc50432fefdb
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 216:52:07 |
Calls: | 6,621 |
Calls today: | 3 |
Files: | 12,171 |
Messages: | 5,317,619 |