public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Python-updater line 415 error
Date: Mon, 3 Aug 2009 02:16:39 -0400	[thread overview]
Message-ID: <20090803021639.3e16463d.frank.peters@comcast.net> (raw)
In-Reply-To: <1249279663.5149.14.camel@localhost>

On Mon, 03 Aug 2009 01:07:43 -0500
Lance Lassetter <lancelassetter@gmail.com> wrote:

> On Mon, 2009-08-03 at 01:59 -0400, Frank Peters wrote:
> > cd /etc && FOO="$(cat < $(ls -a /etc | grep mtab))" && echo $FOO
> 
> Frank,
> 
> The 1st didn't, the second did:
> 
> The 1st:
> 
> # cd /etc && FOO="$(cat < <(ls -a /etc | grep mtab))" && echo $FOO
> dmtab mtab
> 
> 
> The 2nd:
> 
> # cd /etc && FOO="$(cat < $(ls -a /etc | grep mtab))" && echo $FOO
> -su: $(ls -a /etc | grep mtab): ambiguous redirect
> 

Thanks.  There is something funny going on, because the first produces
an error on my system while the second does not.  The first form of the
command is what has been in python-updater.

What version of bash do you have?  Just do:

bash --version

It has to be a bash issue.

Frank Peters




  reply	other threads:[~2009-08-03  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03  4:36 [gentoo-amd64] Python-updater line 415 error Frank Peters
2009-08-03  4:42 ` Lance Lassetter
2009-08-03  5:59   ` Frank Peters
2009-08-03  6:07     ` Lance Lassetter
2009-08-03  6:16       ` Frank Peters [this message]
2009-08-03  6:21         ` Lance Lassetter
2009-08-03  6:28           ` Frank Peters
2009-08-03  6:44             ` Lance Lassetter
2009-08-03 12:31               ` Frank Peters
2009-08-03  7:12             ` [gentoo-amd64] " Duncan
2009-08-03  8:04               ` Lance Lassetter
2009-08-03 12:55               ` [gentoo-amd64] Re: Python-updater line 415 error [Solved] Frank Peters
2009-08-04 15:40                 ` Lance Lassetter
2009-08-04 16:29                   ` Frank Peters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090803021639.3e16463d.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox