https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #12 from Christoph Feck ---
Comment #11 is bug 407852.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370716
Diggory Hardy changed:
What|Removed |Added
CC||k...@dhardy.name
--- Comment #11 from Diggory
https://bugs.kde.org/show_bug.cgi?id=370716
FeepingCreature changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=370716
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #8 from Janek Bevendorff ---
It should have the same logic as the already existing bracket
matching/highlighting.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #7 from Sven Brauch ---
True yes, that should be a stack of saved ranges, not just one.
The other issue with what we're thinking about is that "has a corresponding
opening bracket" is a highly nontrival concept. What
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #6 from Janek Bevendorff ---
It somehow also doesn't eat brackets when a new pair has been inserted
within. So foo(bar(|)) will result in foo(bar())|) when typing ")"
twice. The inner bracket is
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #5 from Sven Brauch ---
That is the problem, yes. That's why current KTextEditor only eats closing
parentheses when you did not move your cursor out of the range between the two
parentheses before typing the closing one.
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #4 from Janek Bevendorff ---
I have to say, there are some corner cases where bracket eating has already
annoyed me in IntelliJ. This is mostly, when revising brackets within brackets.
But generally, this
https://bugs.kde.org/show_bug.cgi?id=370716
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=370716
--- Comment #2 from Janek Bevendorff ---
I think that's what IntelliJ does. It always "eats" the braces and
brackets as long as there are corresponding opening ones. It doesn't
care if they were already there, just
https://bugs.kde.org/show_bug.cgi?id=370716
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
---
12 matches
Mail list logo