Robert Stewart - 2014-08-27

That’s interesting. I didn’t even know about the ASCII encoding alternatives to the special characters. The issue I foresee is knowing when to make the substitution and when not. After all, @ introduces dates, labels, and changelist numbers, so finding those uses as distinct from any other may be a problem. Perhaps if I always replace @, #, *, and % with their ASCII encoded alternatives, Perforce will sort out which are part of a filename and which aren’t. However, in the manual, they say to keep those characters in the filename when adding it and escape them otherwise.

I don’t have experience with such filenames, so I’m uncertain what to change so as to avoid breaking things. If you’d like to experiment with things and tell me what works and what breaks with those substitutions, we could find a good solution.

BTW, If you’re interested, I’d be happy to send you my current development version of p4.el. It is dramatically different than the one currently on SourceForge. (I’ve never gotten around to setting up things to post the dev version to SourceForce; I need to do that.) My dev version has many new features, including a much improved menu and Customize support for options.