You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2008/01/31 02:41:34 UTC

[jira] Closed: (GSHELL-13) Implement command search path

     [ https://issues.apache.org/jira/browse/GSHELL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon closed GSHELL-13.
------------------------------

    Resolution: Fixed

Yay... this is a good first step.  I think we might want to decide on some naming things for variables used by gshell.  Like I'm thinking instead of {{path}} this should be {{gshell.path}}.

Also, we need to fix how {{/}}, {{./}} and {{../}} are handled.  Cause this is a bit weird to me:

{noformat}
set path=/:vfs
{noformat}

IMO, should be:

{noformat}
set path=/:/vfs
{noformat}

And finally, we really need more tests for this stuff... like what happens when 2 paths have the same command name?  Does the command found in the path before the other really get used?...

Yatta!

> Implement command search path
> -----------------------------
>
>                 Key: GSHELL-13
>                 URL: https://issues.apache.org/jira/browse/GSHELL-13
>             Project: GShell
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Core
>    Affects Versions: 0.0.1
>            Reporter: Jason Dillon
>            Assignee: Jason Dillon
>             Fix For: 1.0-alpha-2
>
>         Attachments: GShell-13.patch
>
>
> Command search path.
>  * ~/.gshell/
>  * profile.gsh
>  * settings.gsh?  settings.properties?  settings.xml?

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