Summary: | Duplicate Lines Up/Down shortcuts overwritten | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | cegfault <cegfault> |
Component: | scripting | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | cegfault, cullmann, loh.tar, waqar.17a |
Priority: | NOR | ||
Version: | 22.04.1 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
cegfault
2022-05-27 16:18:08 UTC
I was was surprised und frustrated too that such long existing short cut is suddenly gone/changed. But you can customize these as you like. Contrary to restore to my old good known one, I use now Ctrl+. (dot) to duplicate down. Not sure why. Probably after some search what other editor use. > Acceptable fixes would be either: (a) allow a disable multicursors option to reset the shortcut, (b) set another shortcut for duplicate lines, or (c) allowing users to select/create a shortcut for duplicating lines
All this is possible from configure shortcut dialog.
> There is no shortcut now for duplicating lines.
It was a difficult decision that I made after long discussions. We didn't have a lot of choice and finding a new shortcut is not easy when you are a library (you can't break apps)
Yes, you can configure your own shortcut. Naturally that is a one time extra effort for people used to it, but unfortunately there are no endless shortcuts available for use for the stuff and we decided that to make the multi cursor stuff more discover-able it made sense to alter this. Well today I learned that I *can* override that shortcut, so that's resolved my issue. I guess as a philosophical issue I'd still say breaking userspace is *always* a bad idea, but it is what it is at this point. @Christoph - might I suggest that if you're going to do something like this in the future, at least post a blog or some other update on how to revert the change? I did try searching around first, and didn't see anything in the changelog or press release. At least letting people know how to modify/revert would have saved me hours of headache. Most Kate users are not power users :) > didn't see anything in the changelog or press release. At least letting people know how to modify/revert would have saved me hours of headache.
I doubt you even found a changelog or a release post. The reason being most of us were too busy this time around to compile all the changes and write a blog about it. We need more people stepping in and help us with all that's going on in Kate, especially marketing and co.
Naturally, inform users about any breaking change is a good thing. The point is, somebody must do it. I try to summarize some cool developments when I have time, unfortunately my time is lacking. If somebody steps up to provide nicer release texts, that would be great, one can even just publish a blog post before/after each KDE Gear release to summarize such stuff, but for that we need help. If I have the choice between actually fixing stuff and improving the code or writing blogs, I prefer the first. |