[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: |
Dan Douglas |
Subject: |
Re: [Help-bash] Quoting in variables to be used as command args |
Date: |
Tue, 05 Jun 2012 13:54:21 -0500 |
User-agent: |
KMail/4.8.3 (Linux/3.4.1-pf+; KDE/4.8.3; x86_64; ; ) |
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
> 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.
--
Dan Douglas