On Feb 12, 2018, at 5:13 PM, Branko Čibej <br...@apache.org> wrote: > >> On 12.02.2018 18:41, Bo Berglund wrote: >> On Mon, 12 Feb 2018 15:54:00 +0000, Philip Martin >> <phi...@codematters.co.uk> wrote: >> >>> Bo Berglund <bo.bergl...@gmail.com> writes: >>> >>>> svn add Fasadändring&Attefalltillbyggnad.pdf >>>> svn: warning: W155010: 'D:\Bosse\Fasadändring' not found >>> '&' has special meaning to the shell and needs to be quoted or escaped. >> I always thought that this was the case only for Linux, since & is a >> perfectly valid part of a file name on Windows... >> But I will refrain from such characters in paths in the future. > > The Windows shell has special characters, too. As far as file names are > concerned, Unix filesystems typically allow _more_ characters than > Windows filesystems.
Nevertheless I try to avoid filenames that create difficulties under either system because we have a mix Windows, Mac, and *nix. Each comes with its idiosyncrasies. Oh, and sometimes build systems don't escape everything correctly. Just my 2 cents.
