https://bugs.kde.org/show_bug.cgi?id=439845
Christoph Cullmann <cullm...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cullm...@kde.org
--- Comment #6 from Christoph Cullmann <cullm...@kde.org> ---
Hi,
first: yes, the behavior can be improved for the case you have shown.
Beside this: as said, one can deactivate this variant of the cursor movement
and you are back to the "good old times".
Actually my proposal would be to just not split full lower or upper case words
with numbers at all.
e.g.
xxxxxx121212
XXXXXX123123
123123xxxxxx123123
123123XXXXXX123123
would all be just "one chunk" for the movement.
Btw., whereas such improvement wishes are appreciated, I think it would be
nicer if you could avoid just repeating that you think the behavior is "wrong".
Any such feature is a heuristics, there is no 100% precise definition how it
should behave. We can agree that one can improve this thought.
We work on this in our free-time and strong language/opinions won't help you to
motivate us to work on this.
Btw., if you are a programmer as mentioned, patches are really welcome.
Just search for CamelCursor in ktexteditor.git, we even have unit tests for
this feature.
--
You are receiving this mail because:
You are watching all bug changes.
