D7497: Fix Ctrl PageUp/PageDown shortcut conflict due to KF 5.37.

Nathaniel Graham noreply at phabricator.kde.org
Tue Feb 13 22:54:38 UTC 2018

ngraham requested changes to this revision.
ngraham added a comment.
This revision now requires changes to proceed.

  My strong preference would be to change the shortcut in Katepart itself. The value of a systemwide shortcut like go to next/previous tab is diminished if individual apps override it due to conflicts. In these cases, the wiser course of action IMHO is to change the thing that it conflicts with
  Think of it this way:
  - If we make Kate deviate from the standard tab-changing shortcuts, we will get a steady stream of bug reports about the inconsistency, //forever//. I know because Gedit is in exactly <https://bugzilla.gnome.org/show_bug.cgi?id=737230> this <https://bugzilla.gnome.org/show_bug.cgi?id=705648> situation <https://bugzilla.gnome.org/show_bug.cgi?id=775375>.
  - If we change the move to [top,bottom] of view shortcuts in Katepart, we will get bug reports //once// from the few users who used the old shortcut, and once they have adapted or change the shortcut for themselves, thereafter nobody will ever again complain about anything pertaining to this matter.
  Option #2 gives us less work and headache over the long haul, and makes things better for any existing users who don't use the move to [top,bottom] of view shortcuts in Katepart-based apps.

  R40 Kate


To: dfaure, cullmann, ngraham
Cc: cfeck, ngraham, dhaumann, cullmann, kwrite-devel, #kate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20180213/c001b6a1/attachment.html>

More information about the KWrite-Devel mailing list