On Wed, Nov 14, 2007 at 01:38:01PM +0800, 龙海涛 wrote:
...
> but now what i want to do is write a shell script , call all the
> autotest.sh in every leaf-directory.
You could do that with a recursive function that descends into
each directory. Using ( ) around the cd to a subdirectory will
return
On Wed, Nov 14, 2007 at 03:33:25PM +0800, Tatavarty Kalyan wrote:
> if you use "$PWD" variable the assignment seems redundant too:)
Assigning the value of "$PWD" can be useful for remembering a directory
before using cd to change the directory. That leads into the next
question about directory t
if you use "$PWD" variable the assignment seems redundant too:)
On 11/14/07, Mike Stroyan <[EMAIL PROTECTED]> wrote:
>
> On Wed, Nov 14, 2007 at 01:11:12PM +0800, 龙海涛 wrote:
> > it works.
> > 3x very much.
> >
> > On Tue, 2007-11-13 at 21:51 -0700, Bob Proulx wrote:
> >
> > > 龙海涛 wrote:
> > > > i
On Wed, Nov 14, 2007 at 01:11:12PM +0800, 龙海涛 wrote:
> it works.
> 3x very much.
>
> On Tue, 2007-11-13 at 21:51 -0700, Bob Proulx wrote:
>
> > 龙海涛 wrote:
> > > i want to store the current working dir to a variable, i write
> >
> > The most common way to save the present working directory to a
>
i have a directory, like this
/testcase
/syntaxcheck
/test1
0 (common txt file)
0.expected (common txt file)
1
1.expected
...
autotest.sh (shell script)
/
it works.
3x very much.
On Tue, 2007-11-13 at 21:51 -0700, Bob Proulx wrote:
> 龙海涛 wrote:
> > i want to store the current working dir to a variable, i write
>
> The most common way to save the present working directory to a
> variable would be to use the $(...) form.
>
> test=$(pwd)
> echo
龙海涛 wrote:
> i want to store the current working dir to a variable, i write
The most common way to save the present working directory to a
variable would be to use the $(...) form.
test=$(pwd)
echo $test
Try that.
Bob
sorry for my simple problem.
i want to store the current working dir to a variable, i write
---
pwd | read test
---
and i test the variable:
---
echo $test
---
but the $test is empty.
did i make any stupid mistake?
3x for your atten
On Sun, Nov 11, 2007 at 09:56:11PM -0800, [EMAIL PROTECTED] wrote:
...
> I had some difficulties getting job control working at
> first. I found that having the child process do a
> setpgrp() before forking to the bash instance made the
> error message about disabling job control go away.
You ne
Jan Schampera wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR=
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
11 matches
Mail list logo