Currently, including an invalid filename character in a backup comment can cause unintended behavior (e.g. a comment with a / in it on linux will create the backup inside a nested folder). This change simply changes the existing replacement of #'s within comments into a replacement of any invalid characters.
Szum123321
commented
2 years ago
Currently, including an invalid filename character in a backup comment can cause unintended behavior (e.g. a comment with a / in it on linux will create the backup inside a nested folder). This change simply changes the existing replacement of #'s within comments into a replacement of any invalid characters.