Being unable to have a "non wrapping" cursor, i.e. a cursor that can move over the empty part of the screen left of the sources, makes block selection useless: you can select a block of text only as wide as it last or first line. This kills the easiest way I know to copy blocks of python source to the console for quick testing :-) Reproducible: Always
commits that removed this feature: - https://projects.kde.org/projects/kde/kde-baseapps/kate/repository/revisions/4019f0238c600a1834f5c97f373b0e4d63724e58 - https://projects.kde.org/projects/kde/kde-baseapps/kate/repository/revisions/cf0a6300fc8611f808e78f6ae4ca3b485fbe49e0 - https://projects.kde.org/projects/kde/kde-baseapps/kate/repository/revisions/c4744d0429cbfea752858efe16b36269471f2ace
I have experienced the same problem in Kate 3.10.1 in Opensuse 12.3.
related bug: #314687 Somehow the block selection should still be extendable. It would be ok to let the cursor stay at the end-of-line.
Created attachment 78633 [details] fix reverting old behaviour od block selection mode I tried to write a patch reverting the old behavior. Please see the resulting file attached. The patch works and seems not to break anything new. You can freely move the cursor, select, copy & paste data. The support of cursor past the end seems to be dropped in Kate for KDE 4.10. Eg., pressing 'enter' key creates a new line as expected, but the column (x-coordinate) is modified (to a value between 0 and previous position). /* Note for Gentoo users - to apply this patch, copy it to /etc/portage/patches/kde-base/katepart/ and re-emerge katepart */
*** Bug 321123 has been marked as a duplicate of this bug. ***
This bug has not yet been fixed? The patch I posted solves this bug and it is still applicable in master. Is something wrong with it? It has not been applied for over three months now.
(In reply to comment #6) > This bug has not yet been fixed? > The patch I posted solves this bug and it is still applicable in master. > Is something wrong with it? It has not been applied for over three months > now. Hi everyone, this message is to report that the bug affects me as well: from my side it's the single most important bug in kde that is affecting my productivity at the moment. I tested Jan's fix and I can confirm it works. I haven't noticed side effects yet.
Jan, please submit the patch to https://git.reviewboard.kde.org/ This makes it easier for Kate developers to comment on the changes. For more information, please see http://techbase.kde.org/Development/Review_Board
This is fixed in Kate master, that is Kate in KDE 4.12. The patch was rather huge, so I think it unlikely that this will be backported. The patches are: http://commits.kde.org/kate/cf8f8583e03c1d4c22685888b3a43c685c8a6d5e http://commits.kde.org/kate/7dc070ed3d1b3e6c6e2b901b252b5b25c9d50dfb http://commits.kde.org/kate/28d598d056c95d7b23fecdda14922f31de98bf3f http://commits.kde.org/kate/69f4ba86bec7d9ab0fe347d6ac9e04c24906af9a http://commits.kde.org/kate/b349a1ae0f890ed54d21439495df5b134acc7aea http://commits.kde.org/kate/f295df2bab951df9816b5ca70c9b5e0cc894872c http://commits.kde.org/kate/bdcb24b64ddc3e1ed4790fa625182be2d17a29f6 http://commits.kde.org/kate/18e47aa1be8004d6042b76398ce4d4fdcbbf243f http://commits.kde.org/kate/67427333b81e626354b5159a4ae6173977e017c2 Of course, we could also just reapply the proposed patch. But it would be not well-tested in the 4.11.x line... Christoph, thoughts on this?
I guess best to wait for 4.12 or to build yourself from kate.git, I am not that in favor on changing that now, given we have some "working" variant in master.
Ok, this implies wont-fix for KDE 4.10 and 4.11, but it's fixed in master, i.e. KDE 4.12. If you have KDE 4.11, you are encouraged to build Kate from sources, then you have the fixed variant: http://kate-editor.org/get-it/ (your system installation remains untouched)