James McMurray wrote:
> How can I recursively move through a directory tree and call a function in
> each folder?
Mike Stroyan recently posted an example doing exactly this:
http://lists.gnu.org/archive/html/bug-bash/2007-11/msg00080.html
Bob
How can I recursively move through a directory tree and call a function in
each folder?
--
View this message in context:
http://www.nabble.com/Recursive-directory-traversal--tp14375793p14375793.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
Linda Walsh wrote:
> I was wondering about a possible RFE and whether or not
> it is "inadvisable" or not. I'd be surprised if no one had
> thought of it -- so maybe there is a problem in doing it.
>
> Just like:
> &>word#(preferred syntax)
> and
>>&word
> are semantically e
[EMAIL PROTECTED] wrote:
> $ echo abc
> abc
> $ #echo xyz
> $
> Now do "ESC ." and experience the pain of the buzzer or visual bell
> that means one has done something bad. Yes, I know you are against
> thinking that one would ever want the last item of something one
> commented out, but at least y
$ echo abc
abc
$ #echo xyz
$
Now do "ESC ." and experience the pain of the buzzer or visual bell
that means one has done something bad. Yes, I know you are against
thinking that one would ever want the last item of something one
commented out, but at least you don't have to chastise them :-( I
pers
Linda Walsh wrote:
I was wondering about a possible RFE and whether or not
it is "inadvisable" or not. I'd be surprised if no one had
thought of it -- so maybe there is a problem in doing it.
Just like:
&>word#(preferred syntax)
and
>&word
are semantically equivalent to ">w
At 17.12.2007, Bob Proulx wrote:
Patrick Nagelschmidt wrote:
> The script below fails on my box with the following output:
>
> 1197676800
> date: invalid date `1970-01-01 \033[?1034h1197676800 sec'
>
> So for some reason the value passed to date got a nasty prefix.
Andreas Schwab wrote:
> Patrick Nagelschmidt <[EMAIL PROTECTED]> writes:
>
>> ++ echo '1197919330 - (1197919330 % 86400) - 86400'
>> ++ bc -i
>
> This is bogus. Why are you forcing bc in interactive mode?
I'm assuming this is the problem, since bc -i uses readline, and the
bogus sequence looks
Patrick Nagelschmidt wrote:
> The script below fails on my box with the following output:
>
> 1197676800
> date: invalid date `1970-01-01 \033[?1034h1197676800 sec'
>
> So for some reason the value passed to date got a nasty prefix.
I cannot recreate the problem.
Patrick Nagelschmidt <[EMAIL PROTECTED]> writes:
> ++ echo '1197919330 - (1197919330 % 86400) - 86400'
> ++ bc -i
This is bogus. Why are you forcing bc in interactive mode?
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germ
At 17.12.2007, Chet Ramey wrote:
I can't reproduce this on fedora core 6, which is the closest Linux
box. I suspect this is prompt string or PROMPT_COMMAND related, so a
transcript of running this script with `bash -x' would help.
No problem:
$ bash -x "./test.sh"
+ alias 'scr=screen -R '
+ '
Patrick Nagelschmidt wrote:
> Machine Type: i686-redhat-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 33
> Release Status: release
>
> Description:
> The script below fails on my box with the following output:
>
> 1197676800
> date: invalid date `1970-01-01 \033[?1034h11
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
-DP
13 matches
Mail list logo
