https://bugs.kde.org/show_bug.cgi?id=369573
Sven Brauch changed:
What|Removed |Added
Summary|kdevelop consumes all |kdevelop consumes all
|availabl
https://bugs.kde.org/show_bug.cgi?id=369573
--- Comment #4 from Sven Brauch ---
I removed the "larger" from the title; whatever the problem is, it is not that
the file is so large, that file is only ~1000 lines, which is very small.
Unfortunately I cannot reproduce your crash, what do you edit e
https://bugs.kde.org/show_bug.cgi?id=370461
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=363269
--- Comment #21 from Sven Brauch ---
Git commit 77b83054f943b6c9bce0da178732f7992f7ada3b by Sven Brauch.
Committed on 13/10/2016 at 18:52.
Pushed by brauch into branch '5.0'.
Remove mime type <-> extension cache
The idea that because one file with ext
https://bugs.kde.org/show_bug.cgi?id=363269
--- Comment #22 from Sven Brauch ---
Note that while above commit should fix the crash in this case, this bug is
still open, since it would be back if you would rename the file to
"CMakeLists.txt" ... I think.
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=370715
Sven Brauch changed:
What|Removed |Added
Version|5.0.1 |Git
Component|code completion
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #3 from Sven Brauch ---
Yes, C style. What do you mean by "doesn't indent class methods properly"?
The C style indenter is the normal indenter for C/C++. The C++/boost style
indenter is some really specific tool with lots of assumptions on
https://bugs.kde.org/show_bug.cgi?id=49719
Sven Brauch changed:
What|Removed |Added
CC||kf...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=370716
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #5 from Sven Brauch ---
I think this should be fixed in the C-style indenter.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370716
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=370836
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
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.
Maybe we can insert
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 does that mean? Within
https://bugs.kde.org/show_bug.cgi?id=369326
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=370836
--- Comment #2 from Sven Brauch ---
Git commit 35477927f7dba97fd178ac662c88af725521e3ce by Sven Brauch.
Committed on 15/10/2016 at 11:03.
Pushed by brauch into branch '5.0'.
CMake manager: correcly document dependency on KDevCMakeBuilder plugin in JSON
https://bugs.kde.org/show_bug.cgi?id=369326
Sven Brauch changed:
What|Removed |Added
Version Fixed In||5.0.2
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=369326
--- Comment #11 from Sven Brauch ---
Git commit fb0230e3b6f08303ae92b1912268733d73348061 by Sven Brauch.
Committed on 15/10/2016 at 11:17.
Pushed by brauch into branch 'master'.
more helpful error message when failing to load project plugin
M +2-
https://bugs.kde.org/show_bug.cgi?id=49719
--- Comment #6 from Sven Brauch ---
No, that is making the exact same mistake again: you use an icon with an
unrelated semantic name just because it looks ok in the theme you assume.
"sharpen image" might be something completely unsuitable in a different
https://bugs.kde.org/show_bug.cgi?id=370715
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=369182
Sven Brauch changed:
What|Removed |Added
CC||fab...@web2.0-apps.de
--- Comment #7 from Sven Br
https://bugs.kde.org/show_bug.cgi?id=369573
Sven Brauch changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369631
Sven Brauch changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369326
Sven Brauch changed:
What|Removed |Added
CC||0xd34df...@gmail.com
--- Comment #12 from Sven Br
https://bugs.kde.org/show_bug.cgi?id=368826
Sven Brauch changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368826
--- Comment #3 from Sven Brauch ---
I think bug 331227 is a different issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368420
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=370641
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #4 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=368420
--- Comment #6 from Sven Brauch ---
Sorry, I'm still confused about this. Your traces all show a crash on shutdown,
which is not what you describe. Maybe let's clear that up again first -- you do
see a crash as an effect of triggering an action, right?
https://bugs.kde.org/show_bug.cgi?id=370641
--- Comment #6 from Sven Brauch ---
The cast shouldn't fail. The code obviously excepts that only objects that can
be cast into a ClangProblem are in the vector. The dynamic_cast is only there
to make it easier to debug if it fails.
Your fix is wrong b
https://bugs.kde.org/show_bug.cgi?id=49719
--- Comment #7 from Sven Brauch ---
Git commit 3e4c15c9c88a4bd6c5458718cb917882da9b097f by Sven Brauch.
Committed on 16/10/2016 at 10:36.
Pushed by brauch into branch '5.0'.
Do not use "script-error" icon for breakpoints
It just doesn't look right for
https://bugs.kde.org/show_bug.cgi?id=370641
Sven Brauch changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kdev
|
https://bugs.kde.org/show_bug.cgi?id=370641
--- Comment #13 from Sven Brauch ---
Yes, that looks like a solution to the problem. Thanks for the patch!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370641
Sven Brauch changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
|pl
https://bugs.kde.org/show_bug.cgi?id=356572
Sven Brauch changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=49719
--- Comment #9 from Sven Brauch ---
Ok, sorry, I misunderstood that you wanted to copy those icons instead of just
using them.
I'm still in favor of using the red dot instead of some concentric circles or
triangles; all IDEs in the world have been using
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #15 from Sven Brauch ---
Thanks a lot for looking into that! Could you maybe be so kind and put a patch
up on phabricator.kde.org? Ideally, you could add a test for the new behaviour
:)
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=371012
Bug ID: 371012
Summary: "There is no disk in drive D:\" dialog when starting
KDevelop on some systems
Product: frameworks-solid
Version: 5.27.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=371013
Bug ID: 371013
Summary: some code not highlighted properly
Product: kdevelop
Version: 5.0.2
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=371018
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
CC|
https://bugs.kde.org/show_bug.cgi?id=371009
Sven Brauch changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kdev
|
https://bugs.kde.org/show_bug.cgi?id=371009
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=371018
--- Comment #5 from Sven Brauch ---
That's exactly the point, by delaying the parser a bit longer we get less cases
where completion has to wait for it.
The background parser needs to run automatically after every change, that is
not debatable. We cann
https://bugs.kde.org/show_bug.cgi?id=371018
--- Comment #7 from Sven Brauch ---
Most of the delay you see is a delay, not the parser being slow. The point is
that, right now, as soon as the parser starts you need to wait for it to finish
before you can generate a completion list. Thus the delay,
https://bugs.kde.org/show_bug.cgi?id=371008
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=363044
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=371008
--- Comment #3 from Sven Brauch ---
Hmm, debug info would be useful for this one, inferArgumentsFromCall() is a
relatively long and complex function so it's not clear from this trace what
actually happens. If you like, try installing kdevelop from AUR i
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #10 from Sven Brauch ---
Well, you can apply the 4 patches listed above, then it works. Regarding
upstreaming them, I have no clue, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #20 from Sven Brauch ---
Patch looks sensible to me and even has tests, if there are no objections I
would simply apply it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #22 from Sven Brauch ---
Feel free to just adjust that test to the new behaviour, if you consider the
new behaviour sensible.
To enable autobraces, try view->config()->setAutoBrackets(true).
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=371018
--- Comment #10 from Sven Brauch ---
When you change the code, a background process is started with a certain delay,
which updates the code model (highlighting, ...).
_While_ this process is running, the clang-based cpp support cannot generate
completio
https://bugs.kde.org/show_bug.cgi?id=371235
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Component|general
https://bugs.kde.org/show_bug.cgi?id=371018
--- Comment #13 from Sven Brauch ---
Yes, setting the delay to a longer value doesn't update the highlighting faster
-- on the contrary, it delays it even more ;)
We should probably remove the user-defined delay altogether. I don't see what
it's good f
https://bugs.kde.org/show_bug.cgi?id=350785
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #5 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=350785
--- Comment #6 from Sven Brauch ---
Neverthereless, KDE code should handle this fault condition more gracefully.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364988
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=353404
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=353404
--- Comment #4 from Sven Brauch ---
There's an implied "I won't do it right now because I have other things to do
but I agree that somebody should do it, though I see it coming that this
problem will be there again in six months unless it gets automated
https://bugs.kde.org/show_bug.cgi?id=354082
--- Comment #16 from Sven Brauch ---
If that indeed improves things, you should definitely submit it to Qt. Here is
not a good place for it :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364433
--- Comment #8 from Sven Brauch ---
Git commit f74ec1e6ec16c7e58d34d7fae05867292370b00d by Sven Brauch.
Committed on 09/07/2016 at 12:31.
Pushed by brauch into branch '5.0'.
Fix crash on closing the "missing include" wizard
M +16 -9duchain/assi
https://bugs.kde.org/show_bug.cgi?id=364433
Sven Brauch changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kdev
|
https://bugs.kde.org/show_bug.cgi?id=364433
Sven Brauch changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
|pl
https://bugs.kde.org/show_bug.cgi?id=364433
--- Comment #11 from Sven Brauch ---
This should do. I do however still not understand why the but originally
happened ... valgrind doesn't tell me much either :/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364433
Sven Brauch changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
|el
https://bugs.kde.org/show_bug.cgi?id=354082
--- Comment #21 from Sven Brauch ---
Cool, many thanks for investigating this! Your fix looks sensible to me (if the
glyph height is zero there is nothing to do), but I'm not really qualified to
review it. Did you submit it to the Qt code review system?
https://bugs.kde.org/show_bug.cgi?id=364433
--- Comment #14 from Sven Brauch ---
Couldn't reproduce it any more at least, let me know if you observe something
else. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364650
Sven Brauch changed:
What|Removed |Added
Component|all editors |Vi Input Mode
Assignee|kdevelop-bugs-n.
https://bugs.kde.org/show_bug.cgi?id=364650
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=364650
--- Comment #3 from Sven Brauch ---
No fancy keyboard layouts necessary here btw, this is a german keyboard with
the standard de-latin1-nodeadkeys layout.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365633
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=358521
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=358311
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #6 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=365633
Sven Brauch changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=365634
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=358311
--- Comment #7 from Sven Brauch ---
To be more correct, I have not _seen_ this happening in other languages. It is
some kind of race condition; it is possible it exists in the other languages as
well, but only triggers that often for clang because its p
https://bugs.kde.org/show_bug.cgi?id=365634
--- Comment #2 from Sven Brauch ---
Ok, I do see it after all, maybe I'm just blind. I'll find a way to fix it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365634
Sven Brauch changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=365635
Bug 365635 depends on bug 365634, which changed state.
Bug 365634 Summary: signature assistant asserts since assistant-ng merge
https://bugs.kde.org/show_bug.cgi?id=365634
What|Removed |Added
--
https://bugs.kde.org/show_bug.cgi?id=363752
Sven Brauch changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363752
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #3 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=365773
Sven Brauch changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kdev
|
https://bugs.kde.org/show_bug.cgi?id=358311
Sven Brauch changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=354082
--- Comment #22 from Sven Brauch ---
Can we maybe fix this in konsole instead? Its use of the API does seem strange
judging from what you describe.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361896
--- Comment #12 from Sven Brauch ---
Maybe somebody will look again at with the soon-to-come 5.0 release. Until
then, you can try the binaries: files.svenbrauch.de/kdevelop-linux/
And ping them again, of course.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=361896
--- Comment #14 from Sven Brauch ---
Eh, same issue. Can you paste your environment variables ("env")?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361896
--- Comment #16 from Sven Brauch ---
Mh. Anything interesting in your /etc/pythonstartup?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361896
--- Comment #18 from Sven Brauch ---
Looks harmless. I'm kind of clueless what about your setup triggers this issue,
sorry :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359496
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #3 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=340841
--- Comment #29 from Sven Brauch ---
Can you give some details please? What version of kdev-python is this? Python 2
or Python 3? What file(s) did it crash on? Why do you think that trace is this
bug? Thanks.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=340841
--- Comment #31 from Sven Brauch ---
Ah, ok. Is this using the Python 2 or Python 3 version of the plugin?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=354082
--- Comment #25 from Sven Brauch ---
Can you link to the upstream change which fixed this issue?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368970
--- Comment #3 from Sven Brauch ---
Hmm, is that package written in Python?
Does pressing F5 change anything? Maybe the project wasn't reparsed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368970
--- Comment #5 from Sven Brauch ---
Hm, in the sample code I can't even find "import arcade" ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368970
--- Comment #7 from Sven Brauch ---
Ok, works perfectly fine here with arcade installed system-wide, so the problem
is with paths somehow.
Can you export QT_LOGGING_RULES=kdev.python.duchain.debug=true and watch for
the "search paths" line which prints
https://bugs.kde.org/show_bug.cgi?id=368970
--- Comment #9 from Sven Brauch ---
That shouldn't be a problem ... i'll have to try that out. Maybe there is a
problem with the scheduling for those extra paths, although I have no idea why
that would be.
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=361958
Sven Brauch changed:
What|Removed |Added
Component|CTags |Language Support: CPP
|
https://bugs.kde.org/show_bug.cgi?id=369536
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=369454
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=369403
Sven Brauch changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=369369
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
1 - 100 of 270 matches
Mail list logo
