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 250379 - search within current file seems to not work sometimes
Summary: search within current file seems to not work sometimes
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: Search (show other bugs)
Version: 8.0.2
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
: 207415 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-02-11 17:10 UTC by Grogui
Modified: 2015-03-05 09:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
bug screen shot (60.07 KB, image/png)
2015-02-11 17:12 UTC, Grogui
Details
another exemple (33.19 KB, image/png)
2015-02-20 15:00 UTC, Grogui
Details
message.log (28.56 KB, application/octet-stream)
2015-02-20 16:48 UTC, Grogui
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Grogui 2015-02-11 17:10:15 UTC

    
Comment 1 Grogui 2015-02-11 17:12:06 UTC
Created attachment 151957 [details]
bug screen shot

See the file into attachement please.

Thank you for resolving that.
Comment 2 Ondrej Brejla 2015-02-11 17:18:40 UTC
Reassigning.
Comment 3 Milutin Kristofic 2015-02-18 17:49:59 UTC
How big is the file? Does it happen only once or it happens all the time? If it happen always, can you attach file?
Comment 4 Grogui 2015-02-20 14:27:34 UTC
Hi,

No it's not an so huge file, it's about 100Ko javascript file(nearly 2500 lines) and it happens only sometimes,

NB:If i select again the pattern in the code and paste it to the search field, the search works again (sometimes)
Comment 5 Grogui 2015-02-20 15:00:55 UTC
Created attachment 152119 [details]
another exemple

An other Exemple : a Php File of 2300 Lines and 110Ko

More detailed Use case : 

1/ I have copy/paste a search pattern from notepad++ to Netbeans
2/ Net automatically bring me to the right searched expression without i click on any button
3/ I've decided then go to an other part of the code (to verify something) and then i wanted to click on search button where my searched expression was still visible and that's the moment the issue happens (pattern no more findable )
Comment 6 Milutin Kristofic 2015-02-20 16:16:46 UTC
In your last example you have pressed whole word, so if in searchbar is find term ending with space it should write it is not in document. It is not clear what is in find textfield. 

However, can you attach messages.log from your netbeans directory? Maybe there is some exception. This is serious bug I would like to know how to reproduce it.
Comment 7 Grogui 2015-02-20 16:48:13 UTC
Created attachment 152122 [details]
message.log

(In reply to Milutin Kristofic from comment #6)
> In your last example you have pressed whole word, so if in searchbar is find
> term ending with space it should write it is not in document. It is not
> clear what is in find textfield. 
> 
> However, can you attach messages.log from your netbeans directory? Maybe
> there is some exception. This is serious bug I would like to know how to
> reproduce it.

First of all, thanks for your help cause you're right it's a rather annoying bug that makes me crasy sometimes.

Then the "whole word" parameter was not pressed in my last test, whatever i'm trying now and whatever i use the "whole word" parameter or not it's working just now, do not understand why, i'm sure that there is no space neither at the beginning nor at the end of the pasted searched pattern.

I'm attaching the message.log file.
Comment 8 Grogui 2015-03-05 08:51:31 UTC
Hi,

I have just encountered this issue right now again but i've also found a way to resolve it quickly.

Indeed, i've just to click on the close cross icon at the very left of search block toolbar and lauch a new search by typing ctrl+F then when the search block appears again the searched pattern is directly found...
Comment 9 Milutin Kristofic 2015-03-05 09:27:06 UTC
*** Bug 207415 has been marked as a duplicate of this bug. ***