As you said, you can get par2 to use them already. (Specify them as extra command line args, in case anyone else wonders.)
As far as the feature itself, I'm opposed to it, since the main idea behind giving them the weird name is to avoid problems with either nget or the user thinking they have a correct copy. They can't just be renamed at shutdown, since repeated runs of nget on the same directory would then see them as having the correct name. Likewise for the user looking at the directory some time later where they may have forgotten to run a repair yet.. I am however considering including a cleanup script that would automatically run par2repair and then remove any leftovers. (Perhaps even nget could call it automatically on shutdown if it determined it was needed and that there is enough data to do recovery.) Of course, such a script would have to be very careful to not delete any unrelated files that happen to be laying around.. (I have a prototype that I've been using, but I'd like to maybe make it a bit more automagic before including it...) -- Matthew Mueller [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
