Judging by that debug output, the problem is almost certainly not in gideon, but more 
likely in your editor part. What editor part do you use? Kate? 

Hi, 
 
I use kdevelop 3.0a4a and have a problem with the grep-function: 
 
When I scroll down in the grep-results, and select a result-line then the 
editor shows a wrong position. This doesn't happen, if I don't scroll down. 
Another precondition is that I have selected "Devices -> Mouse -> 
Double click to open files/directories" in the control-center. When I use 
"Single click to open files/directories" everything works fine. 
 
I've analyzed the problem a bit more and the problem seems to be the 
KListBox-implementation, which doesn't behave correctly for "Double-clickers". 
 
Nevertheless I would recommend to change the GrepViewWidget so that it always 
connects the signal clicked() instead of executed(). 
 
kdevelop-3.0a4a/parts/grepview/grepviewwidget.cpp 
... 
GrepViewWidget::GrepViewWidget(GrepViewPart *part) 
    : ProcessWidget(0, "grep widget") 
    , m_matchCount(0) 
{ 
    grepdlg = new GrepDialog(this, "grep widget"); 
    connect( grepdlg, SIGNAL(searchClicked()), 
             this, SLOT(searchActivated()) ); 
    connect( this, SIGNAL(clicked(QListBoxItem*)),  // clicked instead of executed 
             this, SLOT(slotExecuted(QListBoxItem*)) ); 
 
    m_part = part; 
} 
... 
 
Best regards, 
Joachim 
joachim.eibl@gmx.de 
 
PS: Otherwise I use Suse 8.2, with KDE 3.1.1. 

Fixed in CVS, thanks for the patch 

Sorry, but even when single click is selected, the problem persists. FYI, the latest 
gideon from CVS is used.  

Just to make sure: the file you click isn't open and edited? grep works on disk, so if you 
have made any unsaved changes, the line numbers will not match up. 
 
Just to make sure we're not chasing ghosts... :) 

Not at all, sometines the grep view opens a file and go the the first line. And 
sometimes it makes the whole gideon crashed and prints this message: 
kdevelop (grep view): context in grepview 
kdevelop (core): Word:iConnectedSocket: 
kdevelop (grep view): context in grepview 
kdevelop (core): Changing to dir 
kdevelop (core): [virtual void PartController::editDocument(const KURL&, int)] 
file:/user/fred/cvs/communitel_3_13/netergy/edev/sw/src/protocols/call/h323/ccapi/src/h323ccapi.c 
linenum 4287 
kdevelop (core): mimeType = text/x-csrc 
kdevelop (core): factory = 0x87a6ba0 
kdevelop (core): Encoding: , extension: 0x9f76948 
kdevelop (core): MainWindowShare::slotGUICreated() 
kdevelop (core):  *** found "set_confdlg" action - unplugging 
qeditor: CppSupportPart::activePartChanged() 
kdevelop (core): dcop emitting loadedFile 
/user/fred/cvs/communitel_3_13/netergy/edev/sw/src/protocols/call/h323/ccapi/src/h323ccapi.c 
Alarm clock 
 

Changing the editor from Embedded Text Editor Advanced to Qt Designer Text 
editor solves this problem.  

>sometines the grep view opens a file and go the the first line 
 
Yeah, this is a known katepart bug. This can happen for large files (that isn't already 
open). I've seen it with files 2000+ lines.  
 
Never seen that crash though. 

this behaviour is fixed for kde head's kate, it now load the file syncronous like qeditor, 
therefor such set cursor stuff works after openURL returned