PostPosted: Thu May 11, 2017 5:01 pm Post subject: Caching on each syymbols in branch mode. Reply with quote Edit/Delete this post Delete this post
I use it with QuickSearch Extended http://totalcmd.net/plugring/google_like_qs.html
Why in branch mode plugin re caching on each symbol?
In normal folder view it caching once and than uses the result that stored on Temp folder.
The video in total commander https://goo.gl/photos/xQ9XYhXwySCw9mwR8
Can it be modified on ini? Or maby it plugin quicksearch extended
[Converters]
TXT={CP:ANSI} {CP:UTF8} {CP:UTF16}
HTM={CP:ANSI} {CP:UTF8}
HTML=HTM
XML={CP:UTF8} {CP:ANSI}
;MS RTF
;RTF={CP:RTF}
WRI={CP:RTF}
;Adobe Acrobat
;PDF=Conv\GetTextIFilter\GetTextIFilter.exe "{In}" "{Out}"
;HLP=PDF
;XLS=PDF
;PPT=PDF
;;DOC=PDF
;PPS=PDF
XDOC=%COMSPEC% /C Conv\XDoc2txt\xdoc2txt.exe -8 "{In}" > "{Out}" {CP:UTF8}
mht=XDOC
odt=XDOC
doc=XDOC
docx=XDOC
xls=XDOC
pdf=XDOC
;xls=XDOC
xlsx=XDOC
xlsm=XDOC
ppt=XDOC
;ppt=XDOC
pptx=XDOC
pptm=XDOC
rtf=XDOC
TextSearch (Content plugin for fulltext search in DOC)
Moderators: Hacker, petermad, Stefan2, white
TextSearch 1.6.4 dosn't rename TextSearch.Sample.ini
TextSearch 1.6.4 which I found on http://totalcmd.net/plugring/textsearch.html does not rename TextSearch.Sample.ini to TextSearch.ini and therefore it does not work after a fresch installation. I had to rename the file manually.
Additionally it keeps an old TextSearch.ini which does not fit to an overweite refresh installation.
System: Windows 7, 64 Bit.
Additionally it keeps an old TextSearch.ini which does not fit to an overweite refresh installation.
System: Windows 7, 64 Bit.
Re: TextSearch 1.6.4 dosn't rename TextSearch.Sample.ini
And what is the big problem with this ?x73 wrote:TextSearch 1.6.4 which I found on http://totalcmd.net/plugring/textsearch.html does not rename TextSearch.Sample.ini to TextSearch.ini and therefore it does not work after a fresch installation. I had to rename the file manually.
Additionally it keeps an old TextSearch.ini which does not fit to an overweite refresh installation.
System: Windows 7, 64 Bit.
Normal expected usage is to have a look on sample config files
and make your own from it.
Windows 11 Home, Version 24H2 (OS Build 26100.3915)
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
No, normal expected usage is that an installed program runs as expected. Whereas TextSearch dosn't run and does not give any message why. Furtheron it is written in the TextSearch's readme file:
"Configuration file
Plugin configuration file is TextSearch.ini, located in the plugin folder. If it doesn't exist, TextSearch.Sample.ini is copied to TextSearch.ini on execution."
and that is what doesn't work in Versioin 1.6.4. TextSearch.Sample.ini will NOT be copied to TextSearch.ini on execution.
"Configuration file
Plugin configuration file is TextSearch.ini, located in the plugin folder. If it doesn't exist, TextSearch.Sample.ini is copied to TextSearch.ini on execution."
and that is what doesn't work in Versioin 1.6.4. TextSearch.Sample.ini will NOT be copied to TextSearch.ini on execution.
Re: TextSearch (Content plugin for fulltext search in DOC)
Dear Author,
I found the plugin reports error if the filename contains the substring "及情况" (3 Chinese Char).
For example, it reports error if the filename is "及情况.doc" but it reports ok if the filename is "及情.doc".
Thus does it mean that there are bugs in the unicode filename processing?
Totalcmd 9.51 32bit with textsearch 1.6.4, and the converter is xdoc2txt.
Thanks.
I found the plugin reports error if the filename contains the substring "及情况" (3 Chinese Char).
For example, it reports error if the filename is "及情况.doc" but it reports ok if the filename is "及情.doc".
Thus does it mean that there are bugs in the unicode filename processing?
Totalcmd 9.51 32bit with textsearch 1.6.4, and the converter is xdoc2txt.
Thanks.