[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2021-03-01 Thread Max Schwarz
https://bugs.kde.org/show_bug.cgi?id=385113

Max Schwarz  changed:

   What|Removed |Added

 CC||m...@x-quadraht.de

--- Comment #7 from Max Schwarz  ---
For me, adding a new MIME type "text/x-glsl" in system settings -> Applications
-> File Associations with the appropriate file endings (e.g. *.glsl) helps.

Then kmimetypefinder5 returns text/x-glsl instead of text/x-csrc.

I had to clear out my kdevelop cache to remove any lingering error markers.

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2019-07-25 Thread Daniel Bernar
https://bugs.kde.org/show_bug.cgi?id=385113

--- Comment #6 from Daniel Bernar  ---
I fixed it as follows:
1. Right-click on the project
2. Configure project
3. Cppcheck
4. Include Directories
5. Ignored includes - here I pasted the path to the folder with shaders

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2019-07-24 Thread Daniel Bernar
https://bugs.kde.org/show_bug.cgi?id=385113

Daniel Bernar  changed:

   What|Removed |Added

 CC||dbcong...@gmail.com

--- Comment #5 from Daniel Bernar  ---
ArchLinux, KDevelop v5.3.3. The same issue. Editing is possible in some other
program (it's good that KDevelop allows opening files by default in another
program), but when I commit changes, these "errors" interfere. If someone found
a solution to this problem, please share it.

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2017-09-27 Thread Francis Herne
https://bugs.kde.org/show_bug.cgi?id=385113

Francis Herne  changed:

   What|Removed |Added

 CC||m...@flherne.uk
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Francis Herne  ---
The C++ file matching is extremely overzealous...see also:

https://bugs.kde.org/show_bug.cgi?id=360081
"Attempting to parse text/plain files as C or C++" (reported by me)
for *.nml files.

https://bugs.kde.org/show_bug.cgi?id=381709
"Matlab script interpreted as C++"
for *.m files.

It also tries to parse TypeScript (*.ts), and generally anything remotely
C-like.

This occurs despite kmimetypefinder returning text/x-matlab, text/x-typescript
etc.

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2017-09-27 Thread Staffan Palmroos
https://bugs.kde.org/show_bug.cgi?id=385113

--- Comment #3 from Staffan Palmroos  ---
Created attachment 108064
  --> https://bugs.kde.org/attachment.cgi?id=108064&action=edit
Screenshot of the problem

Here is a screenshot of it. The Problem tab is full of errors because it parses
it as C(++) code when it isn't.

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2017-09-27 Thread Staffan Palmroos
https://bugs.kde.org/show_bug.cgi?id=385113

--- Comment #2 from Staffan Palmroos  ---
Created attachment 108063
  --> https://bugs.kde.org/attachment.cgi?id=108063&action=edit
Test project for GLSL parsing issues

Sure, here's one. It's not a complete program, just some vertex and fragment
shaders that triggers the problem mentioned.

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

[kdevelop] [Bug 385113] Turn off semantic analysis for GLSL (or fix it)

2017-09-27 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=385113

--- Comment #1 from Kevin Funk  ---
Do you have an minimal working example which exhibits the problem?

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