QuickSearch eXtended
Moderators: Hacker, petermad, Stefan2, white
Thank you.Samuel wrote:Actually it is possible with default values exactly like this.
If you use "match_beginning=1" you may search for " .pdf" to exclude all but pdf files.
I changed "match_beginning=0" to "match_beginning=1" in tcmatch.ini and restarted TC but I don't see any difference.
All other files aren't excluded.
TC 7.5b8.Samuel wrote:Do you have TC 7.5?
Do you have Ctrl+s activated.
Does any filtering work?
Can you post your "tcmatch.ini"?
I activated it using "Letters - with search dialog"
You're right. When I use Ctrl+s it does work!
However.... it is very very very slow.
p.e. in the directory which I mostly use are almost 5000 files
When I type a search parameter in Quick Search I have to wait a few seconds before Quick Search shows the typed search parameters.
====== tcmatch.ini ======
[general]
simple_search_activate_char=
regex_search_activate_char=?
leven_search_activate_char=<
preset_activate_char=>
simple_search_match_beginning_activate_char=^
and_separator_char=" "
or_separator_char=|
wdx_separator_char=/
negate_char=!
case_sensitive=0
allow_empty_result=1
filter_files_and_folders=3
match_beginning=1
use_pinyin=0
[wdx]
debug_output=1
- Samuel
- Power Member
- Posts: 1930
- Joined: 2003-08-29, 15:44 UTC
- Location: Germany, Brandenburg an der Havel
- Contact:
IMO QS is not designed to handle such big directory's. (Try Locate) It can do so but you may have a little delay. (Here I got ~500 - 1000ms delay in a 5000 files folder)
IMO also a folder with 5000 files in it can / should / must be divided in subfolders.
Nevertheless some ideas.
1) How fast is TCs native Quicksearch? (just rename "tcmatch.dll" after restart of TC)
2) You may have a little speedup (for QSE) by using: "allow_empty_result=0"
3) If you are a coder you may have a look to the source to give hints/write patchs to get more speed.
IMO also a folder with 5000 files in it can / should / must be divided in subfolders.
Nevertheless some ideas.
1) How fast is TCs native Quicksearch? (just rename "tcmatch.dll" after restart of TC)
2) You may have a little speedup (for QSE) by using: "allow_empty_result=0"
3) If you are a coder you may have a look to the source to give hints/write patchs to get more speed.
Samuel, There is no way to make the search faster?Samuel wrote:IMO QS is not designed to handle such big directory's. (Try Locate) It can do so but you may have a little delay. (Here I got ~500 - 1000ms delay in a 5000 files folder)
IMO also a folder with 5000 files in it can / should / must be divided in subfolders.
Nevertheless some ideas.
1) How fast is TCs native Quicksearch? (just rename "tcmatch.dll" after restart of TC)
2) You may have a little speedup (for QSE) by using: "allow_empty_result=0"
3) If you are a coder you may have a look to the source to give hints/write patchs to get more speed.
I don't split up anymore my files in directories.
I use "everything" to search all files and open them using TC
However .... "everything" search all files on my pc and cannot search only one panel in TC.
Quicksearch would be a great solution but I find it a bit too slow to use at the moment.
Wow I renamed tcmatch.dll as you said.Samuel wrote:Can you answer my questions? (1)
Edit:
4) Locate can use command line options to search in a path itself.
5) you shoud just create folders
6) look the code itself or try to understand how it works internally.
The search is now very vast.
What's happening?
- Samuel
- Power Member
- Posts: 1930
- Joined: 2003-08-29, 15:44 UTC
- Location: Germany, Brandenburg an der Havel
- Contact:
Can confirm that.
TC uses an internal QS then. I can confirm that TCs search is faster at 5000 files. (also Christians Chinese plugin is faster)
I will look over mine to improve performance. (Programmers here feel free to do so too)
The main problem is:
I used "wstring" instead of "wchar*". Ok - thats not really the problem.
But Christian parses the string on a "low level" (Christians search routine is relatively simple) and I use more "high level" functions from string library.
If I would use only "low level" code:
1) I probably would loose overview.
2) It probably would get buggy hard to extend / change.
TC uses an internal QS then. I can confirm that TCs search is faster at 5000 files. (also Christians Chinese plugin is faster)
I will look over mine to improve performance. (Programmers here feel free to do so too)
The main problem is:
I used "wstring" instead of "wchar*". Ok - thats not really the problem.
But Christian parses the string on a "low level" (Christians search routine is relatively simple) and I use more "high level" functions from string library.
If I would use only "low level" code:
1) I probably would loose overview.
2) It probably would get buggy hard to extend / change.
Off topic but:
Command: everything.exe
Parameter: -path %P
It can. Create a new button or user command with:raytc wrote:However .... "everything" search all files on my pc and cannot search only one panel in TC.
Command: everything.exe
Parameter: -path %P
Last edited by ZoSTeR on 2009-07-31, 13:26 UTC, edited 1 time in total.
I'am trying this but if I'am in the root "everything" searches all sub directories.ZoSTeR wrote:Off topic but:It can. Create a new button or user command with:raytc wrote:However .... "everything" search all files on my pc and cannot search only one panel in TC.
Command: everything.exe
Parameter: -path %P
How can I avoid this?
(I would like to search only the files in the directory I'am).
@Samuel, thank you very much for your Quick Search plugin. Using it with TC native search makes it very powerful.
Ok, but when I used TC build in QS it didn't exclude all files not included in the search parameter. Now it does?Samuel wrote:If you keep that file renamed then everything you do has nothing to do with my plugin. Its TCs buildin QS what you use then. (It is fast and can do the most. But mine was written to have some extras. And it works with almost no delay for 1000 files here.)
I didn't change anything.
I only added match_beginning=1 in tcmatch.ini