</pre>
</p>
+ <p>
+ <em>Important!</em> If you use <code>--output</code> or any other argument that outputs a file, then it will be assumed you want to run Jalview in headless mode (as if you had specified <code>--headless</code>). To use Jalview with <code>--output</code> and not assume headless mode, use the <code>--gui</code> or <code>--noheadless</code> argument (the order doesn't matter).
+ </p>
+
<h3><a name="format"></a><code>--format</code></h3>
<p>
<tr valign="top"><td><code>‑‑help‑all</code></td><td>Help for all arguments</td></tr>
<tr valign="top">
- <td><code>‑‑headless</code></td>
- <td>Run Jalview in headless mode. No GUI interface will be created and Jalview will quit after all arguments have been processed.</td>
+ <td><code>‑‑headless / ‑‑noheadless</code></td>
+ <td>Run Jalview in headless (/ or not in headless) mode. In headless mode, no GUI interface will be created and Jalview will quit after all arguments have been processed.
+ <br/>
+ If you use a command line argument to specify an output file of some kind (<code>--output</code>, <code>--image</code> or <code>--structureimage</code>) then <strong>headless mode will be assumed</strong>. If you don't want this behaviour use <code>--noheadless</code> or <code>--gui</code>.
+ </td>
+ </tr>
+
+ <tr valign="top">
+ <td><code>‑‑gui</code></td>
+ <td>Force Jalview to run in graphical mode. This can be used to counter the assumption of headless mode when an argument that creates an output file is used. <code>--gui</code> takes precedence over <code>--headless</code>.</td>
</tr>
<tr valign="top">
<tr valign="top">
<td><code>‑‑news / ‑‑nonews</code></td>
- <td>Show (or don't show) the news feed.</td>
+ <td>Show (/ or don't show) the news feed.</td>
</tr>
<tr valign="top">
<td><code>‑‑splash / ‑‑nosplash</code></td>
- <td>Show (or don't show) the About Jalview splash screen.</td>
+ <td>Show (/ or don't show) the About Jalview splash screen.</td>
</tr>
<tr valign="top">
<td><code>‑‑questionnaire / ‑‑noquestionnaire</code></td>
- <td>Show (or don't show) the questionnaire if one is available.</td>
+ <td>Show (/ or don't show) the questionnaire if one is available.</td>
</tr>
<tr valign="top">
<td><code>‑‑usagestats / ‑‑nousagestats</code></td>
- <td>Send (or don't send) initial launch usage stats. <em>Note: usage stats are useful for future funding for Jalview!</em></td>
+ <td>Send (/ or don't send) initial launch usage stats. <em>Note: usage stats are useful for future funding for Jalview!</em></td>
</tr>
<tr valign="top">
<td><code>‑‑webservicediscovery / ‑‑nowebservicediscovery</code></td>
- <td>Attempt (or don't attempt) to connect to JABAWS web services.</td>
+ <td>Attempt (/ or don't attempt) to connect to JABAWS web services.</td>
</tr>
<tr valign="top">
<td>Stop all output to STDOUT (after the Java Virtual Machine has started). Use <code>‑‑quiet</code> a second time to stop all output to STDERR.</td>
</tr>
+<!--
<tr valign="top">
<td><code>‑‑initsubstitutions / ‑‑noinitsubstitutions</code></td>
<td>Set <code>‑‑substitutions</code> to be initially enabled (or initially disabled).</td>
</tr>
+-->
<!--
<tr valign="top">
<ul>
<li><a href="#introduction">Introduction</a></li>
<li><a href="#syntax">Syntax</a></li>
+ <li><a href="#headlessmode">Headless mode</a></li>
</ul>
<h2><a name="introduction"></a>Introduction</h2>
<br/>
<code>--arg file1.fa otherfile.stk</code>
<br/>
- <code>--arg filename*.fa</code> <em>(expanded by shell)</em>
+ <code>--arg filename*.fa</code> <em>(filenames expanded by shell)</em>
<br/>
- <code>--arg=filename*.fa</code> <em>(expanded by Jalview)</em>
+ <code>--arg=filename*.fa</code> <em>(filenames expanded by Jalview)</em>
</li>
<li>
For arguments that act as a switch, most can be negated by preceding the argument name with <code>no</code>.
</p>
<p>
- This may sound complicated, but nearly everything can be done just with plain command line arguments, though in this case the ordering of the arguments is more important.
+ This may sound complicated, but nearly everything can be done just with plain command line arguments (see <a href="clarguments-basic.html">Command Line: basic usage</a>), though in this case the ordering of the arguments is more important.
</p>
+
+ <h2><a name="headlessmode"></a>Headless mode</h2>
+
+ <p>
+ Jalview can be run in headless mode, i.e. without the usual graphical user interface (GUI), by specifying the <code>--headless</code> argument. With command line arguments you can specify operations for Jalview to perform on one or more files and then stop running. Most likely you will want to output another file, either an alignment for image file.
+ </p>
+ <p>
+ <strong>If you specify an argument for an output file</strong> (one or more of <code>--output</code>, <code>--image</code> or <code>--structureimage</code>) then it will be assumed that you wish to <strong>run in headless mode</strong>.
+ </p>
+ <p>
+ You can force Jalview to run in graphical mode using the <code>--gui</code> or <code>--noheadless</code> arguments.
+ </p>
+
+ <p>
+ </p>
+
+
<hr/>
Continue to <a href="clarguments-basic.html">Command Line: basic usage</a>.
<br/>
* An OUTPUTFILE Arg provides an output filename. With Opt.ALLOWALL *.ext is shorthand for
* --all --output={basename}.ext
*/
- OUTPUTFILE("value is an output file"),
+ OUTPUTFILE("output file --headless will be assumed unless --gui used"),
/*
* A STORED Arg resets and creates a new set of "opened" linkedIds
*/
git://source.jalview.org / jalview.git / commitdiff