[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: {.} {/} {/.} ...
From: |
Cook, Malcolm |
Subject: |
RE: {.} {/} {/.} ... |
Date: |
Mon, 25 Apr 2011 10:47:05 -0500 |
Ole,
Such a feature would be useful whenever you wanted to place the output of
processing a file in the same directory as the file. For instance, untarring
all the tar files found recursively in a directory tree.
Actually, having something like `find -execdir`, which runs the exec after
cd-ing to the directory holding the found file, would serve the purpose as
well, if not better. Perhaps rather add a -cd option to `parallel` which would
force cd prior to launching the process.
All of these are perhaps only useful in multicore on single server, not
distributed parallelism....????
Cheers,
Malcolm Cook
Stowers Institute for Medical Research - Bioinformatics
Kansas City, Missouri USA
> -----Original Message-----
> From: parallel-bounces+mec=stowers.org@gnu.org
> [mailto:parallel-bounces+mec=stowers.org@gnu.org] On Behalf
> Of Ole Tange
> Sent: Saturday, April 23, 2011 6:59 AM
> To: Cook, Malcolm
> Cc: parallel@gnu.org
> Subject: Re: {.} {/} {/.} ...
>
> On Fri, Apr 22, 2011 at 9:12 PM, Cook, Malcolm
> <MEC@stowers.org> wrote:
> > how about some syntax to get the dirname of {}
> >
> > maybe {..}
>
> Can you start by giving a few good examples on where this
> would be useful?
>
> What should {..} be if {} = foo.jpg (i.e. no dir)?
>
> What should {..} be if {} = mydir/ (i.e. {} is a dir)?
>
> /Ole
>
>