[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2022-12-30 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=384775

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #12 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2022-12-15 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #11 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2022-11-30 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=384775

Justin Zobel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #10 from Justin Zobel  ---
Thank you for reporting this issue in KDE software. As it has been a while
since this issue was reported, can we please ask you to see if you can
reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when
replying. Thank you!

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2018-09-28 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

RJVB  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #9 from RJVB  ---
This lead to https://phabricator.kde.org/D7930, ultimately, which is still
relevant for the 5.3 branch too.

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2018-09-27 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=384775

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #8 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-29 Thread Simon Andric
https://bugs.kde.org/show_bug.cgi?id=384775

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-21 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #7 from RJVB  ---
This was committed to the 5.2 branch too, from the looks of it?

If so I have to disappoint: the reported issues with e.g. cmakeutils.cpp and
cmakepreferences.cpp persist. These notable (from a ML post):

- when usins CMake Server import, the parser now only doesn't find the
cmakebuilderconfig.h and ui_cmakebuildsettings.h headers in cmakeutils.cpp and
cmakepreferences.cpp .

- when using JSON-based import, the parser doesn't find the interfaces/icore.h
, KLocalizedString, KMessageBox and KJobWidgets headers in cmakepreferences.cpp
and complains about undeclared QString and QStringLiteral in cmakeutils.cpp 

(Turning off cmake server import is trivial using a wrapper script around
cmake, a backdoor I really appreciate because it also gives me full control
over exactly how cmake is called.)

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-21 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=384775

Milian Wolff  changed:

   What|Removed |Added

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

--- Comment #6 from Milian Wolff  ---
waiting for info, see previous comment

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-21 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #5 from Milian Wolff  ---
Can you try again? I think I may just have fixed this issue in the master
branch.

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-19 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #4 from RJVB  ---
Created attachment 107906
  --> https://bugs.kde.org/attachment.cgi?id=107906=edit
parsing glitch in another project

So the 5.2 parser has problems not just with the KDevelop tree itself. I'm also
seeing issues with the Purpose tree, and as shown here, with a project that has
nothing to do with KDevelop/KDevPlatform whatsoever.

Often the initial impression when first opening a document is that all is fine.
Then you reparse one way or another, and the glitches pop up.

Could this be related to the closing of resources that were simply left
open/active in the 5.1 branch and earlier? IIRC Kevin has been working on that
kind of (intended) improvement.

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-16 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #3 from RJVB  ---
Comment on attachment 107880
  --> https://bugs.kde.org/attachment.cgi?id=107880
parser glitch 1

This glitch doesn't occur on Linux (same build).

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-16 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #2 from RJVB  ---
Created attachment 107882
  --> https://bugs.kde.org/attachment.cgi?id=107882=edit
parser glitch 3

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

[kdevelop] [Bug 384775] 5.2 branch: parser issues (and a few other annoyances)

2017-09-16 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=384775

--- Comment #1 from RJVB  ---
Created attachment 107881
  --> https://bugs.kde.org/attachment.cgi?id=107881=edit
parser glitch 2

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