Some ideas
Posted: Wed Mar 25, 2015 1:30 pm
Thanks, this program is very useful, I would like to offer some suggestions based on my experiences.
- Ability to list all files without any in-file searching, according to current filters and location would be useful when working on big number of files. This way we could narrow the selection further using the many sorting options.
- Ability to set a file size range could be useful for example to avoid big files or big number of useless files. But the first suggestion above would eliminate this need, even if not as effectively.
- Ability to load a file list from a text file for highly specific searching. The list could be generated using the already implemented feature that allows to copy the path/file names to clipboard. So let's say there are millions of files and we only need to work on some specific files we could generate a list using TextCrawler or some other program and could resume to work on the list on TextCrawler at a later date. The current alternative I use is by listing the file names by semicolons on the file filter with or without wildcards but this may result in unwanted files from different paths or other problems (very long lists?).
- Bug? If I search for regexp ^ it finds zero-byte files but not when I use limit to lines from 1 to 1. I actually tried this hoping it would speed up finding empty files. The empty files are not useful by themselves, but their path names are useful in my case.
- (If this is currently possible) The recent feature of replacing with path/file name is a useful addition but if it was possible to use as many of the file attributes (path, file name, file type, file size, date, year, month, day) as possible as variables in both finding and replacing text, it would be very useful.
Like: $filepath, $filename, $filesize, $filetype etc.
Example
Regex: $filename
Replace: Full Path: $filepath\$filename \r\n Size: $filesize \r\n Year: $cyear \r\n Last Update: $mdate
(c for created, m for modified)
- Ability to list all files without any in-file searching, according to current filters and location would be useful when working on big number of files. This way we could narrow the selection further using the many sorting options.
- Ability to set a file size range could be useful for example to avoid big files or big number of useless files. But the first suggestion above would eliminate this need, even if not as effectively.
- Ability to load a file list from a text file for highly specific searching. The list could be generated using the already implemented feature that allows to copy the path/file names to clipboard. So let's say there are millions of files and we only need to work on some specific files we could generate a list using TextCrawler or some other program and could resume to work on the list on TextCrawler at a later date. The current alternative I use is by listing the file names by semicolons on the file filter with or without wildcards but this may result in unwanted files from different paths or other problems (very long lists?).
- Bug? If I search for regexp ^ it finds zero-byte files but not when I use limit to lines from 1 to 1. I actually tried this hoping it would speed up finding empty files. The empty files are not useful by themselves, but their path names are useful in my case.
- (If this is currently possible) The recent feature of replacing with path/file name is a useful addition but if it was possible to use as many of the file attributes (path, file name, file type, file size, date, year, month, day) as possible as variables in both finding and replacing text, it would be very useful.
Like: $filepath, $filename, $filesize, $filetype etc.
Example
Regex: $filename
Replace: Full Path: $filepath\$filename \r\n Size: $filesize \r\n Year: $cyear \r\n Last Update: $mdate
(c for created, m for modified)