Bug 82551 - Error window is missing important error lines from compiler
Summary: Error window is missing important error lines from compiler
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: Output Views (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-31 04:51 UTC by Jon Smirl
Modified: 2004-06-09 17:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Smirl 2004-05-31 04:51:30 UTC
Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

The error display window is not including the lines showing where the h file was included from. These are important to locating the error.


In file included from ../dri_client/imports/glxclient.h:52,
                 from ../common/dri_util.h:57,
                 from ../common/utils.h:33,
                 from ../common/utils.c:33:
../../../../../include/GL/glx.h:38:22: X11/Xlib.h: No such file or directory
../../../../../include/GL/glx.h:39:23: X11/Xutil.h: No such file or directory
In file included from ../dri_client/imports/glxclient.h:52,
                 from ../common/dri_util.h:57,
                 from ../common/utils.h:33,
                 from ../common/utils.c:33:
../../../../../include/GL/glx.h:179: error: syntax error before "GLXPixmap"
../../../../../include/GL/glx.h:179: warning: type defaults to `int' in declaration of `GLXPixmap'
../../../../../include/GL/glx.h:179: error: ISO C forbids data definition with no type or storage class
../../../../../include/GL/glx.h:180: error: syntax error before "GLXDrawable"
Comment 1 Sascha Cunz 2004-06-09 02:32:55 UTC
Jon, are you sure to use "Short compiler output" ( and not "Very short compiler output" ) - See Context Menu of "Messages" Tab.

Works for me in Full and Short mode. "Very short" (as the name would imply) keeps those messages away.
Comment 2 Jon Smirl 2004-06-09 04:48:48 UTC
I've been using kdevelop for a year and never knew there was a context menu in the 
output views. I see now that a couple of views have them. Since I never knew these menus were there I've been running with the defaults. Maybe the default should be changed to Short from Very Short.

I also recommend figuring out some way of giving a visual clue that those context menus exist. 
Comment 3 Bernd Pol 2004-06-09 14:13:45 UTC
There are clues.
1) There is a setting on the Configure KDevelop General Page
2) There is a note in the KDevelop User Manual, Chapter 6. Configuring KDevelop -> General Setup -> Messages Output View

BTW: I routinely right click into any unknown window I run across -- just in case there is a popup help window ;)
Comment 4 Jon Smirl 2004-06-09 17:07:08 UTC
I may not be a good example of a normal user since a lot of these features have been slowly added as I used the product. It might be more useful to check with a new user.
Comment 5 Jon Smirl 2004-06-09 17:07:46 UTC
Option was there all along