Home Download Buy Blog Forum Support

ST3: Problems with "Find in files"

ST3: Problems with "Find in files"

Postby HellesAngel on Mon Jul 01, 2013 8:39 am

I spend a lot of time trying to untangle my clients' spaghetti C, which is a mess on an epic scale. The search functions are my life-line whenever the symbol lookup fails. I'm using ST3 build 3047.

Firstly I was a bit surprised how limited the "find in files" is, "Where" is offering only 'open files and folders' and then with a few mouse clicks I can add a directory. Obvious 'nice to have' options could include file filters - search all files, search all files in project, search all recognised source file types in the project tree, give a file filter *.ext, search in comments/ignore text in comments, and so on. Do these filters exist and I missed them, or could they be added to a wish list?

So, search is launched and now currently I'm looking at this:
Searching 61828 files for "is not a valid namespace name"

and wondering how long it will take... A busy indicator, or progress bar/files processed counter/current file name, would be lovely. Perhaps I missed it (like the symbol indexing indicator) but I really did look closely!

Then, the console is full of this:
Unable to auto detect encoding, using fallback encoding Western (Windows 1252)
Unable to auto detect encoding, using fallback encoding Western (Windows 1252)
Unable to auto detect encoding, using fallback encoding Western (Windows 1252)
etc. hundreds of times


It would be nice if these messages were a bit more informative - ie. contain the file name it's complaining about and in general not the same message printed 1000x but perhaps something like this:
Unable to auto detect encoding, using fallback encoding Western (Windows 1252)
Unable to auto detect encoding, using fallback encoding Western (Windows 1252)
Last message repeated 61000 times.


You get the idea.

In general a lot of messages like this come because the client has a borked version control system that occasionally spits binary characters into text files, this then confuses ST into thinking that it's a binary file. I've seen the 'ignoring binary file' warning many times. It would be nice here if ST would trust the extension more than what it finds. An error/warning message would be fine, but it shouldn't just stop searching/indexing because of a few junk characters in what's otherwise quite obviously a source file.
HellesAngel
 
Posts: 11
Joined: Thu Jun 27, 2013 8:44 pm

Re: ST3: Problems with "Find in files"

Postby adzenith on Mon Jul 01, 2013 4:09 pm

You can use things like *.ext in the box, separated with commas.
adzenith
 
Posts: 1215
Joined: Mon Oct 19, 2009 9:12 pm

Re: ST3: Problems with "Find in files"

Postby HellesAngel on Wed Jul 03, 2013 5:35 am

That's helpful, thank you, however I'm hoping for much more ;)
HellesAngel
 
Posts: 11
Joined: Thu Jun 27, 2013 8:44 pm

Re: ST3: Problems with "Find in files"

Postby geerk on Wed Nov 20, 2013 10:48 am

This endless fallback consume 100% CPU. I hope this problem will be solved soon, because this is very irritating.

Thanks.
geerk
 
Posts: 1
Joined: Wed Nov 20, 2013 10:45 am


Return to Technical Support

Who is online

Users browsing this forum: Exabot [Bot], Google [Bot] and 26 guests