Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <4668018.1196304283573.JavaMail.jira@brutus>
Date: Wed, 28 Nov 2007 18:44:43 -0800 (PST)
From: "Jason Warner (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GSHELL-20) `set foo="bar"` does not work as
 expected
In-Reply-To: <30763177.1151279071040.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546543 ] 

Jason Warner commented on GSHELL-20:
------------------------------------

That is actually somewhat expected behavior.  I didn't realize that single quotes should be parsed the same as double quotes.  Should double and single quotes be working in the same manner?  I was working on the jira in a literal sense.  Was there more outside of what was described that was in the scope of the jira?

> `set foo="bar"` does not work as expected
> -----------------------------------------
>
>                 Key: GSHELL-20
>                 URL: https://issues.apache.org/jira/browse/GSHELL-20
>             Project: GShell
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Commands, Core
>    Affects Versions: 0.0.1
>            Reporter: Jason Dillon
>            Assignee: Jason Warner
>            Priority: Critical
>             Fix For: 1.0-alpha-2
>
>         Attachments: GShell-20.patch
>
>
> Due to the way parsing happens, this line:
> {noformat}
> set foo="bar"
> {noformat}
> Ends up calling the command with 2 arguments: "foo=" and "bar", which is not what the command expects, which is one argument of: "foo=bar"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.