https://bugs.kde.org/show_bug.cgi?id=488624
JATothrim changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=488624
--- Comment #8 from JATothrim ---
> Have a patch attempt in master.. That may help with the this. If so it can be
> back ported to stable.
Tested, the fix works! :)
However, mentioned in https://invent.kde.org/sdk/kdiff3/-/merge_requests/6
https://bugs.kde.org/show_bug.cgi?id=492852
JATothrim changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=492852
Bug ID: 492852
Summary: Corrupt output file encoding since commit
19ca36b7fa135e5db107d63fe22197519be30441
Classification: Applications
Product: kdiff3
Version: 1.11.3
Platfor
https://bugs.kde.org/show_bug.cgi?id=488624
--- Comment #6 from JATothrim ---
> Going the address this directly sorry for the delay unfortunately I find
> myself as the only one doing work with this code. My attention has been else
> where lately. In particular dealing with the odd
https://bugs.kde.org/show_bug.cgi?id=488624
JATothrim changed:
What|Removed |Added
Version|1.11.2 |unspecified
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=488624
JATothrim changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=488624
JATothrim changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #11 from JATothrim ---
I would like note that I'm using an "manual workaround" to avoid or at least
reduce the chance of crashing the IDE:
If the parser ever sees an partial #include with "" or <> brackets
https://bugs.kde.org/show_bug.cgi?id=488624
--- Comment #2 from JATothrim ---
I built kdiff3 in debug mode to able to step through the code in GDB, and
diff.h:getLineData() has ran itself into an corner: it has to return a
reference to something. The passed in argument is "e_SrcSelector::A
https://bugs.kde.org/show_bug.cgi?id=488624
--- Comment #1 from JATothrim ---
Got updated to 1.11.2 and I'm still experiencing the same bug. Just to note,
this issue is slightly different from
https://bugs.kde.org/show_bug.cgi?id=489494 and
https://bugs.kde.org/show_bug.cgi?id=487338 in tha
https://bugs.kde.org/show_bug.cgi?id=488624
JATothrim changed:
What|Removed |Added
Version|1.11.1 |1.11.2
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=426866
--- Comment #13 from JATothrim ---
Thanks for the very nice bug report. :)
The kdev-python's debugger is unfortunately quite broken, due to the
in-band-communication not working well... So, until the debugger is
resurrected, don't e
https://bugs.kde.org/show_bug.cgi?id=488624
Bug ID: 488624
Summary: kdiff3 unusable due to crashing
Classification: Applications
Product: kdiff3
Version: 1.11.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=487378
JATothrim changed:
What|Removed |Added
CC||jarmo.tii...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=486967
--- Comment #2 from JATothrim ---
(In reply to Igor Kushnir from comment #1)
> Do you manually arange tabs in your preferred order? My tabs usually end up
> in quite a mess of an
> order, because I tend to go on document-opening spree by Ctrl
https://bugs.kde.org/show_bug.cgi?id=486967
Bug ID: 486967
Summary: Remember order of closed document tabs/views
Classification: Applications
Product: kdevelop
Version: unspecified
Platform: unspecified
OS: Unspecified
https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #2 from JATothrim ---
> I don't find anything like this backtrace in my local collection. Could be a
> libclang 17 regression (I am still at v16).
Well, good then that I opened a bug report for this. I have had KDevelop
crashi
https://bugs.kde.org/show_bug.cgi?id=486932
Bug ID: 486932
Summary: Background parser crash C++ source
Classification: Applications
Product: kdevelop
Version: git master
Platform: Arch Linux
OS: Linux
Status: RE
https://bugs.kde.org/show_bug.cgi?id=362485
JATothrim changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #5 from JATothrim ---
A
https://bugs.kde.org/show_bug.cgi?id=362485
JATothrim changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=363237
--- Comment #10 from JATothrim ---
I scratched my itch with this bug. I want it *gone*. :-)
I built the kdevelop in the LXC container last week:
I used the kdesrc-build tool to build and checkout the sources.
I checkout master branch at
https://bugs.kde.org/show_bug.cgi?id=363237
--- Comment #9 from JATothrim ---
Created attachment 161752
--> https://bugs.kde.org/attachment.cgi?id=161752&action=edit
patch 2/2
The RFC bug fix.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363237
--- Comment #8 from JATothrim ---
Created attachment 161751
--> https://bugs.kde.org/attachment.cgi?id=161751&action=edit
patch 1/2
Wire an new event handler in BreakpointModel.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=363237
--- Comment #6 from JATothrim ---
(In reply to Sven Brauch from comment #2)
> Hmm, can't reproduce the crash but yes, the display is definitely buggy, we
> need to look into that.
>
> But, how did you lose data? Crash recovery should
https://bugs.kde.org/show_bug.cgi?id=449793
JATothrim changed:
What|Removed |Added
CC||jarmo.tii...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=449793
Bug ID: 449793
Summary: switching project build type changes current launch
config
Product: kdevelop
Version: 5.7.211201
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=363237
JATothrim changed:
What|Removed |Added
CC||jarmo.tii...@gmail.com
--- Comment #1 from
28 matches
Mail list logo
