Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.11.0
-
Fix Version/s: None
-
Component/s: Command Line Interface
-
Labels:None
Description
When running Jalview in headless mode, using the new documented launcher binaries and passing command line arguments, the getdown splashscreen still appears.
Can a headless mode be detected before viewing the getdown splashscreen and avoid showing it?
Should a different command line be recommended for running jalview headlessly? (possibly)
When a headless command produces an output file, the default PWD for Jalview is the getdown app dir (e.g. by default /Applications/Jalview.app/Content/Resources/app/ on a mac, or %LOCALAPPDATA%\Jalview on Windows, or ~/opt/Jalview in unix/linux), no matter which directory the user's shell is in when launching Jalview.
Can the PWD be changed to the user's shell PWD? Or better documentation for users so that they use full-path output filename or know where to look (perhaps a STDOUT message of "File test.png written to .../Jalview" [see the "getdownappdir" property passed in by getdown]).
Can a headless mode be detected before viewing the getdown splashscreen and avoid showing it?
Should a different command line be recommended for running jalview headlessly? (possibly)
When a headless command produces an output file, the default PWD for Jalview is the getdown app dir (e.g. by default /Applications/Jalview.app/Content/Resources/app/ on a mac, or %LOCALAPPDATA%\Jalview on Windows, or ~/opt/Jalview in unix/linux), no matter which directory the user's shell is in when launching Jalview.
Can the PWD be changed to the user's shell PWD? Or better documentation for users so that they use full-path output filename or know where to look (perhaps a STDOUT message of "File test.png written to .../Jalview" [see the "getdownappdir" property passed in by getdown]).