Martin GräßlinOn Wednesday 07 May 2014 10:11:37 wrote:
Any advice on how to handle this situation is appreciated.
As several people responded that I should report the issues I just did that
and reported the following bug reports against GTK:
* CSD styled windows don't react on compositing
https://bugs.kde.org/show_bug.cgi?id=328593
--- Comment #3 from Martin Gräßlin mgraess...@kde.org ---
I would close it. I'm sure there are issues but I would say they are mostly
in kwin now.
KWin is regressing on dual screen too.
Please give a try to
I would close it. I'm sure there are issues but I would say they are mostly
in kwin now.
KWin is regressing on dual screen too.
Please give a try to https://git.reviewboard.kde.org/r/117614/
I'm unsure about whether I want to ship it, but we need to do something.
QDesktopWidget has
On May 7, 2014, 7:31 p.m., Thomas Pfeiffer wrote:
Okay, usability review. Some recommendations, some questions:
- This right now only has these options because adding wallpapers or
Plasmoids simply wasn't implemented yet and will get more settings once
they are implemented, right?
-
See http://build.kde.org/job/plasma-workspace_master_qt5/164/changes
Changes:
[notmart] undefined stuff--
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 1 (PACKAGER LINBUILDER) in workspace
On Wednesday 07 May 2014 15:10:00 Aleix Pol wrote:
Git commit 1cb38cd86f50424574e246b1816f72274c5799ce by Aleix Pol.
Committed on 07/05/2014 at 15:08.
Pushed by apol into branch 'master'.
Introduce libkscreen as a feature of Plasma Workspace
my plasma-workspace build is now failing due to
https://bugs.kde.org/show_bug.cgi?id=328593
--- Comment #4 from Martin Klapetek mklape...@kde.org ---
Actually now after the kscreen merge, I see new bugs wrt to multi-screen, I'll
file them and make them block this one for tracking.
--
You are receiving this mail because:
You are on the CC
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117893/#review57556
---
Ship it!
Ship It!
- David Edmundson
On April 30, 2014,
https://bugs.kde.org/show_bug.cgi?id=328593
Martin Klapetek mklape...@kde.org changed:
What|Removed |Added
Depends on||334498
--
You are
https://bugs.kde.org/show_bug.cgi?id=328593
Martin Klapetek mklape...@kde.org changed:
What|Removed |Added
Depends on||334500
--
You are
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118013/#review57557
---
ksmserver/screenlocker/kcfg/kscreensaversettings.kcfg
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118013/#review57558
---
Ship it!
...but that would probably rename the autogenerated
https://bugs.kde.org/show_bug.cgi?id=328593
Martin Klapetek mklape...@kde.org changed:
What|Removed |Added
Depends on||334502
--
You are
On May 8, 2014, 11:35 a.m., David Edmundson wrote:
...but that would probably rename the autogenerated KScreenSaverSettings
class name and you'd have to adjust loads of code.
Your choice.
Ship it from me.
I'll give it a try. Should be possible with the kcfgc file.
- Martin
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118038/#review57560
---
ksmserver/screenlocker/kcm/CMakeLists.txt
On May 8, 2014, 11:38 a.m., Burkhard Lück wrote:
ksmserver/screenlocker/kcm/CMakeLists.txt, line 2
https://git.reviewboard.kde.org/r/118038/diff/2/?file=271973#file271973line2
You define a TRANSLATION_DOMAIN screenlocker_kcm here, but where is the
Messages.sh to ectract strings
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118012/#review57561
---
Ship it!
- David Edmundson
On May 6, 2014, 8:06 a.m.,
On Thu, May 8, 2014 at 10:47 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Wednesday 07 May 2014 15:10:00 Aleix Pol wrote:
Git commit 1cb38cd86f50424574e246b1816f72274c5799ce by Aleix Pol.
Committed on 07/05/2014 at 15:08.
Pushed by apol into branch 'master'.
Introduce libkscreen as
Hey all,
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
it's well tested with that, as opposed to Qt 5.2.x.
Should the decision be against it, we should checkout Qt 5.2 and start
It also needs to be added on jenkins, otherwise the build will keep failing
there too.
Cheers
--
Martin Klapetek | KDE Developer
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Thursday 08 May 2014, Aleix Pol wrote:
I added it to dependency-data file, I thought it would be enough.
David is adding it to kdesrc-build, because he's a greay guy. :D
is libkscreen master already kf5?
last time i built was still from frameworks branch..
I think it's not good at all at
On Thursday 08 May 2014, Martin Klapetek wrote:
Hey all,
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
it's well tested with that, as opposed to Qt 5.2.x.
Should the
On Thu, May 8, 2014 at 12:44 PM, Martin Klapetek
martin.klape...@gmail.comwrote:
Hey all,
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
it's well tested with that, as opposed
What's the implications of this for Plasma Next? I guess we'll delay for 1
month, right? Or we want to depend on beta3 for the first release?
Aleix
-- Forwarded message --
From: Kevin Ottens er...@kde.org
Date: Mon, May 5, 2014 at 8:57 PM
Subject: KDE Frameworks: There will be a
On Thursday 08 May 2014, Aleix Pol wrote:
What's the implications of this for Plasma Next? I guess we'll delay for 1
month, right? Or we want to depend on beta3 for the first release?
Aleix
that's what I already asked some days ago...
I really don't feel that good depending on beta3 :/
--
On Thursday 08 May 2014 12:57:16 Marco Martin wrote:
On Thursday 08 May 2014, Aleix Pol wrote:
What's the implications of this for Plasma Next? I guess we'll delay for 1
month, right? Or we want to depend on beta3 for the first release?
Aleix
that's what I already asked some days
On Thursday 08 May 2014 12:44:29 Martin Klapetek wrote:
Hey all,
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
it's well tested with that, as opposed to Qt 5.2.x.
Should
Currently we have..
Fri, 9th May: Beta
Tue, 27th May: RC1
Thu, 29th May: Artwork freeze
Tue, 10th June: Tagging Plasma 2014.6
Tue, 17th June: Plasma 2014.6 Final
I propose..
Thursday June 5, Beta 2 tars, release on Monday 9th
Thursday July 3, RC tars, release on Monday 7th
Thursday July
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118049/
---
Review request for Plasma.
Repository: plasma-workspace
Description
On Thursday 08 May 2014 12:41:24 Aleix Pol wrote:
On Thu, May 8, 2014 at 10:47 AM, Martin Gräßlin mgraess...@kde.org wrote:
On Wednesday 07 May 2014 15:10:00 Aleix Pol wrote:
Git commit 1cb38cd86f50424574e246b1816f72274c5799ce by Aleix Pol.
Committed on 07/05/2014 at 15:08.
Pushed by
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117893/#review57576
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117893/
---
(Updated May 8, 2014, 11:12 a.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/165/changes
Changes:
[mgraesslin] Add unit test for kscreenlocker_greet to test all signals
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118049/#review57577
---
Ship it!
That does indeed seem pointless.
In fact this
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118049/
---
(Updated May 8, 2014, 11:16 a.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118049/#review57578
---
This review has been submitted with commit
See http://build.kde.org/job/plasma-workspace_master_qt5/166/changes
Changes:
[mklapetek] Remove useless timer from systray, which only closes the popup in
10ms
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building
On May 8, 2014, 11:31 a.m., David Edmundson wrote:
ksmserver/screenlocker/kcfg/kscreensaversettings.kcfg, line 6
https://git.reviewboard.kde.org/r/118013/diff/1/?file=271758#file271758line6
it's bit odd having an rc that is a different name to the .kcfg file
renaming is possible
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118013/#review57580
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118013/
---
(Updated May 8, 2014, 11:31 a.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/167/changes
Changes:
[mgraesslin] [screenlocker] Drop unused greeter.h and greeter.cpp
[mgraesslin] [screenlocker] Drop config option ScreenSaverEnabled
[mgraesslin] [screenlocker] Drop SuspendWhenInvisible configuration key
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118051/
---
Review request for Plasma, David Edmundson and Thomas Pfeiffer.
On Thursday, May 08, 2014 12:04:02 Jonathan Riddell wrote:
Thursday June 5, Beta 2 tars, release on Monday 9th
Thursday July 3, RC tars, release on Monday 7th
Thursday July 10, Final tars, release on Monday 14th
Releasing on Tuesdays is better for press impact, so I'd suggest moving them
On Thursday, May 08, 2014 12:44:29 Martin Klapetek wrote:
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
it's well tested with that, as opposed to Qt 5.2.x.
Should the
+1
2014-05-08 9:25 GMT-03:00 Sebastian Kügler se...@kde.org:
On Thursday, May 08, 2014 12:44:29 Martin Klapetek wrote:
Qt 5.3 is out on 20th May; should we hard depend on it in plasma with the
first release?
Given we've all been using Qt from git, I think this makes much sense as
2014-05-08 9:31 GMT+02:00 Martin Gräßlin mgraess...@kde.org:
Martin GräßlinOn Wednesday 07 May 2014 10:11:37 wrote:
Any advice on how to handle this situation is appreciated.
As several people responded that I should report the issues I just did that
and reported the following bug reports
Have there been any form of reply from them? At least something so we can gage
the level of interest in the subject?
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Thursday 08 May 2014 14:42:17 Jens Reuterberg wrote:
Have there been any form of reply from them? At least something so we can
gage the level of interest in the subject?
not yet, but given from the time of the replies in David's bug report I do not
expect anything before tomorrow morning.
On Thursday, May 08, 2014 14:39:49 Matthias Klumpp wrote:
However, to support the cross-desktop efforts, the GNOME people should
maybe make a few compromises (e.g. make GTK+ behave differently on
other DEs), especially since GTK+ is not just for GNOME but also used
by other projects.
This is
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118051/#review57585
---
Ship it!
Review is fine from a coding POV.
- David
On Thursday 08 May 2014 14:39:49 Matthias Klumpp wrote:
2014-05-08 9:31 GMT+02:00 Martin Gräßlin mgraess...@kde.org:
Martin GräßlinOn Wednesday 07 May 2014 10:11:37 wrote:
Any advice on how to handle this situation is appreciated.
As several people responded that I should report the
https://bugs.kde.org/show_bug.cgi?id=328593
Bug 328593 depends on bug 334498, which changed state.
Bug 334498 Summary: Panel struts are not being set in multiscreen
https://bugs.kde.org/show_bug.cgi?id=334498
What|Removed |Added
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117767/
---
(Updated May 8, 2014, 1:32 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118051/#review57586
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118051/
---
(Updated May 8, 2014, 1:33 p.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/168/changes
Changes:
[mgraesslin] [screenlocker] Remove autologout functionality
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 4
https://bugs.kde.org/show_bug.cgi?id=328593
Bug 328593 depends on bug 334500, which changed state.
Bug 334500 Summary: plasmoid.screen returns -1 in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=334500
What|Removed |Added
See http://build.kde.org/job/plasma-workspace_master_qt5/169/changes
Changes:
[notmart] less undefined variable access
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER)
See http://build.kde.org/job/plasma-workspace_master_qt5/170/changes
Changes:
[aleixpol] remove pointless output
[aleixpol] Remove hack for early initialization of PanelView
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
See http://build.kde.org/job/khotkeys_master_qt5/23/changes
Changes:
[jr] set soversion to 5
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER) in workspace
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118053/
---
Review request for Plasma.
Repository: plasma-workspace
Description
https://bugs.kde.org/show_bug.cgi?id=328593
Bug 328593 depends on bug 334502, which changed state.
Bug 334502 Summary: Panel positions in multiscreen are not remembered/placed
depending on mouse position
https://bugs.kde.org/show_bug.cgi?id=334502
What|Removed
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118053/#review57587
---
Ship it!
Ship It!
- Marco Martin
On May 8, 2014, 1:57
See http://build.kde.org/job/plasma-workspace_master_qt5/171/changes
Changes:
[notmart] item plasmoids can open the applet
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118053/#review57588
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118053/
---
(Updated May 8, 2014, 2:08 p.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/172/changes
Changes:
[mklapetek] Remove another timer from systray
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER
+1 for delay
+1
--
Make your code readable. Pretend the next person who looks
at your code is a psychopath and they know where you live.
-- Philip Wadler
___
Plasma-devel mailing list
Plasma-devel@kde.org
See http://build.kde.org/job/plasma-workspace_master_qt5/173/changes
Changes:
[notmart] make mouse wheel work again
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER LINBUILDER) in
See http://build.kde.org/job/plasma-workspace_master_qt5/174/changes
Changes:
[notmart] fix minimum height on vert panels
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER
See http://build.kde.org/job/plasma-workspace_master_qt5/175/changes
Changes:
[notmart] setScreen must be called with a valid containment
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3
See http://build.kde.org/job/plasma-workspace_master_qt5/176/changes
Changes:
[aleixpol] Fix crash
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER LINBUILDER) in workspace
I'd like to propose to change Krunner's default activation shortcut away
from Alt+F2 and keeping that as a secondary shortcut for legacy purposes in
Plasma Next
Reasons:
- F keys are very often mapped to multimedia/utility keys on laptops,
pressing Alt+F2 then requires pressing a
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117995/#review57591
---
ksmserver/screenlocker/autotests/CMakeLists.txt
+1 on the idea EXCEPT we have to think how much we want to promote
Krunner? Lets face it currently Krunner is something of a poweruser thing
(which is odd but thats the way its communicated for the moment) with
extensions to it something odd and weird.
I have Meta+Space personally but thats
On Thursday 08 May 2014 17:18:10 Martin Klapetek wrote:
I'd like to propose to change Krunner's default activation shortcut away
from Alt+F2 and keeping that as a secondary shortcut for legacy purposes in
Plasma Next
Reasons:
- F keys are very often mapped to multimedia/utility keys on
On May 8, 2014, 5:21 p.m., David Edmundson wrote:
ksmserver/screenlocker/autotests/CMakeLists.txt, line 30
https://git.reviewboard.kde.org/r/117995/diff/1/?file=271561#file271561line30
does running ctest in the build directory try to run this? We don't
want that to happen.
ctrl+space is taken by auto-completion in IDEs. You don't want to break my
workflow ;-) Alt+Space is window menu in GNOME. Maybe meta+space. For
those
remembering: what was it in Katapult?
and then can we market it like a prize winning hog at christmas?
On Thu, May 8, 2014 at 5:28 PM, Martin Gräßlin mgraess...@kde.org wrote:
ctrl+space is taken by auto-completion in IDEs. You don't want to break my
workflow ;-)
Ah true, haven't realized that.
Alt+Space is window menu in GNOME.
In Gnome or in Gnome apps running in Plasma?
Maybe
In data giovedì 8 maggio 2014 17:18:10, Martin Klapetek ha scritto:
- Change the shortcut to something that's more closely to each other
like Alt+Space or Ctrl+Space -- same row, no need to raise your palm
-1. Ctrl-Space is a common shortcut for (and I think default in some) input
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117770/
---
(Updated May 8, 2014, 3:43 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117770/#review57593
---
This review has been submitted with commit
On Thursday 08 May 2014, Martin Klapetek wrote:
I'd like to propose to change Krunner's default activation shortcut away
from Alt+F2 and keeping that as a secondary shortcut for legacy purposes in
Plasma Next
alt+space (or meta, even tough i would have to change that on my trusty old
IBM :p)
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117775/
---
(Updated May 8, 2014, 3:46 p.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/177/changes
Changes:
[notmart] try harder to center the icon(s)
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER
On Thursday 08 May 2014 17:36:32 Martin Klapetek wrote:
On Thu, May 8, 2014 at 5:28 PM, Martin Gräßlin mgraess...@kde.org wrote:
ctrl+space is taken by auto-completion in IDEs. You don't want to break my
workflow ;-)
Ah true, haven't realized that.
Alt+Space is window menu in GNOME.
See http://build.kde.org/job/plasma-desktop_master_qt5/147/changes
Changes:
[jr] use renamed keditfiletype5 binary
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 1 (PACKAGER LINBUILDER) in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117884/
---
(Updated May 8, 2014, 4:17 p.m.)
Status
--
This change has been
See http://build.kde.org/job/plasma-workspace_master_qt5/178/changes
Changes:
[jr] use renamed kioclient5
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 3 (PACKAGER LINBUILDER) in workspace
See http://build.kde.org/job/plasma-desktop_master_qt5/148/changes
Changes:
[jr] use renamed oxygen sound file
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 4 (PACKAGER LINBUILDER) in
See http://build.kde.org/job/plasma-desktop_master_qt5/149/changes
Changes:
[kensington] Install documentation into own subdirectory.
--
Started by remote host 2a01:4f8:160:9363::9 with note: Triggered by commit
Building remotely on LinuxSlave - 4
Ok I just want to know - is it ok if we market this? Because I can see it over
and over again in a promo video... hey shut up and press key+key and then
write what you need
Seriously just a yes and I will be on this like ... like... like Der Stijl
and colorful squares of paint! (yes that was a
On Monday, May 05, 2014 15:55:27 Sebastian Kügler wrote:
Take to kde-promo for further discussion
So it seems we're not unanimously, but pretty clearly in favor of the Plasma 5
proposal. I know it's never going to be perfect, but we have to move on at
this point.
I'll bring this up on
On Thursday 08 of May 2014 12:46:51 Marco Martin wrote:
On Thursday 08 May 2014, Aleix Pol wrote:
I added it to dependency-data file, I thought it would be enough.
David is adding it to kdesrc-build, because he's a greay guy. :D
is libkscreen master already kf5?
last time i built was
See http://build.kde.org/job/plasma-workspace_master_qt5/179/changes
Changes:
[notmart] first pieces for the manual show/hide config
[notmart] Configuration option to disable plasmoids is back
--
Started by remote host 2a01:4f8:160:9363::9 with note:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117859/#review57608
---
at least to me looks good. only unsure should
Meta+Space and Ctrl+Space are used by triggering input method by default
(fcitx, scim, gcin is using ctrl+space, while ibus is moving to meta+space
to be consistent with windows 8 IMHO), which should never be occupied by
global hotkey.
On Thu, May 8, 2014 at 12:34 PM, Jens Reuterberg
On Thu, May 8, 2014 at 12:46 PM, Marco Martin notm...@gmail.com wrote:
On Thursday 08 May 2014, Aleix Pol wrote:
I added it to dependency-data file, I thought it would be enough.
David is adding it to kdesrc-build, because he's a greay guy. :D
is libkscreen master already kf5?
last
On May 08, 2014 17:18:10 Martin Klapetek wrote:
Additional question - have you ever changed krunner's shortcut in your
setup?
Can't let a bikeshedding oportunity like this pass by unnoticed...
I changed it to Win+R over ten years ago and never looked back. :)
That's the shortcut used on MS
99 matches
Mail list logo
