Anton Shepelev wrote on Fri, 27 Mar 2020 23:40 +00:00: > Daniel Shahaf: > > but in any case, this sounds quite reasonable. How about > > assigning it the syntax «^./» (caret, dot, slash)? That way we > > only have one "special" leading character to worry about. > > That ^ character must be escaped in Windows, so I don't really like > it. My personal (and uneducated) preference of an inexperienced > user is to activate CWD URL mode in a cleaner way: either by an > option (quite possible, because SVN commands may share options), or > via a simpler and shorter syntax than (on Windows) ^^./ . I will, > however, be only happy if the caret version is implemented. It is, > after all, consistent with the current usage. > > I think other users of SVN via commadline (instead of the various > GUI plugins) should give their opinions and help the maintaners > make the correct decision.
Here are our notes about this from back when the ^/ syntax was added: http://svn.apache.org/viewvc/subversion/trunk/notes/cli-repo-root-relative-support.txt?view=markup#l42 There must have been dev@ threads too, around the time that document was written. Tilde is also special to some shells, at least in the sh/csh «~username» syntax and in zsh's «foo~bar» syntax (also part of EXTENDED_GLOB); and more generally, there's the consistency aspect, as you mention. That matters, for example, for scripts that want to escape arbitrary local paths when calling svn. Today, the rule is "Append an '@', and if it starts with a caret-slash then prepend './'."; it would be nice not to break this. An --option sounds a little too specialized to me. Also, it's a form of action at a distance (the positional arguments and the --option's presence would be coupled), whereas the ^/ syntax is self-contained. Cheers, Daniel