Re: [fossil-users] filename contains illegal characters

2010-06-28 Thread Michael Richter
On 29 June 2010 02:18, Eric wrote: > [] are there for the same reason as * and ?: > > ~ $ ls -d p[lu]* > play public_html > Ah. I was unaware of that expansion. I always used something like p{l,u}* in those situations. -- "Perhaps people don't believe this, but throughout all of the discuss

Re: [fossil-users] filename contains illegal characters

2010-06-28 Thread Eric
On 28 June 2010 at 3:26 pm, "Michael Richter" wrote: > On 28 June 2010 21:20, Kevin Greiner wrote: > >> For a few files I see the following error: >>fossil: filename contains illegal characters: prep_20100113[1] clean/ >> 135816_0001.ps >> >> I understand it's the square brackets that are caus

Re: [fossil-users] filename contains illegal characters

2010-06-28 Thread Michael Richter
On 28 June 2010 21:20, Kevin Greiner wrote: > For a few files I see the following error: >fossil: filename contains illegal characters: prep_20100113[1] clean/ > 135816_0001.ps > > I understand it's the square brackets that are causing this error but not > why this is by design. Could someone

[fossil-users] filename contains illegal characters

2010-06-28 Thread Kevin Greiner
This is perhaps a non-typical use case but I'm trying to take a daily snapshot of a network share here at work. Thousands of files in thousands of folders over which I don't have any control but for which I'd still like to see a daily change history. I'm using a command like this to get new files