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

List:       kdevelop-bugs
Subject:    [Bug 134467] New: Enhancements to grep output view
From:       Daniel "Calviño" "Sánchez" <danxuliu () gmail ! com>
Date:       2006-09-21 17:19:52
Message-ID: 20060921191951.134467.danxuliu () gmail ! com
[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=134467         
           Summary: Enhancements to grep output view
           Product: kdevelop
           Version: 3.3.4
          Platform: Mandriva RPMs
        OS/Version: Linux
            Status: NEW
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: danxuliu gmail com


Version:           3.3.4 (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
Compiler:          gcc 4.0.1 
OS:                Linux

Right now, grep/find in files output view is "only" an embellished view of grep \
output with navigation to the clicked matches.

The output format for each file is a line containing the full name of the file \
followed by all the matches in that file, one in each line. Each line is started by \
the line where the match is.

The output view would be more useful if, optionally, it could be shown in a tree \
structure. Each directory and file would be a tree item that could be expanded and \
collapsed. Each match would be a leaf in the tree item of its file.

The tree should keep the same structure as the file system, but only from the base \
directory used to make the search.

Moreover, when searching in files, only a subset of the results shown is really \
important, while others are only junk for the purpose of the search. Elements should \
be able to be removed from the output, so you can end only with the results you \
really care about.

Additionally, an option to keep the output view in sync with the real file could also \
be interesting, but possibly wouldn't worth the effort to implement it.

Here it is an example of the output shown by the current grep output and the one \
proposed. A search for "world" is made in directory src of the current project, named \
foo:

Current output:
/home/johndoe/Projects/foo/src/bar.cpp
42: hello += world;
108: world = i18n("World");
/home/johndoe/Projects/foo/src/plugin/foo.cpp
23: message = getWorld();

Proposed output (with foo.cpp matches folded):
(-)--bar.cpp
 |    |
 |    +--42: hello += world;
 |    +--108: world = i18n("World");
 |
(-)--plugin
      |
     (+)--foo.cpp


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