2012/11/19 Stefan Bellon <sbel...@sbellon.de>: > I think this restriction > > * Does not contain any of these characters in the path: "\*[]?" > > is too arbitrary. If you try to create a file or directory in the > Windows explorer and type e.g. a " then you get a bubble help with the > information that you must not use any of the following characters > > \ / : * ? " < > |
An EXPERIMENTAL fix is committed now in [82ce90f91c]. It handles the invalid characters in the same way as cygwin does: <http://cygwin.com/cygwin-ug-net/using-specialnames.html> In cygwin it is no problem at all to use such characters in filenames, except for the backslash. I found ':' problematic as well, as it is used in UNIX as path separator (path1:path2) and on Windows as drive separator (C:\foo). The advantage of this method is that using a cygwin-compiled fossil will have exactly the same result as using a win32 version of fossil. The cygwin shell will show all filenames as they are expected to be. From Windows explorer they might look strange, but nothing goes wrong. The only remaining problematic characters are '\' and ':', all others are - on Windows - translated to a safe Unicode range. At this moment I don't see a way to work around the two remaining problematic characters. I think this deserves a lot more testing. I will.... Regards, jan Nijtmans _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
