On Monday 04 May 2009 21:12:15 Chet Ramey wrote:
> Mike Frysinger wrote:
> > On Thursday 30 April 2009 05:56:02 Jan Schampera wrote:
> >> Sandino Araico Sánchez wrote:
> >>>1.
> >>> #!/bin/bash
> >>>2.
> >>>
> >>>3.
> >>> for i in {0..15000} ; do
> >>>4.
> >>>
Mike Frysinger wrote:
> On Thursday 30 April 2009 05:56:02 Jan Schampera wrote:
>> Sandino Araico Sánchez wrote:
>>>1.
>>> #!/bin/bash
>>>2.
>>>
>>>3.
>>> for i in {0..15000} ; do
>>>4.
>>> echo $i > /dev/null
>>>5.
>>> done
>>>
>>>
>>>
>>> Re
On Monday 04 May 2009 15:46:59 jida...@jidanni.org wrote:
> Greg Wooledge writes:
> > quotes inside -- [^" "] -- works. But the backslash approach you used
> > is probably the clearest way to write it.
>
> Anyways, it should be mentioned in the man page's [...] discussion, even
> though legally o
On Thursday 30 April 2009 05:56:02 Jan Schampera wrote:
> Sandino Araico Sánchez wrote:
> >1.
> > #!/bin/bash
> >2.
> >
> >3.
> > for i in {0..15000} ; do
> >4.
> > echo $i > /dev/null
> >5.
> > done
> >
> >
> >
> > Repeat-By:
> > Run
Greg Wooledge writes:
> quotes inside -- [^" "] -- works. But the backslash approach you used
> is probably the clearest way to write it.
Anyways, it should be mentioned in the man page's [...] discussion, even
though legally one could say it is probably already mentioned, though
scattered around
On Mon, May 04, 2009 at 12:34:19AM +0800, jida...@jidanni.org wrote:
> Maybe mention in the man page at
>[...] Matches any one of the enclosed characters...
> that one will need to backslash at least any spaces used inside it:
> $ ls [^ ]
> ls: cannot access [^: No such file or directory
