From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-amd64+bounces-11791-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1MY0Ez-0000wo-CZ
	for garchives@archives.gentoo.org; Mon, 03 Aug 2009 16:18:25 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 7EC1CE041F;
	Mon,  3 Aug 2009 16:18:24 +0000 (UTC)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16])
	by pigeon.gentoo.org (Postfix) with ESMTP id 59779E041F
	for <gentoo-amd64@lists.gentoo.org>; Mon,  3 Aug 2009 16:18:24 +0000 (UTC)
Received: from OMTA20.westchester.pa.mail.comcast.net ([76.96.62.71])
	by QMTA01.westchester.pa.mail.comcast.net with comcast
	id Pmor1c0061YDfWL51sJR9o; Mon, 03 Aug 2009 16:18:25 +0000
Received: from ajax.firstbooks ([68.42.187.112])
	by OMTA20.westchester.pa.mail.comcast.net with comcast
	id PsLU1c0062Rw5443gsLVt0; Mon, 03 Aug 2009 16:20:29 +0000
Date: Mon, 3 Aug 2009 12:17:51 -0400
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Eselect Syntax Bug?
Message-Id: <20090803121751.ccc23314.frank.peters@comcast.net>
In-Reply-To: <87k51lt1k4.fsf@phoenix.asynchronous.org>
References: <20090803100425.e83801b8.frank.peters@comcast.net>
	<87k51lt1k4.fsf@phoenix.asynchronous.org>
X-Mailer: Sylpheed 2.7.0 (GTK+ 2.16.5; x86_64-unknown-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-amd64@lists.gentoo.org>
List-Help: <mailto:gentoo-amd64+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-amd64+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org>
X-BeenThere: gentoo-amd64@lists.gentoo.org
Reply-to: gentoo-amd64@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: c6b11735-50a8-4d8c-a277-e0c546560d41
X-Archives-Hash: 786ed759ea05634defa8d9a90453edd0

On Mon, 03 Aug 2009 10:27:39 -0400
Josh Sled <jsled@asynchronous.org> wrote:

> It works fine, here:
>=20
> jsled@phoenix [~]$ eselect --help
> Usage: eselect <global options> <module name> <module options>
>=20
> Global options:
> [=E2=80=A6works fine, no errors, &c.=E2=80=A6]


That's the question.  Why does it work on your system?

If you feel so inclined, would you save the following lines
to a text file in some directory, give the file execute permissions,
and then execute the file.  These lines encapsulate the problem with
the eselect code.


#! /bin/bash
function-one()
{
echo "FOOBAR"
}
function-one


This code fails on my system.  In fact, I booted into my old system,
a non-gentoo system, and the code also failed.  However, after booting
into a Linux rescue disk, that runs from a CD and ramdisk, the code does
not fail.  (All bash versions were 4.x.)

Although this problem is only of minor concern, it has become rather
annoying to me.

USE=3D"net -afs -bashlogger -examples -nls -plugins -vanilla"

But I also compiled with vanilla and the results are the same.

Maybe in time I can gain some more insight into this behavior but
right now I am stumped.

Frank Peters