There is a curious matter found in the printing of text files, and in the loading out of them for screen viewing, and as the programs themselves are transferred as text, and as they are loaded and run, and that drawing, music, and even photographic and video files (these less so,) are written and revised as text. In this the original typing, and with the backspacing and typeovers, inserts and revisions: that they are stored exactly as they are typed in. That is, with all the back-spacing, inserts and shifting and moving around is found in the complete texts, and that only in the loading to the screen each time, or to the printer buffer, is this memory of the file finally sorted out into what will be its final form. Even store-bought discs of code, even from the best and biggest originators, contains quantities of this excess. We find that our hard drives and program files are filled with it, slowing down operation, and even causing errors.
A particular e-mail my mom showed me comes to mind. She had printed it using a system or setting which revealed all the code. The few paragraphs of the printed letter were at the top of the page. Grouped near the bottom below a large white area was another large paragraph of page control symbols, looking like a view of one end of a large set of nested parentheses, such as in algebra. Undecipherable to the casual observer, the machine had to nonetheless,do the extra work required to resort it, and made the printing look normal and correct. Think what it is when your machine finds this much hash on startup each time, (And more!), and has to refigure the contexts and revisions each time, just to run some simple programming!
Since I discovered this for myself, and that I had someone who knew of these things to talk to, when I mentioned it he said that the only way they had ever found was that you could print out your files, then scan them back in to obtain a perfect document in your archive. One other fellow showed me this: ( ~_00_+ ) curiosity, he puts it into those blanks in web pages that ask for an entry, and he said that it cleans the mistakes and errors of many a user who may have entered there. I have made up a batch of text files with this alone in them (with spacing, etc.), and I keep them stacked in folders three deep on all my drives. I'm told that they shouldn't overlap, but to keep a gap each fourth level in the overall structure of your folder-within-folder architecture so that they will work there properly.
CAPTAB There is a surprising way I have found that works. By repeatedly visiting a highlighted spot, such as a link might be, or a filename, as may be highlighted within any folder, including the desktop, BY USING THE TAB KEY IN REVERSE. This evidently removes much of the unwanted hash, and that eventually, the files are clean as can be, store smaller load cleaner and better, and run with more stability and speed. I have cleaned some of my files so completely that web servers run off of my little portal, the few instances where my answer was ready that much sooner. (Earthlink 5.0 and TotalAccess in Program Files was the example, but Windows was just as bloated.)
I merely close my files and highlight them (Ctrl+A), then CAPTAB! (Shift+Tab). Sometimes a brief tap of CTRL will make it halt in an advantageous spot, like a search window, or the address bar. It works as well or better!
There is a format to move into these nested folders, CAPTAB a while, then ENTER by using the BACK ARROW (Green). This works well to set the work formally, and works well with web pages when the LINK used to move yourself into a lower folder is found on the same server. Again the back arrow is used as an Enter or Close command. Since this is a rather slow process, it is interesting to note that beyond hearing your drive re-file shrunken texts, you can watch for any progress by viewing the little icon in the left of the address bar. The flickering of that little icon tells you it's working!