[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-bash] Quoting in variables to be used as command args
From: |
suvayu ali |
Subject: |
Re: [Help-bash] Quoting in variables to be used as command args |
Date: |
Wed, 6 Jun 2012 10:23:27 +0200 |
Hi Dan,
On Tue, Jun 5, 2012 at 8:54 PM, Dan Douglas <address@hidden> wrote:
> On Tuesday, June 05, 2012 08:36:22 PM suvayu ali wrote:
>> A few questions, I don't understand the use of two '<' characters. Why
>> is one input redirection not enough?
>
> The first < is the redirect. <(cmds) is a substitution expanding to a
> filename.
> The space prevents ambiguity with herestring or heredoc redirects.
>
> http://wiki.bash-hackers.org/syntax/expansion/proc_subst
>
Thanks for clarifying this. Although I have used the <(..) syntax
before, I realise now that I didn't understand the mechanism at all.
>> Why are the escaped parentheses
>> around findopts required? Just using "address@hidden" seems to work in
>> my script.
>
> Parentheses are metacharacters and need escaping or quoting to pass as
> arguments to find. There they act as grouping operators which I suppose might
> be necessary depending on the contents of findopts.
Thanks, I read this in the find man page after my last message. :-p
> --
> Dan Douglas
Thanks a lot to both of you, I learned a lot. :)
Cheers,
--
Suvayu
Open source is the future. It sets us free.