Hi everyone,
Would it be possible to add another extended matching operator to already
supported ones? It's just we have "or" in @() and "not (or)" in !(), but no
"and". And combining patterns without it is awkward.
If I want to say "a and not b", I have to write "not (not a or c)", like this:
On 11/28/2012 04:58 PM, Nikolai Kondrashov wrote:
Would it be possible to add another extended matching operator to already
supported ones? It's just we have "or" in @() and "not (or)" in !(), but no
"and". And combining patterns without it is awkward.
If I want to say "a and not b", I have to w
Hi,
I need to run a script via cron that in turn launches a script to set up the
requisite environment variables needed for a successive script that is called.
Moreover, I need to change my group ID in order for the scripts called within
the cron job to run properly.
I have included a representat
On Wed, Nov 28, 2012 at 09:10:02AM -0800, Mun wrote:
> I need to run a script via cron that in turn launches a script to set up the
> requisite environment variables needed for a successive script that is called.
> Moreover, I need to change my group ID in order for the scripts called within
> the
Mun wrote:
> #! /bin/bash
> newgrp group1
> id -g -n // This shows my login group ID, not group1
The 'newgrp' command spawns a new child shell. After that child shell
exits the new group evaporates. The rest of the script continues with
the previous id. This is a common misunderstan
Hi Greg, Bob,
Thanks for your replies.
Please see my comments below.
On Wed, Nov 28, 2012 at 09:50 AM PST, Greg Wooledge wrote:
GW> On Wed, Nov 28, 2012 at 09:10:02AM -0800, Mun wrote:
GW> > I need to run a script via cron that in turn launches a script to set up
the
GW> > requisite environment
