On Sun, 23 Feb 2003, Theo. Sean Schulze wrote:
> On Fri, Feb 21, 2003 at 09:59:37AM +0100, J. hunted and pecked out:
> [snip]
> >
> > BTW,
> >
> > please remember that `blank' is a GNU extension, regarding portability
> > issues.. etc..
> >
> > ~$ man isblank
> >
> This shouldn't be a problem,
On Fri, Feb 21, 2003 at 09:59:37AM +0100, J. hunted and pecked out:
[snip]
>
> BTW,
>
> please remember that `blank' is a GNU extension, regarding portability
> issues.. etc..
>
> ~$ man isblank
>
This shouldn't be a problem, since I will only be using it on GNU/Linux. Also,
[:blank:] is a ch
On Thu, 20 Feb 2003, Theo. Sean Schulze wrote:
> J.,
>
> Thanks for your suggestions. While googling comp.unix.shell today, I found yet
>another method. I was not aware that "*" when used by itself matches every filename
>in a directory. Apparently, part of the problem I was having was a sid
On Thu, 20 Feb 2003, Theo. Sean Schulze wrote:
> J.,
>
> Thanks for your suggestions.
No problemo,
btw: 4 out of 5 pages on teamfinders.org are generating http 404 not found
messages. I think you should have a critical look at all the http links in
the main page.
J.
-
To unsubscribe from t
J.,
Thanks for your suggestions. While googling comp.unix.shell today, I found yet
another method. I was not aware that "*" when used by itself matches every filename
in a directory. Apparently, part of the problem I was having was a side effect of ls
and find. Here is the script that I use
