[
https://issues.apache.org/jira/browse/GSHELL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Warner updated GSHELL-13:
-------------------------------
Attachment: GShell-13.patch
This implements the beginnings of command path search. An environment variable
"path" can be set so that commands can be used without fully qualifying the
path every time (i.e, script instead of bsf/script). An issue I came across is
that the "set" command doesn't like when you try to add to the path via
path=$path:bsf. This causes an error and the path isn't set properly.
Can gshell load environmental variables from a .profile type file, yet? Having
a persistent path based on such a file would be neat. If it doesn't exist, I
might just have to look into it.
As a side note, I made the command path work such that you can always access
the builtins in case someone accidentally mucks up their path. I did that
during testing and none of the commands could be found, including quit (ctrl +
c to the rescue!).
> 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 Warner
> 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.
