https://bugs.kde.org/show_bug.cgi?id=491923
kdeb...@toeai.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
--- Comment #4 from kdeb...@toeai.com ---
(In reply to Christoph Cullmann from comment #2)
> Hmm, we do to prefer to wrap at word boundaries. I don't see that we can
> have more fine grained control with Qt over this, if that is wanted, one
> must report that upstream to Qt. Did you alter the options to allow wrapping
> anywhere? e.g. 'Disregard word boundaries for...'? If yes, one might try to
> disable that, if not, I don't see that we will work on this.
No, I did have the 'Disregard word boundaries for dynamic wrapping' option
checked.
I guess I don't know enough about the internals of how lines are wrapped. If
you think this is something to report upstream, then exactly what type of
widget are we dealing with, and what are the options used for its creation?
Why I don't think it's something that could be reported upstream is because
it's language dependent, and syntax highlighting is a feature of Kate, not Qt,
right?
When it comes to other methods of determining words and word breaks, I know
that Kate has a way of messing with that. For some examples:
If you double-click on a "word" it selects the word. Without any special
syntax highlighting , a leading # on a word is selected along with the word.
But with syntax highlighting for Python, it is not, because the hash just
indicates a comment; it is not part of the first word in the comment.
Similarly, with syntax highlighting for C, if you double-click #include only
the letters "include" are selected, whereas the hash would also be selected
without the syntax highlighting.
If you press the right or left arrow keys while holding down the Ctrl key, it
moves the cursor one "word" at a time. With syntax highlighting of C or
Python, the cursor will move over a hash character (#) and any whitespace that
follows it in one move. But without any special syntax highlighting, the
cursor will (rather oddly) stop between the hash character and any whitespace
that follows it.
Are you telling me that Kate has control over what constitutes a "word" for
double-click selection and for cursor movement but not for wrapping? That just
seems odd.
--
You are receiving this mail because:
You are watching all bug changes.
