Hi David. That is really a good news! Thx for working on this!

As I mentioned in T10568 we need IMHO better discoverability not yet another global shortcut.

FWIW I agree with David argument in the bug report and to reject the suggestion for 2 more global shortcuts.

-1 from my side.

Oh, maybe: prevent problems(?) with sh -> dash systems use the env tool:

What I usually use to tweak my systems:

FWIW: If that's the case, then the task should be maybe re-titled to one of:

+ 1 for Ctrl-Shift-0

Hi I think ctrl-<anything> is not a good idea in konsole. One never knows which app runs inside konsole and with shortcuts it uses. E.g. ctrl-0 in vim and bash emacs mode goes to the first char in the line.

Let's try to define what we^W I are trying to define:

Maybe it's worth to add to the describtion of this task:

IMHO instead of filing bug report for the apps, it may make more sense to first add a describtion of the 'right' behaviour to the KDE human interface guide line https://community.kde.org/KDE_Visual_Design_Group/HIG . Maybe a new phab task and invite the developers to the apps of the apps that do it 'right' and 'wrong' to the task?

If the 'plus' button is not shown again when changing back to 'single-click' mode: -1 for the change because it's bad for everyone switching back to single-click mode.

In case it's not hidden, but destroyed, create a new KMessageWidget?
Or maybe the 'close' button can be remapped to trigger a hide instead of destroy?

Other apps (dolphin, kmail) use the 'cross on red bg' button in the upper right corner to close the msg.

FWIW: My first imprression was that the dialog is too narrow. My 'rule' is : the most frequently entered URLs should fit into the dialog without scrolling to the left or the right. In this dialog the string '.flatpakrepo' seems to use already 30 % of the width. Not left for the rest.

In case the double-click proposal would be accepted, ...
IMHO we have to make sure that old installations keep their current behaviour.
AFAIU this would not be the case if we just set a new default.

We have to be careful when comparing screenshots

Reminds me ...

From my experience 50 % increase font size, 50 % keep it. Depends on who many young and older people you see using KDE.

I'm used to the 'blue' screens now and it's sort of unique. Some times I start thinking it's 'the' KDE blue (like Ferrari red). And then I'm proud ;-) Nevertheless using the default upstream wallpager is also okay.

As open animation: maybe like the unminimize animation with the origin wherever the click (or return in krunner) happened?

I turn it on and the frist window I closed, 'vanished' into a icon in dolphin that was behind the window. That was quite irretating.
The current animation is IMHO also not very nice (personal impression)

Despite that I disagree here with Nate, I want to say: a big bold thank you Nate! I'm really impressed by the great job you do in public relation and usablility! Thx a lot!

a big bold -1 from my side IMO. I use the effect every day when placing windows relative to each other that overlap.

Hi Allen, thx! AFAIU it's not commited, so I can't test it via kde neon dev stable or unstable :-( Nevertheless every language that displays the date in non-US format should be fine. So I guess adding Montel, Faure or Dvratil as reviewers should do the trick.

FWIW: I use the feature quite often when positioning windows over each other to make sure relevant information is not hidden when another window pops to the front. As the feature does not hurt when on: -1 for removing it.

If it's decided to go the /etc/skel route ( -1 from my side ;-) ) , remember that ~/.config has mode 0700 and config files 0600. Are permission fixed later if files from /etc/skel have wrong permission?

IMHO system defaults should make sense. Preconfigured config files in $HOME is IMHO not the way to go. /etc/skel doesn't fix the problem for all our existing users out there that already needlessly run akonadi. Config files in $HOME can also not changed via .deb postinstall

As qgetenv/getenv does not handle shell features like ${XDG_DATA_HOME:=~/.local/share} another solution may be: