This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 7311 - Find Results dialog should show matching text lines
Summary: Find Results dialog should show matching text lines
Status: RESOLVED DUPLICATE of bug 33717
Alias: None
Product: utilities
Classification: Unclassified
Component: Search (show other bugs)
Version: 3.x
Hardware: All All
: P4 enhancement (vote)
Assignee: issues@utilities
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2000-08-08 17:57 UTC by eakle
Modified: 2003-08-04 10:02 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description eakle 2000-08-08 17:57:16 UTC
If I do a Find operation on a Filesystem Folder in the Explorer (text search),
the "Search Results" dialog shows me the files where it found matches, and also
the line numbers in each file where matches occurred.  I can click those line
numbers and it positions me on that line in the source file.  That is nice, but
often most of the search 'hits' I get are bogus and I would like to avoid having
to look at the source file for each 'hit' in order to evaluate it.  This could
be accomplished by changing the "Search Results" dialog:  1.  When I open a file
where a 'hit' occurred, don't show me the same thing as I see in the  Explorer
-- instead, show me to actual lines of text in the file where the hit occurred
(just like grep would do).  2.  Modify this dialog to give more room for showing
text lines (remove bottons from RHS); also the list of line numbers below the
buttons would no longer be needed.
Comment 1 eakle 2000-08-08 18:06:59 UTC
double-clicking a line of text where 'hit' occurred would position you on that
line in source editor (sorry, I forgot to mention this).
Comment 2 Tomas Pavek 2000-09-22 09:38:59 UTC
Clicking "Show All Details" button the output window is opened and filled with
whole matching text lines which behaves described way. Only difference is that
hits from all files are put together (grouped of course).
Comment 3 Peter Zavadsky 2001-04-04 09:21:06 UTC
Reassigned to utilities.
Comment 4 Jan Chalupa 2001-05-06 15:21:32 UTC
Target milestone -> 3.3
Comment 5 eakle 2001-05-18 01:27:18 UTC
In the Search Results dialog, in the list field titled "Position within the 
file" which currently shows line numbers, how about replacing that with 
"Matching line within the file" and show the matching line itself, rather than a 
line number?  I don't think people care about what the line number is, so 
instead of showing that, let's show the actual source line.  We should keep the 
current behavior, where if you click a line in that box, then the source file 
scrolls there.
Comment 6 Jan Chalupa 2001-11-27 17:26:35 UTC
Target milestone -> 3.3.1.
Comment 7 eakle 2002-03-07 22:02:33 UTC
I just did a search and got 75 hits, which is too many to evaluate in 
this window (would take me too long).  I could have narrowed the list 
a lot if I could have sorted the list by package name, because I know 
that hits in some packages don't need to be looked at.  But I can't 
sort by package name (and I can't even see a Package name until I 
click on a Result line).  Suggestion: replace the current 
Explorer "Search Results" panel with a JTable that has 3 columns: 
type (the icon), Name, and Path; clicking on the column title sorts 
the table on that column; I wouldn't bother showing FileSystem, and I 
would put the "Position within the File" (which hopefully will become 
the actual source lines) below the JTable, rather than beside it.  I 
believe this would make the window simpler, and more powerful.
Comment 8 Marek Grummich 2002-07-22 11:52:38 UTC
Set target milestone to TBD
Comment 9 Marek Grummich 2002-07-22 11:55:50 UTC
Set target milestone to TBD
Comment 10 Marian Petras 2003-08-04 10:02:14 UTC
In order to have this problem tracked as a single entry in IssueZilla,
I resolve this issue as a duplicate of #33717 (which is a P3 defect so
that there will be stronger press on fixing it).

I will add the reporter and people from Cc: list to the Cc: list of 33717.

*** This issue has been marked as a duplicate of 33717 ***