Re: path = not supporting *

Sebastian Schleussner <[email protected]> writes:

> * Consider the legacy/beginner case "path = Path to the lake/Designs". A 
> keyword-optional Unison would happily parse that as a PathSpec "to the 
> lake/Designs" without sensing any reason to issue a warning. ;)

That's a good point.  Really, nobody should use spaces in file names,
and any syntax that allows filenames with spaces to be represented
should have quoting, but that ship has sailed :-)

So it would have to be PathComplex or something, or perhaps PathRegex
and PathGlob.

But still, the other half of the question remains: are the people that
want this willing to do all the work.  There is no magic support team
working on user requests.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].