https://bugs.kde.org/show_bug.cgi?id=371741
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=371761
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=371645
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=371481
--- Comment #5 from Sven Brauch ---
Yes, if you had some example code which reproduces the issue, that'd be great.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371761
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=371645
--- Comment #3 from Sven Brauch ---
Are the projects available somewhere so I could load them and see if I can
reproduce the crash?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371809
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=371809
--- Comment #2 from Sven Brauch ---
Oh and -DCMAKE_BUILD_TYPE=RelWithDebInfo instead of Release, for better traces.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371801
--- Comment #2 from Sven Brauch ---
We have this implemented in the "multicursor" branch, but it needs polishing
and bugfixing before it can be merged. If you want to spend some time on
that... very welcome!
See https://phabricator.k
https://bugs.kde.org/show_bug.cgi?id=371933
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven
https://bugs.kde.org/show_bug.cgi?id=368855
--- Comment #7 from Sven Brauch ---
The time is spent in libclang, i.e. parsing. This behaviour seems perfectly
normal to me; files changed, they have to be reparsed, that takes a while. So,
not a bug ...?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=372032
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=372040
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #3 from Sven Brauch ---
Ah, sorry, I overlooked the samba part. I find the perf data hard to read ...
but it does seem to spend noticeable time in I/O. Maybe it would be interesting
to copy the project to local disk and see if it still
https://bugs.kde.org/show_bug.cgi?id=372035
Sven Brauch changed:
What|Removed |Added
Component|general |Language Support: PHP
CC
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #6 from Sven Brauch ---
Ok, so it really seems to be I/O. Thanks for the tests! Maybe it would be
useful after all to run kdevelop in gdb, interrupt it when it's hanging, and
get a backtrace. I guess that's the easiest way to fin
https://bugs.kde.org/show_bug.cgi?id=372040
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=371645
--- Comment #6 from Sven Brauch ---
Did we break that between 5.0.1 and 5.0.2 ...?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368855
--- Comment #9 from Sven Brauch ---
This could be the same issue like the one on the mailing list, i.e. parsing
sometimes being super slow under some unclear conditions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371645
--- Comment #11 from Sven Brauch ---
That is unrelated to the original issue and looks very much like a bug in
libclang. It should be reported (and fixed) there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372346
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Status
https://bugs.kde.org/show_bug.cgi?id=371481
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=372454
Sven Brauch changed:
What|Removed |Added
Target Milestone|--- |5.0.3
Product|kdevelop
https://bugs.kde.org/show_bug.cgi?id=372558
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=372558
--- Comment #3 from Sven Brauch ---
That doesn't seem right, if your .cache is empty, from my knowledge you
shouldn't get the "it crashed" dialog -- the flag for that is stored in the
cache. The project file contains no reference
https://bugs.kde.org/show_bug.cgi?id=372558
--- Comment #6 from Sven Brauch ---
Ah ok, that makes more sense. Thanks for the clarification.
Maybe there's an issue when you close a project which is currently being opened
or so. Maybe you can reproduce it?
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=372599
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Summary|code
https://bugs.kde.org/show_bug.cgi?id=372686
Sven Brauch changed:
What|Removed |Added
CC||alexander.se...@web.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=372693
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=372686
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven
https://bugs.kde.org/show_bug.cgi?id=372875
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Status
https://bugs.kde.org/show_bug.cgi?id=372905
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #5 from Sven
https://bugs.kde.org/show_bug.cgi?id=372875
--- Comment #3 from Sven Brauch ---
Certainly a debatable choice, I guess the simple answer is that a single use
always has a single range in KDevelop, and for this you'd need to associate two
ranges to one use, i.e. technical reasons.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=373093
Sven Brauch changed:
What|Removed |Added
Product|kdevelop|frameworks-ktexteditor
Assignee
https://bugs.kde.org/show_bug.cgi?id=373171
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=373171
Sven Brauch changed:
What|Removed |Added
Summary|Why is it so hard to get|KDevelop allows to create a
https://bugs.kde.org/show_bug.cgi?id=373171
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=465688
Bug ID: 465688
Summary: "Fit" on scaled wayland display doesn't fit
Classification: Applications
Product: gwenview
Version: 22.12.2
Platform: Other
OS: Linux
Status: R
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #2 from Sven Brauch ---
Hi, QWidget has a devicePixelRatioF which contains this 1.25 IIRC:
https://doc.qt.io/qt-6/qpaintdevice.html#devicePixelRatioF -- I think that's
what you need?
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #3 from Sven Brauch ---
By the way, on my screen on Wayland, 125% wouldn't fit either. I need to set
~160%, which I can't make sense of. The only calculation I can come up with
which gives 1.6 would be 1.2 * 1/0.75, but it req
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #5 from Sven Brauch ---
You need devicePixelRatioF for sure, devicePixelRatio is only for integer
scaling.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466253
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Resolution
https://bugs.kde.org/show_bug.cgi?id=466253
--- Comment #3 from Sven Brauch ---
You need to trigger a build once (just once ever) so your build system
generates the files in the beginning, it will only work after that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #6 from Sven Brauch ---
Ok, the situation here seems to be that Wayland only supports integer scaling
at the moment. My 125% scaling is rounded up to 2, which is what is used by
Gwenview to scale the image, which makes it 2 / 1.25 = 1.6
https://bugs.kde.org/show_bug.cgi?id=465688
Sven Brauch changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #7 from Sven Brauch ---
To clarify again, I think there is no problem in Gwenview, its code already
accounts for display scaling in abstractimageview.cpp. It just gets the wrong
scale from Qt.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #9 from Sven Brauch ---
Hi, I tried this and I think Jorge did too, and both of us get "2.0" from
QApplication::devicePixelRatio() with 125% scaling configured in
systemsettings. I also tried in Qt6, and I *still* get "2.0&q
https://bugs.kde.org/show_bug.cgi?id=427147
--- Comment #8 from Sven Brauch ---
@anonymous11oneele...@gmail.com, please take your issue to a different report
-- it is not the same issue, and 80% of issues are with the background parser,
they can not all be tracked in the same repot. Thanks
https://bugs.kde.org/show_bug.cgi?id=427147
Sven Brauch changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=465688
--- Comment #11 from Sven Brauch ---
FWIW I would provide a patch for this if I could, but I think it's not possible
right now.
Gwenview wants to 1:1 map image pixels to screen pixels for zoom = 100%.
It cannot do that if it gets a surface fro
https://bugs.kde.org/show_bug.cgi?id=466975
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #5 from Sven
https://bugs.kde.org/show_bug.cgi?id=467710
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=459055
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Component|general
https://bugs.kde.org/show_bug.cgi?id=470963
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=460769
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=460769
Sven Brauch changed:
What|Removed |Added
Product|kdevelop|frameworks-ktexteditor
Version
https://bugs.kde.org/show_bug.cgi?id=464034
Sven Brauch changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=414531
Sven Brauch changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=463338
Sven Brauch changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #13 from Sven Brauch ---
Hi, I backported Python 3.11 support to 22.12, so it should be in 22.12.1.
I also fixed the original crash which caused this issue. That fix is on master
and will be in KDE Gear 23.04 (together with the feature it
https://bugs.kde.org/show_bug.cgi?id=443167
--- Comment #4 from Sven Brauch ---
Python 3.10 and 3.11 are supported now, FYI.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463802
--- Comment #14 from Sven Brauch ---
Sorry -- the backporting happened to 22.12.2, not .1 of course.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=464747
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #5 from Sven
https://bugs.kde.org/show_bug.cgi?id=464987
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #3 from Sven
https://bugs.kde.org/show_bug.cgi?id=426866
Sven Brauch changed:
What|Removed |Added
CC||jarmo.tii...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=426866
--- Comment #11 from Sven Brauch ---
Hi, thanks for this very detailed report. I've added the developer who has
recently been working on the debugger to the CC list of this bug, maybe he
knows something about this.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=486656
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven
https://bugs.kde.org/show_bug.cgi?id=486656
--- Comment #5 from Sven Brauch ---
Selection clipboard also works on Wayland, I tried it here. You are right, that
works even without this code for the navigation popup, I wasn't aware.
I would much prefer removing the feature completely over a
https://bugs.kde.org/show_bug.cgi?id=445565
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven
https://bugs.kde.org/show_bug.cgi?id=379506
Sven Brauch changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=444883
Sven Brauch changed:
What|Removed |Added
CC||mattia.basag...@gmail.com
--- Comment #26 from
https://bugs.kde.org/show_bug.cgi?id=446423
Sven Brauch changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=446464
Sven Brauch changed:
What|Removed |Added
Version|5.6.2 |5.88.0
Severity|minor
https://bugs.kde.org/show_bug.cgi?id=451041
Sven Brauch changed:
What|Removed |Added
Component|general |general
Assignee|kdevelop-bugs-n
https://bugs.kde.org/show_bug.cgi?id=447740
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven
https://bugs.kde.org/show_bug.cgi?id=447740
--- Comment #4 from Sven Brauch ---
The other bug https://bugs.kde.org/show_bug.cgi?id=451041 says X11...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455855
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=457974
Sven Brauch changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=457974
--- Comment #3 from Sven Brauch ---
Hi, unfortunately KDevelop is relatively short-staffed and simply nobody built
an AppImage for the latest release. It would of course be possible to do that,
though.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=442027
Sven Brauch changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=442029
Sven Brauch changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC
https://bugs.kde.org/show_bug.cgi?id=438206
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #7 from Sven
https://bugs.kde.org/show_bug.cgi?id=438206
--- Comment #8 from Sven Brauch ---
>From an end-user perspective, you can use the KDevelop AppImage from our
website, which we can build against Python 3.9 until this issue is resolved
somehow. It will of course not support Python 3.10 syntax, so
https://bugs.kde.org/show_bug.cgi?id=438206
--- Comment #12 from Sven Brauch ---
Any help is certainly very welcome. I am not very active on IRC currently, but
I definitely read and answer kdevelop-de...@kde.org.
In principle, the task is simple: in parser/ast.h we have our own data
structure
https://bugs.kde.org/show_bug.cgi?id=438206
--- Comment #13 from Sven Brauch ---
Hi, I've drafted a possible way forward in the "python310" branch in the
kdev-python repo. The AST is written to an XML stream from a tiny Python
program and read using QXmlStreamReader in C++. So f
https://bugs.kde.org/show_bug.cgi?id=438206
--- Comment #14 from Sven Brauch ---
Let's move any discussion on this topic to
https://invent.kde.org/kdevelop/kdev-python/-/merge_requests/16.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=84
Sven Brauch changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=444647
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #2 from Sven
https://bugs.kde.org/show_bug.cgi?id=444883
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Product|kdevelop
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #4 from Sven Brauch ---
Hi Waqar,
thanks for having a look at this. The problem is not (only) that it is slow in
KDevelop, the problem is also that it now misbehaves. Try it out with a
somewhat large project; the re-querying will somehow
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #6 from Sven Brauch ---
Hi, sorry, I didn't want to play a blame game, I am thankful for Waqar's work
on this topic and I do feel somewhat responsible for the issue at hand because
I know I should have taken the time to test tho
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #12 from Sven Brauch ---
You can try in KDevelop, it's really easy to reproduce there. Just start typing
something that will open a completion (e.g. member completion on anything), and
keep adding characters. At some point it will fl
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #14 from Sven Brauch ---
That might make sense, yes. I don't think any of the KDevelop sources profit
from getting a larger part of the current word; they are designed to just
provide all possible items and then filter.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #16 from Sven Brauch ---
@milian: There are more results because the filter gets cleared, it just shows
all, not just matching after the bug triggers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #18 from Sven Brauch ---
Ah. I didn't understand that either, but trusted the people who had used it
with the LSP stuff to have a valid reason for this behaviour.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #20 from Sven Brauch ---
Why is this happening, though? Do the LSP servers cut off the completion list
after N items because it gets too long (performance-wise) otherwise?
But yes, this seems to be the obvious difference to the KDevelop
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #22 from Sven Brauch ---
I mean, in the KDevelop case, there's nothing better to be done. It won't
profit from re-computing the list after typing a few characters, it has no
useful additional information over what it had in the
https://bugs.kde.org/show_bug.cgi?id=444883
--- Comment #24 from Sven Brauch ---
That sounds pragmatic. Thank you very much!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443315
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426561
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #3 from Sven
1 - 100 of 872 matches
Mail list logo
