[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 136441] New: Seach in compilation output
From:       Gregory Shpitalnik <g_greg () netvision ! co ! il>
Date:       2006-10-29 0:21:24
Message-ID: 20061029022123.136441.g_greg () netvision ! co ! il
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=136441         
           Summary: Seach in compilation output
           Product: kdevelop
           Version: 3.3.4
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: g_greg netvision co il


Version:           3.3.4 (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs
OS:                Linux

It would be nice if kdevelop could enable search in the message window (compilation \
output search). Sometimes you want to find what flags were used when cirtain file was \
compiled, or whether some command was executed during the build. Scrolling up and \
down through large compilation output is not the best way of finding things. May be a \
good idea is to add "Open compilation log file" item to the message view menu and \
open. say, kdevelop.compfile when the compilation is done. This is a simple solution \
that allows searching within the file. However it's of cause bad idea to update this \
file each time something changes in the compilation output, it will cause every \
second reload of this file.


[prev in list] [next in list] [prev in thread] [next in thread]