wcpercent release notes and changelog

I'm rapidly running out of reasons to avoid calling this thing a 1.0 version. I'll probably increment to 0.9 when I get rid of the use of "tail". Maybe I'll jettison -d at 1.0, which might also mean that a new -d will be used to daemonize. This will break backward compatibility with calls to wcpercent from other scripts or from older .conkyrc configurations. Please feel free to report bugs, request features, and submit suggestions or patches at my Contact Page.

Version 0.8.6 (Tue Nov 21 01:41:13 MST 2006):

Changes to this version include:

Possible to-do list for the future:

Version 0.8.4 (Thu Nov 9 21:25:14 MST 2006):

Changes to this version include:

Possible to-do list for the future:

Version 0.8.3 (Mon Nov 6 22:57:02 MST 2006):

Changes to this version include:

Possible to-do list for the future:

Version 0.8.2 (Mon Nov 6 13:39:35 MST 2006):

Changes to this version include:

Possible to-do list for the future:

Version 0.8.1 (Mon Nov 6 03:56:27 MST 2006):

This version incorporates changes so that the script defaults to writing logs to a filename that changes every hour. The reason for this is simply that with the sort of brief delays in script runs triggered by conky, the single plain text logfile was growing too large too quickly. The next step will probably be to modify the script so that it only writes a new entry if the wordcount has changed since the last entry, but I'm too lazy right now to do that. This version also incorporates a simple modification to the previous that causes it to create new logfiles as needed, rather than requiring the user to create an empty logfile so the script can write to it.

Additional plans for the future include adding easy support for multiple directories (I just directly hacked my own script to hard-code directory paths -- a real sign there's something wrong with the script's feature set). Also on the horizon is potential use of a config file so that commmand line options need not be used (though you'll be able to use the options, too, of course). Don't expect me to jump on either one of these, though. At the moment, the script works the way I need it to; any further work is charity and pride rather than necessity. As such, I'll probably aim for the low-hanging fruit when deciding what changes to make next. When I'm feeling really ambitious, I might eventually make it more platform-agnostic so that it can be put to some kind of use on even Windows systems, but chances are pretty poor of that happening since I have zero concern for it working on Windows right now, and it would require a complete rewrite anyway, to say nothing of figuring out how I'd make it useful outside of use by conky or some other, similar daemon that doesn't run on Windows.

All original content may be distributed under the terms of the PDL.