I'm using the new TPv8. When I search through my websites with the "Find in Files..." function, often the majority of the resulting lines are warnings:
Code: Select all
WARNING: Line 3 too long (> 64k characters) in C:\websites\Sitebytes2010\ergobase.nl_old\tests\yaml\docs\assets\css\layout-min.css
WARNING: Line 12 too long (> 64k characters) in C:\websites\Sitebytes2010\ergobase.nl_old\tests\yaml\docs\assets\js\snippet\jquery.snippet.min.js
WARNING: Line 1 too long (> 64k characters) in C:\websites\Sitebytes2010\fleurenhof.com\httpdocs\edit\tinymce\tiny_mce.js
WARNING: Line 7 too long (> 64k characters) in C:\websites\Sitebytes2010\fleurenhof.nl_old\httpdocs\common\bootstrap\3.1.1\css\bootstrap.min.css
WARNING: Line 5 too long (> 64k characters) in C:\websites\Sitebytes2010\fleurenhof.nl_old\httpdocs\common\bootstrap\3.2.0\css\bootstrap.min.css
WARNING: Line 5 too long (> 64k characters) in C:\websites\Sitebytes2010\fleurenhof.nl_old\httpdocs\common\bootstrap\3.3.1\css\bootstrap.min.css
WARNING: Line 5 too long (> 64k characters) in C:\websites\Sitebytes2010\fleurenhof.nl_old\httpdocs\common\bootstrap\3.3.5\css\bootstrap.min.css
1. One solution would be not to search through any *.js and *.css files. Regretably this is not an option for a webdesigner. Obviously *.js and *.css files are important.
2. I did not find a way to switch off these warnings.
3. I also cannot find a way to exclude *.min.js and *.min.css files from the search. If it exists I am not aware of it.
4. Reading the manual:
I could use a file with all the filenames I want to search, but that's quite inflexible. Every change has to be incorporated in the file.In the In Files box, either type a space separated list of wild cards, or choose a previous list from the drop-down list. Note that by creating a file containing a list of file names, one per line, and specifying the name of that file in this box, preceded by the character '@', this command will search the specified files.
In short: I would like these warnings to disappear.
In my opinion line length should not affect searching in this way. It never did.
PS: I have noticed that the files, containing the long lines, can be edited without any warning, and that the long lines show up correctly. Eh? So it's only the searching which has problems with long lines?