[forge-issues] [JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

[George Gastaldi (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi reopened FORGE-1622:
------------------------------------



> It would be good if Aesh had access to export variables
> -------------------------------------------------------
>
>                 Key: FORGE-1622
>                 URL: https://issues.jboss.org/browse/FORGE-1622
>             Project: Forge
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: UI - Shell
>    Affects Versions: 2.1.1.Final
>            Reporter: Antonio Goncalves
>            Assignee: Daniel Cunha
>            Priority: Minor
>             Fix For: 2.7.0.Final
>
>
> This would be a "nice to have" feature from the shell command line. 
> I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : 
> {code}
> ~$ cd $CODE_HOME          // Under OS X
> ~/Documents/Code$ forge   // Entering Forge
>     _____
>    |  ___|__  _ __ __ _  ___
>    | |_ / _ \| `__/ _` |/ _ \  \\
>    |  _| (_) | | | (_| |  __/  //
>    |_|  \___/|_|  \__, |\___|
>                    |___/
> JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc.
> [Code]$ cd ~
> [antoniombp]$ cd $CODE_HOME    //  Good if it goes to the right directory
> [antoniombp]$ echo $CODE_HOME  // Doesn't have access to the exported variable
> [antoniombp]$
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)