[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #14 from plane.wan...@gmail.com ---
(In reply to Christoph Feck from comment #13)
> That's not standard procedure. If you have an honest issue, report it.

The very first thing you did was assuming bad faith, which goes against your
code of conduct. You have absolutely no idea about any of my motives, because
you can't possibly know and shouldn't even care. But since you already made up
your mind that this isn't honest, despite me giving valid arguments that could
be discussed, you're effectively blocking me from participating. I hereby
remind you again about the code of conduct both you and me are supposed to
follow and ask you to get back on topic.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #13 from Christoph Feck  ---
That's not standard procedure. If you have an honest issue, report it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #12 from plane.wan...@gmail.com ---
Is this standard procedure here that bug reports are closed without any reason
given? I mean its stupid enough that people seem to care more about figuring
out my motives and questioning them, which btw. is a violation to your code of
conduct, than talking about my arguments, but its even worse if the request is
just dismissed without any comment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #11 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #10)
> >I could easily lie
> 
> It would take a very odd sort of person to be disingenuous on a bug tracker.

Then you can assume I'm telling the truth, but I don't know why an anecdote of
a single user should have any relevance whatsoever. Like does it make a
difference if I witnessed this issue 5 times, or 10 times? And how often is
enough for this to become important? Also the last time the same arguments were
used to justify the removal of similar features in KWin it didn't matter if it
actually happened to anyone.

> However, it seems cfecks initial comments were right.
> Thanks for wasting my time.

I didn't make this personal, I didn't make this OT, I didn't break any Code of
Conduct, all I did was putting forward arguments why destructive window
shortcuts are an issue in my oppinion. But instead of arguing about the issue,
which I'd much rather do, I have to deal with ad hominem attacks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

David Edmundson  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #10 from David Edmundson  ---
>I could easily lie

It would take a very odd sort of person to be disingenuous on a bug tracker.

However, it seems cfecks initial comments were right.
Thanks for wasting my time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #9 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #8)
> That's not what I meant, I meant if you've observed users accidentally
> closing windows this way

I don't think my answer to that question should matter given that I could
easily lie and there would be no way to prove me wrong. But for the sake of the
argument I'll say: Yes, I observed it many times that users lost some data this
way.

Imho the important question is if the arguments make sense and given that those
same arguments were used to remove similar features in KWin before I thought
that they indeed do make sense to the project's goals.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #8 from David Edmundson  ---
That's not what I meant, I meant if you've observed users accidentally closing
windows this way

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #7 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #6)
> Has this been an observed problem?

Yes, like I said it can be easily reproduced.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #6 from David Edmundson  ---
Has this been an observed problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #5 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #4)
> alt+f4 is not an easy to press shortcut.

That doesn't matter. An admin can change that shortcut to whatever they felt
like, e.g. , , ... which all do non-destructive
actions on other platforms, therefore users might accidentally trigger
destructive actions on KWin because they expected something else to happen for
those shortcuts. Therefore this feature needs to be removed - it's not
explicit/clear and might lead to data loss.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #4 from David Edmundson  ---
alt+f4 is not an easy to press shortcut.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #3 from plane.wan...@gmail.com ---
(In reply to Christoph Feck from comment #2)
> That's probably not a serious wish, but a prank related to bug 321190
> comment #2.

Prank or not doesn't matter, it's the arguments that matter. Those same
arguments were already used as a justification to remove similar functionality
from KWin before and I'm just trying to be consistent.

Either the arguments make sense, then they should be taken seriously, or they
don't then this whish can be ignored, but then other desicions might need to be
re-evaluated.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #2 from Christoph Feck  ---
That's probably not a serious wish, but a prank related to bug 321190 comment
#2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #1 from plane.wan...@gmail.com ---
*** Bug 406527 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.