public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Sled <jsled@asynchronous.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Eselect Syntax Bug?
Date: Mon, 03 Aug 2009 12:46:02 -0400	[thread overview]
Message-ID: <877hxku9px.fsf@phoenix.asynchronous.org> (raw)
In-Reply-To: <20090803121751.ccc23314.frank.peters@comcast.net> (Frank Peters's message of "Mon\, 3 Aug 2009 12\:17\:51 -0400")

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Frank Peters <frank.peters@comcast.net> writes:
> 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.

Runs fine here.  :(

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

'vanilla' is the one that jumped out at me, too.

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

Very strange, indeed.  I mean, the bash man page is very clear on the
grammar for 'name' (the token-class in question), and it does not admit
'-'.  Maybe see if there's a bash bug or FAQ from that angle?  Plus,
report the bad syntax to the eselect devs, of course.  Even if it works,
it only works accidentally, and is bad form.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2009-08-03 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 14:04 [gentoo-amd64] Eselect Syntax Bug? Frank Peters
2009-08-03 14:27 ` Josh Sled
2009-08-03 16:17   ` Frank Peters
2009-08-03 16:37     ` Frank Peters
2009-08-03 16:46     ` Josh Sled [this message]

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=877hxku9px.fsf@phoenix.asynchronous.org \
    --to=jsled@asynchronous.org \
    --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