20100124 Beta

[jps]

20100124 is out now, with various improvements to find in files.

There's a new field in the find in files panel, which can be used to limit the files searched. Multiple wild card patterns can be used by separating them by semicolons (e.g., "*.h;*.cpp"). Prefixing a wild card pattern with a minus will result in it being used as an exclusion, e.g., "*.txt;-readme.txt".

F4 will now either go to the next find result, or the next build error, depending on which panel was used last. Shift+F4 goes to the previous result.

[Seldaek]

Thanks, I still have the problem with Find & Replace not switching focus to the Replace field when I hit tab though.

[jps]

It appears to be working for me here - does tab work as expected in the Find in Files panel?

[Seldaek]

Yup, find in files works, but replace doesn't, until I click it manually then it works for a while (not sure if it's until I restart or just "a while" though).

[kemayo]

I noticed an inconsistency in minimap behavior depending on the value of clickToScroll. If it's set to "position" you can click outside the view and then drag to move. However, if it's set to "text" then click-then-drag won't move it.

[Seldaek]

I also have problems since the last beta (or the one before I believe), when I use find/find&replace with "search in selection" enabled (it's always on here), it doesn't work anymore if there is no selection, and sometimes screws up completely and even doesn't find anything within the selection. Once it found the first result in the file, which was out of the selection, and that was it.

[ifni]

Find in Files is an absolute gem, however I have a question, what's the option to enable file opening on double click in the find in files window?

[jps]

Seladek: Search in selection does indeed work differently since the previous beta. The key difference is that now the area that it searches in is the selection as of when the find panel was opened. In the past it didn't work properly with find next.

ifni: There isn't an option for it, it should always be on. Is it not working for you at all, or just inconsistently?

[ifni]

ifni: There isn't an option for it, it should always be on. Is it not working for you at all, or just inconsistently?

It seems to work inconsistently. If you look at this image it seems related to the 'Unable to open...' string above the results (check out my 1337 mspaint skillz)
So if I attempt to open a result that was proceeded by an 'unable to open' string, it fails, otherwise it works. It seems to apply to the entire set of results for a single file.

On a related note, is there any way to suppress those 'unable to open' messages? My projects have a lot of empty __init__.py files, which it fails to open, and it fills up the find in files buffer with unhelpful information.

[jps]

Thanks for the info, I can track down what's going wrong from the imgae. I'll fix both issues for the next beta.