To facilitate scripting and automation. The end user would be able to, say, launch an application from within a given environment, without first entering it.
$ be in myproject mytask --run maya
This would then run the command "maya" within "myproject" and "mytask".
Implementation
This would simply toggle the subshell into a subcommand, adding whatever is passed to --run to the end of the given startup script, and then return, as opposed to drop the user into it allowing for further commands.
End result
The end result is the ability to up-front decide upon which environment is of interest, and then decide which command to run once there. This will foremost facilitate the use of be for external launcher-type application, where the launcher can then present options, either via be or elsewhere, and then simply hand this information off to be for set-up and execution of the given command.
Goal
To facilitate scripting and automation. The end user would be able to, say, launch an application from within a given environment, without first entering it.
This would then run the command "maya" within "myproject" and "mytask".
Implementation
This would simply toggle the subshell into a subcommand, adding whatever is passed to
--runto the end of the given startup script, and then return, as opposed to drop the user into it allowing for further commands.End result
The end result is the ability to up-front decide upon which environment is of interest, and then decide which command to run once there. This will foremost facilitate the use of
befor external launcher-type application, where the launcher can then present options, either via be or elsewhere, and then simply hand this information off tobefor set-up and execution of the given command.