[kdevelop] [Bug 371641] KDevelop Icon style can not be customized.

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371641

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||m...@svenbrauch.de
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sven Brauch  ---
The AppImage ships a fixed icon set and theme and this is unlikely to change
because of the implications on file size and complexity of having it changable.

Your distribution packages, which you should prefer if available, use the
platform theme's icons, colors and style, as they always did.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 338376] Reformat source has no default shortcut

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=338376

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID
 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
Closing as invalid, you can assign a shortcut and not everything needs a
default shortcut.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368970

Sven Brauch  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||-python/82729e275d176a81101
   ||da98f9af4fd8a465f73c2
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Sven Brauch  ---
Git commit 82729e275d176a81101da98f9af4fd8a465f73c2 by Sven Brauch.
Committed on 23/10/2016 at 11:25.
Pushed by brauch into branch 'master'.

Allow configuring a per-project Python interpreter for search paths.

This introduces rudimentary support for virtualenv, since you can now
set the virtualenv's "python" as the project's interpreter.

M  +2-1CMakeLists.txt
M  +1-1codecompletion/context.cpp
M  +2-2duchain/contextbuilder.cpp
M  +29   -13   duchain/helpers.cpp
M  +4-4duchain/helpers.h
A  +52   -0projectconfig/projectconfig.ui
A  +43   -0projectconfig/projectconfigpage.cpp [License: UNKNOWN]  *
A  +45   -0projectconfig/projectconfigpage.h [License: GPL (v2+)]
M  +15   -1pythonlanguagesupport.cpp
M  +3-0pythonlanguagesupport.h
M  +1-1pythonparsejob.h

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/kdev-python/82729e275d176a81101da98f9af4fd8a465f73c2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371481] kdevelop segfaults while typing

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371481

--- Comment #3 from Sven Brauch  ---
Can you make sure you have kdev-php version 5.0.1, not 5.0.0? We fixed a
similar bug in between. You can also try with the pre-built kdevelop from
kdevelop.org/download.

I can't reproduce the issue on 5.0.2. :/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371481] kdevelop segfaults while typing

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371481

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Ok, looks like a bug in the PHP plugin. Can you paste the code you typed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[Sven Brauch via KDE Bugzilla]

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 for.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 371235] vi-mode: ":tabe anything" crashed KDevelop

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371235

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de
  Component|general |Vi Input Mode
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
Product|kdevelop|kate
Version|5.0.2   |16.08

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[Sven Brauch via KDE Bugzilla]

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
completion lists, it has to wait. Before it is started and after it is finished
all is fine. This is an unfortunate limitation of libclang, the old kdevelop
cpp parser didn't have that. Thus, we added this "long" delay as a workaround,
and thus it doesn't help to scale this delay with CPU speed either. I know this
is unfortunate, but I'm not capable of improving the situation in
clang/libclang, and I don't have the time to work into that either. Maybe
Milian has an idea.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

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 watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

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.

[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 371008] KDevelop crashes when reloading file

[Sven Brauch via KDE Bugzilla]

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 in
RelWithDebInfo mode (if you actually want to use it, I recommend not building
in Debug, it's noticeably more sluggish).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 363044] Crash when parsing javascript/python files [DeclarationBuilder::inferArgumentsFromCall]

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363044

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||m...@svenbrauch.de

--- Comment #5 from Sven Brauch  ---
Closing this as fixed since you say it doesn't happen any more in 4.7.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371008] KDevelop crashes when reloading file

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371008

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de
 Status|RESOLVED|UNCONFIRMED
 Resolution|DUPLICATE   |---

--- Comment #2 from Sven Brauch  ---
I don't think this is a duplicate, just because it crashes in the same
function. The circumstances are different (reloading file, ...) and the other
bug was confirmed fixed in 4.7.3 by the reporter, while this is still present
in 5.0. I'll reopen this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[Sven Brauch via KDE Bugzilla]

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, and thus changing
the delay based on processor speed doesn't help -- it's meant to match your
typing speed, not the processor.

The parser is slow because parsing C++ correctly is complicated.

This issue has nothing to do with the size of whatever cache you're thinking
about.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[Sven Brauch via KDE Bugzilla]

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 cannot even update highlighting properly without doing that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371009] 5.0.2 breakpoints no longer visible in icon border

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371009

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Issue in the AppImage, I created an updated image and it will replace the old
one on the KDE servers soon-ish.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371009] 5.0.2 breakpoints no longer visible in icon border

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371009

Sven Brauch  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/63822e268096c906f6e8a2
   ||8da3ee3a5675099f95

--- Comment #2 from Sven Brauch  ---
Git commit 63822e268096c906f6e8a28da3ee3a5675099f95 by Sven Brauch.
Committed on 17/10/2016 at 19:51.
Pushed by brauch into branch '5.0'.

appimage: only remove breeze icons, not our only ones

M  +2-1appimage/kdevelop-recipe-centos6.sh

http://commits.kde.org/kdevelop/63822e268096c906f6e8a28da3ee3a5675099f95

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371018

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||m...@svenbrauch.de
 Ever confirmed|0   |1

--- Comment #1 from Sven Brauch  ---
The problem is that while the background parser is running for kdev-clang,
generating completion items is very slow ... so we explicitly added a longer
delay for some edits, such that the update doesn't overlap with the user
requesting completion.

I see your point though, and I'm still not sure what to do about it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 371013] New: some code not highlighted properly

[Sven Brauch via KDE Bugzilla]

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
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@svenbrauch.de
CC: kf...@kde.org, m...@milianw.de

Some of the below code is not being highlighted at all by kdev-clang:

#ifndef FIXPOINT_HPP
#define FIXPOINT_HPP

#include 
#include 
#include 
#include 

template  struct SIntegerBySize {};
template <> struct SIntegerBySize<1> { using stype = int8_t;using utype
= uint8_t; };
template <> struct SIntegerBySize<2> { using stype = int16_t; using
utype = uint16_t; };
template <> struct SIntegerBySize<4> { using stype = int32_t; using
utype = uint32_t; };
template <> struct SIntegerBySize<8> { using stype = int64_t; using
utype = uint64_t; };
#if defined(__SIZEOF_INT128__)
template <> struct SIntegerBySize<16>{ using stype = __int128; using
utype = unsigned __int128; };
template <> struct SIntegerBySize<32>{ using stype = __int128; using
utype = unsigned __int128; };
#else
template <> struct SIntegerBySize<16>{ using stype = int64_t; using
utype = uint64_t; };
#endif

template  struct SDoubleWidth
{
using type = typename std::conditional::stype,
typename
SIntegerBySize::utype >::type;
};

template  struct SBiggerType
{ using type = typename std::conditional<(sizeof(T1)>sizeof(T2)) , T1,
T2>::type; };

template struct static_min{ static constexpr int value = X < Y ?
X : Y; };
template struct static_max{ static constexpr int value = X >= Y ?
X : Y; };
template struct static_clamp{ static constexpr int
value = static_max::value, min>::value; };
template struct staitc_abs{ static constexpr int value = X < 0 ? -X : X;
};
template struct static_shift{ static constexpr int value =
static_clamp::value; };


template struct Fixpoint;
template  struct
ArbitraryMUL;
template  struct
ArbitraryDIV;

template ResultType ShrinkType(const T& t)
{
if (sizeof(T) > sizeof(ResultType))
{
constexpr int DestTypeSize = static_min::value;
//constexpr int DiscardedBits = (sizeof(T) - sizeof(ResultType))*8;
const bool __attribute__((unused)) OverflowCheck = (t >> DestTypeSize)
== 0;
assert(OverflowCheck);

if (std::is_signed::value && std::is_signed::value)
{
const bool InputIsNegative = t < 0;
const bool CastedVersionIsNegative = ResultType(t) < 0;
const bool __attribute__((unused)) SignHasChangedDueToOverflow =
InputIsNegative == CastedVersionIsNegative;
assert(SignHasChangedDueToOverflow);
}
}
return ResultType(t);
}

enum FixpointOperationAggregate{foaArbitraryADD, foaArbitraryMUL,
foaArbitraryDIV};

template  struct
ArbitraryADD
{
ArbitraryADD(const lhs_T& _lhs, const rhs_T& _rhs): lhs(_lhs), rhs(_rhs) {}
using type = ArbitraryADD;
static constexpr int lhs_prec = lhs_FP;
static constexpr FixpointOperationAggregate Operation = foaArbitraryADD;
using lhs_type = lhs_T;
template constexpr operator Fixpoint() const
{
if (ret_FP <= static_min::value)  // return precision
is the lowest
{
//Convert everything down to ret_FP, then add to allow overflow
constexpr int minprec = static_min::value;
const lhs_T lhs_shifted = lhs >> staitc_abs::value;
const rhs_T rhs_shifted = rhs >> staitc_abs::value;
return Fixpoint::ConstructRaw( (lhs_shifted +
rhs_shifted) >> staitc_abs::value);
}
else if (ret_FP > static_max::value) // return
precision is the highest
{
//use the highest precision of lhs and rhs available,
constexpr int max_lhs_rhs = static_max::value;

const lhs_T lhs_shifted = lhs_FP < max_lhs_rhs ? lhs <<
staitc_abs::value : lhs;
const rhs_T rhs_shifted = rhs_FP < max_lhs_rhs ? rhs <<
static_clamp::value : rhs;
return Fixpoint::ConstructRaw((lhs_shifted +
rhs_shifted) << staitc_abs::value);
} else if ( (rhs_FP >= ret_FP) && (ret_FP >= lhs_FP) )
{
const rhs_T rhs_shifted = rhs >> staitc_abs::value;
const lhs_T lhs_shifted = lhs << staitc_abs::value;
return Fixpoint::ConstructRaw(lhs_shifted +

[frameworks-solid] [Bug 371012] New: "There is no disk in drive D:\" dialog when starting KDevelop on some systems

[Sven Brauch via KDE Bugzilla]

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: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: m...@svenbrauch.de
CC: kdelibs-b...@kde.org, kf...@kde.org

When starting KDevelop on Windows on some systems, we get several "There is no
disk in drive D:\" dialogs. This seems to come from Solid's free space info
code, here's a trace (no detailed debug symbols, sorry):

Thread 1 (Thread 5316.0x1034):
#0  0x7ffa873209ea in ntdll!ZwOpenFile () from
C:\Windows\SYSTEM32\ntdll.dll
#1  0x7ffa84864246 in KERNELBASE!GetDiskFreeSpaceExW () from
C:\Windows\system32\KernelBase.dll
#2  0x7ffa69e83e9a in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#3  0x7ffa69e83a0e in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#4  0x7ffa69e7bbe3 in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#5  0x7ffa69e7a42c in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#6  0x7ffa69e7dee0 in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#7  0x7ffa69e51776 in
KF5Solid!?trUtf8@DeviceNotifier@Solid@@SA?AVQString@@PEBD0H@Z () from
C:\Program Files\KDevelop\bin\KF5Solid.dll
#8  0x7ffa6d917229 in
KF5KIOFileWidgets!?dir@KRecentDirs@@YA?AVQString@@AEBV2@@Z () from C:\Program
Files\KDevelop\bin\KF5KIOFileWidgets.dll
#9  0x6d38c38e in Qt5Core!?event@QObject@@UEAA_NPEAVQEvent@@@Z () from
C:\Program Files\KDevelop\bin\Qt5Core.dll
#10 0x6d6bc5a6 in
Qt5Widgets!?notify_helper@QApplicationPrivate@@QEAA_NPEAVQObject@@PEAVQEvent@@@Z
() from C:\Program Files\KDevelop\bin\Qt5Widgets.dll
#11 0x6d6bbba6 in
Qt5Widgets!?notify@QApplication@@UEAA_NPEAVQObject@@PEAVQEvent@@@Z () from
C:\Program Files\KDevelop\bin\Qt5Widgets.dll
#12 0x6d367609 in
Qt5Core!?notifyInternal2@QCoreApplication@@CA_NPEAVQObject@@PEAVQEvent@@@Z ()
from C:\Program Files\KDevelop\bin\Qt5Core.dll
#13 0x6d36834a in
Qt5Core!?sendPostedEvents@QCoreApplicationPrivate@@SAXPEAVQObject@@HPEAVQThreadData@@@Z
() from C:\Program Files\KDevelop\bin\Qt5Core.dll
#14 0x7ffa5e82546f in qwindows!qt_plugin_instance () from C:\Program
Files\KDevelop\bin\platforms\qwindows.dll
#15 0x6d3b47b6 in
Qt5Core!?activateEventNotifier@QEventDispatcherWin32Private@@QEAAXPEAVQWinEventNotifier@@@Z
() from C:\Program Files\KDevelop\bin\Qt5Core.dll
#16 0x7ffa86fd24fd in USER32!DispatchMessageW () from
C:\Windows\system32\user32.dll
#17 0x7ffa86fd2357 in USER32!NotifyWinEvent () from
C:\Windows\system32\user32.dll
#18 0x6d3b58de in
Qt5Core!?processEvents@QEventDispatcherWin32@@UEAA_NV?$QFlags@W4ProcessEventsFlag@QEventLoop@Z
() from C:\Program Files\KDevelop\bin\Qt5Core.dll
#19 0x7ffa5e825449 in qwindows!qt_plugin_instance () from C:\Program
Files\KDevelop\bin\platforms\qwindows.dll
#20 0x6d365020 in
Qt5Core!?exec@QEventLoop@@QEAAHV?$QFlags@W4ProcessEventsFlag@QEventLoop@Z
() from C:\Program Files\KDevelop\bin\Qt5Core.dll
#21 0x6d367c47 in Qt5Core!?exec@QCoreApplication@@SAHXZ () from
C:\Program Files\KDevelop\bin\Qt5Core.dll
#22 0x7ff6ce0ed64d in ?? ()

Any ideas what that could be?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

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 watching all bug changes.

[kdevelop] [Bug 49719] breakpoints are hard to see with dark themes, icon border should be enabled by default

[Sven Brauch via KDE Bugzilla]

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 a red dot for breakpoints in
the last twenty years, so we should not break that for no reason.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 356572] Crash when parsing the source code of LibreOffice

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356572

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |NEEDSINFO
 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
Setting this to NEEDSINFO, assuming it has been fixed in clang since. If not,
please re-open it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

[Sven Brauch via KDE Bugzilla]

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
   |platform/e4fb596442fe7cb1f5 |platform/8cdd0ade6755d76b6e
   |a96c377a08c0aee917b05c  |4400adf05411397258f3ab

--- Comment #14 from Sven Brauch  ---
Git commit 8cdd0ade6755d76b6e4400adf05411397258f3ab by Sven Brauch, on behalf
of René J.V. Bertin.
Committed on 16/10/2016 at 14:29.
Pushed by brauch into branch 'master'.

export IProblem

Otherwise, dynamic_casts away from that type fail on macOS, apparently.

M  +1-1interfaces/iproblem.h

http://commits.kde.org/kdevplatform/8cdd0ade6755d76b6e4400adf05411397258f3ab

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370641

Sven Brauch  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/e4fb596442fe7cb1f5
   ||a96c377a08c0aee917b05c
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #12 from Sven Brauch  ---
Git commit e4fb596442fe7cb1f5a96c377a08c0aee917b05c by Sven Brauch, on behalf
of René J.V. Bertin.
Committed on 16/10/2016 at 14:21.
Pushed by brauch into branch '5.0'.

export IProblem

Otherwise, dynamic_casts away from that type fail on macOS, apparently.

M  +1-1interfaces/iproblem.h

http://commits.kde.org/kdevplatform/e4fb596442fe7cb1f5a96c377a08c0aee917b05c

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 49719] breakpoints are hard to see with dark themes, icon border should be enabled by default

[Sven Brauch via KDE Bugzilla]

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 some themes, e.g. Breeze. Instead, we
ship our own icon, which looks like what people expect (red dot).

At this occasion, use 16x16 size for the icon border icon,
because the width of the icon border is fixed to that in kate.
Differential Revision: https://phabricator.kde.org/D3061

M  +4-4debugger/breakpoint/breakpointmodel.cpp
M  +1-1debugger/interfaces/ibreakpointcontroller.cpp
A  +---pics/16x16/actions/breakpoint.png
A  +---pics/22x22/actions/breakpoint.png
M  +2-5pics/CMakeLists.txt
A  +95   -0pics/scalable/breakpoint.svg
M  +1-1shell/debugcontroller.cpp

http://commits.kde.org/kdevplatform/3e4c15c9c88a4bd6c5458718cb917882da9b097f

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

[Sven Brauch via KDE Bugzilla]

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 because it works around the failing cast instead of finding
the reason for why it fails.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

[Sven Brauch via KDE Bugzilla]

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? Not just on shutdown?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370641

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #4 from Sven Brauch  ---
Your "possibly related" bug seems like a hint to the reason. Did you
investigate that? Maybe for Mac you need to export both types, or so? I could
imagine ClangProblem is not exported. Add a KDEVBLUBB_EXPORT macro and see if
that fixes it.

Your proposed fix looks wrong to me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368420

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
The trace you post here crashes from MainWindow::~MainWindow downwards, i.e. it
is a crash on shutdown. Do you have a trace for the crash you described, when
you click Run -> Execute launch?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368826] KDevelop crashed when trying to open a CMake project

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 368826] KDevelop crashed when trying to open a CMake project

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368826

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---


*** This bug has been marked as a duplicate of bug 369326 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Sven Brauch  changed:

   What|Removed |Added

 CC||0xd34df...@gmail.com

--- Comment #12 from Sven Brauch  ---
*** Bug 368826 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #12 from Sven Brauch  ---
Setting state to NEEDSINFO because I don't think we can fix it with this
information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369573

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Sven Brauch  ---


*** This bug has been marked as a duplicate of bug 369182 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369182] kdevelop crashes while parsing javascript files

[Sven Brauch via KDE Bugzilla]

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 Brauch  ---
*** Bug 369573 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370715

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #8 from Sven Brauch  ---
I think I know why this is: typing the closing brace triggers a deindent --
which makes sense, but is wrong in this case. Also this needs to be fixed in
the c style indenter.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 49719] breakpoints are hard to see with dark themes, icon border should be enabled by default

[Sven Brauch via KDE Bugzilla]

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 theme
(e.g. oxygen).

Either we get a dedicated icon called "breakpoint.svg" in breeze, or we ship
our own, which is what I suggest in https://phabricator.kde.org/D3061.

Regarding enabling the border by default, I sent a mail to kwrite-devel, I
don't think we can change default options right now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

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-1shell/project.cpp

http://commits.kde.org/kdevplatform/fb0230e3b6f08303ae92b1912268733d73348061

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

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:
You are watching all bug changes.

[kdevelop] [Bug 370836] Kdevelop crashes when creating project or opening file

[Sven Brauch via KDE Bugzilla]

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
file

There's an assert or a crash if the plugin is not available at runtime.
This happens if you disable the make and ninja plugins, or if they
cannot be loaded for some reason.
Related: bug 369326

M  +4-1projectmanagers/cmake/kdevcmakemanager.json

http://commits.kde.org/kdevelop/35477927f7dba97fd178ac662c88af725521e3ce

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/35477927f7dba97fd178ac
   ||662c88af725521e3ce

--- Comment #9 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
file

There's an assert or a crash if the plugin is not available at runtime.
This happens if you disable the make and ninja plugins, or if they
cannot be loaded for some reason.
Related: bug 370836

M  +4-1projectmanagers/cmake/kdevcmakemanager.json

http://commits.kde.org/kdevelop/35477927f7dba97fd178ac662c88af725521e3ce

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370716] Automatically overwrite closing brackets

[Sven Brauch via KDE Bugzilla]

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 the
same line? In the whole document? Do comments count? Do strings count?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370716] Automatically overwrite closing brackets

[Sven Brauch via KDE Bugzilla]

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 the () from KDevelop by simulating typing "(" if autobrace
is enabled. Then that would work here, too ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370836] Kdevelop crashes when creating project or opening file

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370836

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Trace looks familiar, can you check you have all of the "cmake", "make" and
"ninja" plugins enabled in the settings -> plugins dialog? If any is disabled,
can you please enable it and try again?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370716] Automatically overwrite closing brackets

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370716

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Sven Brauch  ---
Ok, that would solve your original request as well. I'll implement that and
talk it over with the kate devs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 370716] Automatically overwrite closing brackets

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370716

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
For kate's autobrace, this is already the case, under certain conditions.

For KDevelop's autobraces, hmm, I don't know how simple it is to do this
technically. Not so simple, I think.

I'm actually considering to rework how autobraces work in kate, i.e. just "eat"
closing parentheses iff the result of inserting a new character would lead to
there being more closing than opening parentheses in the current line. Would
that help?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 49719] breakpoints are hard to see with dark themes, icon border should be enabled by default

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=49719

Sven Brauch  changed:

   What|Removed |Added

 CC||kf...@kde.org,
   ||m...@svenbrauch.de
 Status|REOPENED|CONFIRMED

--- Comment #3 from Sven Brauch  ---
I agree with basically all you said.

Icon border and line numbers should be enabled by default. It's ok to not have
this for kate, since it is used by a lot of people to edit simple text, but for
KDevelop it should just be on.

The breeze icon we use for breakpoint is really bad and unsuitable, from the
aesthetic (imo) point of view but especially from the recognizability -- it
just doesn't fit. I'll look that we can get a dedicated "breakpoint" icon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

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 your code
style that generally (imo) do not apply.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370715

Sven Brauch  changed:

   What|Removed |Added

Version|5.0.1   |Git
  Component|code completion |indentation
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
 CC||m...@svenbrauch.de
Product|kdevelop|kate

--- Comment #1 from Sven Brauch  ---
Changing product to kate.

Yes, it's broken, but the C++/boost indenter is so super strange that I'm not
sure if it's worth fixing. Just use the normal C++ indenter instead.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 363269] Crash when projects contains *.txt file that is actually a binary file [cmListFileLexerSetToken]

[Sven Brauch via KDE Bugzilla]

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:
You are watching all bug changes.

[kdevelop] [Bug 363269] Crash when projects contains *.txt file that is actually a binary file [cmListFileLexerSetToken]

[Sven Brauch via KDE Bugzilla]

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 extension X has mime type A,
determined by its contents, hence other files with extension X will
have the same mime type is just wrong. One common example where this
breaks in a spectacular way is CMakeLists.txt and the .txt extension.

I found the claim that looking into each file will make the application
unresponsive to be unfounded. QMimeType will only read the first 16kB to
guess the mime type, which takes less than a millisecond for each file.
A test project with three hundred 3 MB binary blobs still loads instantly.
If, in comparison, we parse one of the files as CMake erraneously, we
take multiple seconds.
Differential Revision: https://phabricator.kde.org/D3042

M  +1-35   shell/languagecontroller.cpp

http://commits.kde.org/kdevplatform/77b83054f943b6c9bce0da178732f7992f7ada3b

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370461] Crash at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370461

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Crash in the old cpp plugin -- sorry, low priority, since that code is
completely gone in 5.x :/

Happens every time or just once?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file

[Sven Brauch via KDE Bugzilla]

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 exactly?

Also, what language is this? It's not plain JavaScript, and KDevelop's JS
parser immediately chokes on it ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369573

Sven Brauch  changed:

   What|Removed |Added

Summary|kdevelop consumes all   |kdevelop consumes all
   |available memory when   |available memory when
   |editing larger js file  |editing js file
 CC||m...@svenbrauch.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 369883] Ctrl-f only works first time to select text for Find

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369883

Sven Brauch  changed:

   What|Removed |Added

Product|kdevelop|kate
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
 CC||m...@svenbrauch.de
Version|5.0.1   |16.08
  Component|all editors |part

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 369363] Type not inferred when iterating objects with __next__

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369363

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Sven Brauch  ---
Valid issue but probably hard to fix given how it's implemented currently. :/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

--- Comment #11 from Sven Brauch  ---
Ah, in that case try
export QT_LOGGING_RULES="kdevelop.plugins.clang.debug=true"
then you should see processed files.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

--- Comment #9 from Sven Brauch  ---
Or go up in the stack with the debugger and print it, e.g. the top context is
available almost everywhere and it has a url().

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

--- Comment #6 from Sven Brauch  ---
Maybe you can figure out what file it crashes on and give us the part of it
that triggers the crash? That'd help a lot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

--- Comment #4 from Sven Brauch  ---
To me this crash looks quite different from the first one you posted. That
could be a bug. Is the project which you are working on public?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369631] KDevelop crashed at startup

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369631

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Can you rm -Rf ~/.cache/kdevduchain and try again? Looks like corrupted cache.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369105

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #4 from Sven Brauch  ---
Hmm. Thanks for the information. I really can't see what could be wrong from
our side :/
I think I'll let this rest unless at least one or two other users can reproduce
the same problem, I think the risk of wasting time hunting a bug on our side
which isn't one is too high here. Sorry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #8 from Sven Brauch  ---
For most plugins, KDevelop does lazy-loading anyways (i.e. only loads the
plugin when needed) even if they are enabled. So there is little to no reason
to ever disable a plugin, except e.g. if it crashes.

Which means that, in my opinion, we should consider removing the option for the
relevant plugins. Disabling a language might make sense, but why would anyone
want to disable the Projects toolview plugin, VCS plugins, or project managers?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 363269] Crash when projects contains *.txt file that is actually a binary file [cmListFileLexerSetToken]

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363269

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #20 from Sven Brauch  ---
Thanks for looking. You are indeed right -- .txt files are treated as cmake in
some cases. I also poked around a bit, when it does not find a language for a
file it looks at the contents, guesses the mime type, and caches that. So when
you open CMakeLists.txt, after that all .txt files will be treated as CMake.
That is a bug, and needs to be fixed. The relevant code is, I think, in
languagecontroller.cpp:310ff.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Sven Brauch  changed:

   What|Removed |Added

 CC||kf...@kde.org

--- Comment #6 from Sven Brauch  ---
But why?

@Kevin: We could fix that -- or maybe we should just not allow to disable those
plugins? What's the point?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #4 from Sven Brauch  ---
Ah, great, that's getting a lot closer to a solution. We should certainly fix
the crash. The more on-track question is though, how did the make plugin get
disabled? Did you turn it off by hand?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369324] KDevelop5 crashes when i press Build

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369324

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||m...@svenbrauch.de
 Resolution|--- |DUPLICATE

--- Comment #2 from Sven Brauch  ---


*** This bug has been marked as a duplicate of bug 369326 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #3 from Sven Brauch  ---
*** Bug 369324 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
It shouldn't crash in any case, but to debug this problem: is cmake in your
$PATH?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 369364] Calling an instance method through the class deduces arg types wrong

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369364

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Sven Brauch  ---
Yep, need to fix that. Thanks for the comprehensible report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 369367] Caught exceptions get wrong scope (py3 change)

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369367

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Severity|normal  |wishlist
   Priority|LO  |NOR
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Sven Brauch  ---
Valid issue, I'll make this a wishlist item though since "del" is not supported
at all currently. I guess adding that would go hand in hand with fixing this
issue as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 369369] Methods get wrong arguments marked as optional in tooltip

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369369

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369403] No Autocomplete for calls to qt connect()

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369403

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||m...@svenbrauch.de
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Sven Brauch  ---
Yes, that is a missing feature in 5.0. The rationale is that the new-style
signal/slot syntax which exists since Qt 5.0 is preferrable in almost all cases
over the old macro-style connect(), and the new style is supported just fine.

But yes, missing feature.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369454] Crash when opening project

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369454

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
>From a quick look it looks a bit like it tries to update the root item before
it was created during opening. There should be ways to fix that, but can you
reproduce this issue so we know it actually was that?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevplatform] [Bug 369536] Mouse cursor invisible in toolviews after typing text in editor

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369536

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||m...@svenbrauch.de
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Sven Brauch  ---
Can't reproduce. For me the cursor only hides when it is actually within the
editor area, as it should be. Anybody else can reproduce this?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 361958] outline dropdown widget jumps to function implementation in another file

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

Sven Brauch  changed:

   What|Removed |Added

  Component|CTags   |Language Support: CPP
   ||(Clang-based)
 CC||m...@svenbrauch.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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 are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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 all the search paths?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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.

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369105

Sven Brauch  changed:

   What|Removed |Added

   Assignee|kdevelop-bugs-n...@kde.org  |m...@svenbrauch.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369105

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
Thanks a lot for this info. I think the interesting line is this:

  5970: file=libxcb-dri3.so.0 [0];  needed by /usr/lib64/libGL.so.1 [0]

and that is the only thing which needs it, and conversely the only thing which
can look up symbols in it (and fail), or am I wrong here?

libGL.so.0 is taken from your system (as it should be), and thus your versions
of libGL and libxcb-dri3.so seem to be binary incompatible. Can you please
rebuild them both?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368970

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Add the path in Configure Project -> Include paths.

I eventally want to support a configurable python interpreter per project to
retrieve paths from, that's a long-standing feature request ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368970

Sven Brauch  changed:

   What|Removed |Added

   Assignee|kdevelop-bugs-n...@kde.org  |m...@svenbrauch.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368855] changing files via git (rebase, checkout) causes 100% CPU usage on 2 cores

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368855

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #3 from Sven Brauch  ---
Hm, all threads in that trace are idle.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368375] KDevelop hangs while parsing project

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368375

Sven Brauch  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Sven Brauch  ---
Yes, pretty sure this is the same issue. Fixed in 5.0.1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368689

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||m...@svenbrauch.de
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Sven Brauch  ---
I can confirm the issue is still there, I also see it sometimes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 368752] Microsoft Visual C++ Runtime Error! when trying to modify a multiline text with the shape manipulation tool

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368752

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Came across this in the forums, pasting the trace inline so it doesn't get lost
should pastebin decide to remove it:

AddrPC   Params
7FFFD7934ED4  FFE17B80  
ntdll.dll!NtWaitForSingleObject
7FFFD40775FF 48493E40 2C31  
KERNELBASE.dll!WaitForSingleObjectEx
6889EA8B 19A7F038 4AE6FE60 4AE6FE50 
Qt5Core.dll!QWaitCondition::wait
68899A47 4CA86330 4AE6FE44 0001 
Qt5Core.dll!QSemaphore::acquire
195F68EF 19A7F020  4024 
libkritaimage.dll! ??  
[C:/dev/krita-3.0.1/libs/image/tiles3/kis_tile_data_pooler.cc @ 165]
195F7025 19A7F020 4108A200 3B79A380 
libkritaimage.dll!run 
[C:/dev/krita-3.0.1/libs/image/tiles3/kis_tile_data_pooler.cc @ 187]
6889DB6C 2E475340   
Qt5Core.dll!QThread::setTerminationEnabled
7FFFD4E6B2BA 7FFFD4EC0670 3B79A380  
msvcrt.dll!_beginthreadex
7FFFD4E6B38C    
msvcrt.dll!_endthreadex
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91    
ntdll.dll!RtlUserThreadStart

AddrPC   Params
7FFFD79359A4 7FFE0010   
ntdll.dll!NtWaitForMultipleObjects
7FFFD20728C0    
WINMM.dll!timeThread
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91    
ntdll.dll!RtlUserThreadStart

AddrPC   Params
7FFFD7934ED4 4B06FDA8 484940E8 5556 
ntdll.dll!NtWaitForSingleObject
7FFFD40775FF 48493E80 484945A0  
KERNELBASE.dll!WaitForSingleObjectEx
6889EA8B  0001  
Qt5Core.dll!QWaitCondition::wait
68899CB2 19A7F060   
Qt5Core.dll!QSemaphore::tryAcquire
19607800 19A7F060 4108A300 3B7C5C50 
libkritaimage.dll!run 
[C:/dev/krita-3.0.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp @ 86]
6889DB6C 2E475340   
Qt5Core.dll!QThread::setTerminationEnabled
7FFFD4E6B2BA 7FFFD4EC0670 3B7C5C50  
msvcrt.dll!_beginthreadex
7FFFD4E6B38C    
msvcrt.dll!_endthreadex
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91    
ntdll.dll!RtlUserThreadStart

AddrPC   Params
7FFFD7938624  002BF000  
ntdll.dll!NtWaitForWorkViaWorkerFactory
7FFFD78C2F6E    
ntdll.dll!TppWorkerThread
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91    
ntdll.dll!RtlUserThreadStart

AddrPC   Params
7FFFD79359A4  7FFFD7908E42  
ntdll.dll!NtWaitForMultipleObjects
7FFFD40AC19F  48C8CA80 48C7AB20 
KERNELBASE.dll!WaitForMultipleObjectsEx
7FFFD40AC09E   393C3730 
KERNELBASE.dll!WaitForMultipleObjects
689BFAC5 48B99EE0 488D74F0 393C3740 
Qt5Core.dll!QLockFile::unlock
6889DB6C 2E475340   
Qt5Core.dll!QThread::setTerminationEnabled
7FFFD4E6B2BA 7FFFD4EC0670 393C3740  
msvcrt.dll!_beginthreadex
7FFFD4E6B38C    
msvcrt.dll!_endthreadex
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91    
ntdll.dll!RtlUserThreadStart

AddrPC   Params
7FFFD7938624 0008 340829F0 0010 
ntdll.dll!NtWaitForWorkViaWorkerFactory
7FFFD78C2F6E    
ntdll.dll!TppWorkerThread
7FFFD77E8364    
KERNEL32.DLL!BaseThreadInitThunk
7FFFD78F5E91  

[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366596

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #8 from Sven Brauch  ---
I think Kevin has patches, they just need to be upstreamed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ktexteditor] [Bug 368589] Minimap should jump to position on click

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368589

--- Comment #3 from Sven Brauch  ---
I'm with Kare, but changing it is ok as well. The problem with middle-click is
that absolutely nobody knows about it, and I think it doesn't even work e.g. on
windows.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 368556] parsing order is sometimes wrong

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368556

--- Comment #2 from Sven Brauch  ---
This should hopefully fix it, if you see it again in 5.0.1 (to be released next
week-ish), please let me know. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 368556] parsing order is sometimes wrong

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368556

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||-python/4eb9fc0ef094b03a400
   ||200543cee91b5052fe0ce
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Sven Brauch  ---
Git commit 4eb9fc0ef094b03a400200543cee91b5052fe0ce by Sven Brauch.
Committed on 11/09/2016 at 19:32.
Pushed by brauch into branch '5.0'.

fix dependency scheduling logic

It is not correct to check for the priority of the parse job; that
only exists if the job for that document was already started, which is
usually not the case. Instead, use the API to get the priority of the
document from the job queue.

M  +3-8duchain/helpers.cpp

http://commits.kde.org/kdev-python/4eb9fc0ef094b03a400200543cee91b5052fe0ce

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 368556] New: parsing order is sometimes wrong

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368556

Bug ID: 368556
   Summary: parsing order is sometimes wrong
   Product: kdev-python
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@svenbrauch.de

Sometimes parsing order is wrong, and files are not updated in the right
sequence. This needs to be investigated. A complex example is below, but I have
also seen similar issues in simpler cases.

from django.template import RequestContext
from django.shortcuts import render_to_response
from django.contrib.auth import (authenticate, login, logout)

from storageadmin.models import (Appliance, Setup, UpdateSubscription)
from django.shortcuts import redirect
from django.contrib import messages
from django.conf import settings
from rest_framework.renderers import JSONRenderer


def login_page(request):
return render_to_response('login.html',
  context_instance=RequestContext(request))

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 368556] parsing order is sometimes wrong

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368556

Sven Brauch  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368458] Can't change highlight color used when hovering identifier

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368458

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/f871ad77943e4d584f
   ||c051309d83c6d493fa51b4
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Sven Brauch  ---
Git commit f871ad77943e4d584fc051309d83c6d493fa51b4 by Sven Brauch.
Committed on 08/09/2016 at 20:49.
Pushed by brauch into branch '5.0'.

Use search background color for highlighting in the view.

So far it was always a hard-coded bright yellow.
REVIEW:128862

M  +19   -18   plugins/contextbrowser/contextbrowser.cpp

http://commits.kde.org/kdevplatform/f871ad77943e4d584fc051309d83c6d493fa51b4

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368301] Error when launching an executable when "Environment Variables" are configured

[Sven Brauch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368301

--- Comment #3 from Sven Brauch  ---
*** Bug 368292 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.