Comment 27 for bug 81844
Revision history for this message
| Richard Wilbur (richard-wilbur) wrote Re: [Bug 81844] Re: backslash in filename causes InvalidEntryName etc | #27 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On Jan 14, 2018, at 04:46, Jelmer Vernooij <email address hidden> wrote:
> At that point, it's an error - not a warning. We can't check out files with backslashes in the names on Windows.
Ugh! You are right.
I would be in favour of either:
1. offering to bzr mv the offending files to substitute a user-specified legal character for the backslash (as part of the branch operation, so it can succeed!),
-or-
2. nag the user at nearly every opportunity to change the problematic names (with a helpful message showing proper bzr syntax to accomplish the transformation). Id est, at commit, cp, mv, add, status, info, et cetera.
Otherwise, I would be in favour of at least giving a detailed explanatory error message mentioning which file(s) at what path(s) are causing the problem--whether we refuse to add, cp, mv, et cetera or simply refuse to branch onto a filesystem that can't handle the filename(s). We could offer syntax to fix the problem (valid on a *nix platform).