Multi Commander > Beta Releases
Multi Commander 6.0 BETA
Mathias (Author):
--- Quote from: Ulfhednar on March 26, 2016, 21:53:18 ---That was the only difference I could see in the files.
MC searched the contents of these files yesterday, I updated today & now it won't....
Works fine on txt with only attribute A :-\
***
Update
Been looking at this some more. May have a clue to the answer.
I added the search to the saved searches.
I found that on loading the long dir name, MC has split the name over 2 lines.
Opening form dialog (with ...) shows
C:\Users\...\AppData\Local\...\...\...\
as
C:\Users\...\AppData\Local\...\...
...\
'Correcting' this didn't alter the 0 results however.
I stripped the I attribute & it makes no difference. :-[
Can it be nested folder depth?
C:\Users\...\AppData\Local\...\...\...\*.* fails
C:\Users\...\AppData\Local\*.* works
I hope this gives you some ideas.
--- End quote ---
It only makes a different if you have set the SubLevel option to a value that prohibit in from reaching that far down.
ehh wait 2 lines in the "..." dialog ? Then it searches multiple locations
got a space that is not around " or something in there that will break the line making it think you have multiple search path,.
Ulfhednar:
Thanks for the reply Mathias. I agree with you - that is what should be & was happening.
But in this case -
* On clicking start the dialog blinks briefly & 'search completed!' is shown. (Less than 1/4 of a second.)
* I was starting the search at that sub-level. The path field correctly shows the path from the selected folder. I then saved it.
* On closing the dialog & then reopening/loading the saved search, the saved search had split the line - I found this when I opened the form to see if it was different. I edited out the line break but no difference, copying the path from the path bar into the '...' form didn't help.
Altering the SubLevel 0-all switch makes no difference.
I'm not using any unusual characters in the dir names I'm just starting at a 'deep' level - 6 or 7 steps down from drive root.
If I start at depth 4 the same file is read correctly.... ???
Mathias (Author):
--- Quote from: Ulfhednar on March 27, 2016, 12:38:01 ---Thanks for the reply Mathias. I agree with you - that is what should be & was happening.
But in this case -
* On clicking start the dialog blinks briefly & 'search completed!' is shown. (Less than 1/4 of a second.)
* I was starting the search at that sub-level. The path field correctly shows the path from the selected folder. I then saved it.
* On closing the dialog & then reopening/loading the saved search, the saved search had split the line - I found this when I opened the form to see if it was different. I edited out the line break but no difference, copying the path from the path bar into the '...' form didn't help.
Altering the SubLevel 0-all switch makes no difference.
I'm not using any unusual characters in the dir names I'm just starting at a 'deep' level - 6 or 7 steps down from drive root.
If I start at depth 4 the same file is read correctly.... ???
--- End quote ---
If you get multiple lines in the "..." dialog then you have a path that makes the search think you have multiple search locations.
space is an unusual character when it comes to paths, You probably got a space or ; somewhere in the path.
Next version will be more robust against paths like that. I thought that was already in that version. But I think I forgot to include it in the version that was pushed out.
Ulfhednar:
--- Quote from: Mathias (Author) on March 27, 2016, 14:39:50 ---
--- Quote from: Ulfhednar on March 27, 2016, 12:38:01 ---Thanks for the reply Mathias. I agree with you - that is what should be & was happening.
But in this case -
* On clicking start the dialog blinks briefly & 'search completed!' is shown. (Less than 1/4 of a second.)
* I was starting the search at that sub-level. The path field correctly shows the path from the selected folder. I then saved it.
* On closing the dialog & then reopening/loading the saved search, the saved search had split the line - I found this when I opened the form to see if it was different. I edited out the line break but no difference, copying the path from the path bar into the '...' form didn't help.
Altering the SubLevel 0-all switch makes no difference.
I'm not using any unusual characters in the dir names I'm just starting at a 'deep' level - 6 or 7 steps down from drive root.
If I start at depth 4 the same file is read correctly.... ???
--- End quote ---
If you get multiple lines in the "..." dialog then you have a path that makes the search think you have multiple search locations.
space is an unusual character when it comes to paths, You probably got a space or ; somewhere in the path.
Next version will be more robust against paths like that. I thought that was already in that version. But I think I forgot to include it in the version that was pushed out.
--- End quote ---
Ahhhh mystery solved. I didn't consider that. One dir element does have a space in its name & that's the problem! Thanks for checking this out :)
Ulfhednar:
Just updated to 2110 & search is working properly & is fast again. ;D
Thanks for all the work on this Mathias.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version