As we're probably all aware, `globstar' follows symlinks when doing recursive
traversal. Is it possible to, at some future version, have an option that
enables/disables (I guess enables by default for backwards compatibility)
following symlinks? This can be quite irritating when trying to traverse
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VEND$
uname output: Linux win7082 3.2.0-4-amd64 #1
On 08/01/2013 04:09 PM, Greg Wooledge wrote:
On Thu, Aug 01, 2013 at 09:37:38AM +0200, Lakshminarasimhan Srinivasan wrote:
ldapscripts do not work from inside a "while read line" loop.
The exact same scripts were working fine until the last upgrade
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/31/13 5:17 AM, Chris Down wrote:
> I think our documentation on $! is a little misleading. `man bash' states:
>
> Special Parameters
> The shell treats several parameters specially. These parameters may
> only
> be referenced
On 2013-08-01 11:37, Chet Ramey wrote:
> How about the command (or job) most recently placed in the background.
That works for me. I'd be more inclined to use "job" since it avoids confusion
about what happens when backgrounding a pipeline.
Thanks.
pgp2RdgUre66e.pgp
Description: PGP signature
On 7/30/13 7:04 PM, Curtis Doty wrote:
> The above works. Whereas the below fails.
>
> #! /bin/bash -ex
> #
>
> tee >(
> # ain't this nifty
> echo hi there
> )
>
> It burps thusly:
>
> ./foo.sh: line 7: bad substitution: no closing `)' in >(
> # ain't this nifty
> echo
On Thu, Aug 01, 2013 at 09:37:38AM +0200, Lakshminarasimhan Srinivasan wrote:
> ldapscripts do not work from inside a "while read line" loop.
> The exact same scripts were working fine until the last upgrade
> -
> #!/bin/bash
> echo "Testing
On Thu, 1 Aug 2013, Lakshminarasimhan Srinivasan wrote:
...
Description:
ldapscripts do not work from inside a "while read line" loop. The
exact same scripts were working fine until the last upgrade
Repeat-By:
Prerequisite: ldapscripts installed.
Open a new bash script and type in the f