> On Tue, 4 Mar 2014, Rich Shepard wrote: > > > Naive as I am, I wonder why a simple 'rm -rf "C:\nppdf32Log\"' in > >~/.bash_logout wouldn't work as well. On Tue, Mar 04, 2014 at 01:30:32PM -0800, Rich Shepard wrote: > Actually, the correct command is 'rm -rf "C:\\nppdf32Log\\debuglog.txt"' > and should probably be preceeded by a test to see if the file is present.
Good question. It depends on the directory from which acrobat is launched. This file can end up all over the place, if you launch from the command line in another directory, or from some other program. I used to run acrobat in a shell script wrapper that removed the file, wherever the shell script was started. The file goes away when acrobat terminated normally, but that does not always happen. Obviously, the file won't be removed if acrobat is running during a crash, or goes zombie. Better to send the bits directly to /dev/null hell, where they will await the soul of the damned programmer who thought that creating this file was a good idea. Note that some browsers, like firefox, are bulked up with their own pdf reader, without this stupid "feature". Firefox pdf sometimes produces really odd results, bad fonts, etc., so all the different tools are sometimes needed. The biggest problem I have with PDFs is slow printing - Some multipage color "image" documents can take hours to print on an 100mbps 600dpi ethernet postscript printer. But then, the folks who write this stuff (most especially Adobe) don't bother with extensive automated use-case testing, actionable logging, etc. Neither do I when writing code, though I do enormous amounts of testing when making integrated circuits. Someday, computer "science" won't be an oxymoron, and current programming practices will be grouped with stone axes and medicinal leeching. Keith -- Keith Lofstrom [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
