Apologies. My feature request evolved while I was typing it, and I forgot to delete the first paragraph! My initial though was to add a parameter to the ExecuteCommandLineOperation, before the idea of os_eval
came along. However, as long as we're talking about OS shell integration points...
One thing my colleagues mentioned is what would be ideal is if we could indicate which shell to use in a number of customization opportunities in Oxygen. On Windows, the options for us are the legacy cmd shell, PowerShell, and GitBash, although we only care about CMD and Bash. GitBash does have the ability to invoke it with a command line parameter to provide the Bash command to execute.
For an os_eval
implementation, perhaps there could be a preference for the default command shell, but also supporting an optional parameter to indicate the shell to use.
A bit more ambitious feature would be something I've mentioned in another forum post or perhaps a support email. It would be wonderful if we could:
- pick which shell to use in the External Tools dialog. The console display would show the output from a given shell.
- provide a true console that supports interactive input as well as output. Many text editors and IDEs provide that feature, and it precludes a user having to leave the OxygenXML UX to get something done in a separate terminal application.
There appear to be a few related terminal open source Java plugins for Eclipse, such as:
which support multiple shell types.