Version: 3.0 alpha4 (using KDE KDE 3.1.1) Installed from: SuSE RPMs Compiler: gcc 3.3 OS: Linux Test case: I have a project that lives in: /home/eisfuchs/Development/cvs/konversation/ where "eisfuchs" is a symlink to /attic/backup/home/eisfuchs When I double click on a class in the class browser, everything is fine. Now change something that produces an error and recompile. The error reporter tells you where to look. Click on the error line and you will see, that another window opens, with the same class file in it, but the "resolved" symlink part. Try to "Compile this File" now. gideon will tell you that this file is not in your project's folder. Additionally you now have two different views of the same file. This can lead to confusion and unintentional reverting of changes made in the other window. It seems that only the error reporter is suffering from this bug.
This is quite nasty. Turns out that the outputview is fed the "resolved" path from the make process. This makes the outputview paths not match the paths the rest of gideon works with, since those are the "symlinked" paths.
Jens's fix for this is now in CVS - we're all praying that it's the final resolve!