<mapID target="commandline" url="html/features/commandline.html"/>
<mapID target="jalviewcltool" url="html/features/commandline.html#script"/>
<mapID target="clarguments" url="html/features/clarguments.html"/>
+ <mapID target="clarguments-intro" url="html/features/clarguments-intro.html"/>
+ <mapID target="clarguments-basic" url="html/features/clarguments-basic.html"/>
+ <mapID target="clarguments-advanced" url="html/features/clarguments-advanced.html"/>
+ <mapID target="clarguments-argfiles" url="html/features/clarguments-argfiles.html"/>
<mapID target="jvlfiles" url="html/features/jvlfiles.html"/>
<mapID target="io" url="html/io/index.html"/>
<mapID target="io.modellerpir" url="html/io/modellerpir.html"/>
<tocitem text="Groovy Features Counter example" target="groovy.featurescounter"/>
</tocitem>
<tocitem text="Command Line" target="commandline" expand="false">
- <tocitem text="Command Line Arguments: summary" target="clarguments" />
- <tocitem text="Command Line Arguments: introduction" target="clarguments-intro" />
- <tocitem text="Command Line Arguments: basic usage" target="clarguments-basic" />
- <tocitem text="Command Line Arguments: advanced usage" target="clarguments-advanced" />
- <tocitem text="Command Line Arguments: argfiles" target="clarguments-argfiles" />
+ <tocitem text="Command Line: summary" target="clarguments" />
+ <tocitem text="Command Line: introduction" target="clarguments-intro" />
+ <tocitem text="Command Line: basic usage" target="clarguments-basic" />
+ <tocitem text="Command Line: advanced usage" target="clarguments-advanced" />
+ <tocitem text="Command Line: argument files" target="clarguments-argfiles" />
</tocitem>
<tocitem text="Memory Settings" target="memory" expand="false"/>
<tocitem text="Jalview Launch Files" target="jvlfiles" expand="false"/>
* along with Jalview. If not, see <http://www.gnu.org/licenses/>.
* The Jalview Authors are detailed in the 'AUTHORS' file.
-->
-<title>Jalview Command Line Arguments: advanced usage</title>
+<title>Command Line: advanced usage</title>
<body>
- <h1>Jalview Command Line Arguments: advanced usage</h1>
+ <h1>Command Line: advanced usage</h1>
<p>
- <a href="clarguments.html">Jalview Command Line Arguments: summary</a>
+ <a href="clarguments.html">Command Line: summary</a>
<br/>
- <a href="clarguments-intro.html">Jalview Command Line Arguments: introduction</a>
+ <a href="clarguments-intro.html">Command Line: introduction</a>
<br/>
- <a href="clarguments-basic.html">Jalview Command Line Arguments: basic usage</a>
+ <a href="clarguments-basic.html">Command Line: basic usage</a>
<br/>
- Jalview Command Line Arguments: advanced usage
+ Command Line: advanced usage
<br/>
- <a href="clarguments-argfiles.html">Jalview Command Line Arguments: argfiles</a>
+ <a href="clarguments-argfiles.html">Command Line: argument files</a>
</p>
<hr/>
<ul>
<li><a href="#alignmentlinkedids">Alignment linked IDs</a></li>
- <li><a href="#moresubtitutions">More substitutions</a></li>
+ <li><a href="#moresubstitutions">More substitutions</a></li>
<li><a href="#equalsseparatorandfileglobs">Equals separator and file globs</a></li>
+ <li><a href="#subvaluemodifiers">Sub-value modifiers</a></li>
</ul>
<h2><a name="alignmentlinkedids"></a>Alignment linked IDs</h2>
<p>
- Jalview's alignment related arguments are linked together using a <em>linked ID</em>. In all of the basic usage examples this linked ID is assigned using a default formula of <code>JALVIEW:<em>n</em></code> where <em>n</em> starts at 0 and increments every time there is an <code>--open</code>ed file (or a first use of <code>--append</code>) or the <code>--new</code>argument is used.
+ Jalview's alignment related arguments are linked together using a <em>linked ID</em>. In all of the basic usage examples this linked ID is assigned using a default formula of <code>JALVIEW:<em>n</em></code> where <em>n</em> starts at 0 and increments every time there is an <code>--open</code>ed file (or a first use of <code>--append</code>) or the <code>--new</code> argument is used.
</p>
<p>
- When another alignment related argument is used, it is assigned the same linked ID. When the <code>--all</code> argument is used, following alignment related arguments are applied to all linked IDs (made so far).
+ When another alignment related argument is used (without a specified linked ID), it is assigned this default linked ID. When the <code>--all</code> argument is used, following alignment related arguments are applied to all of the linked IDs (made so far).
</p>
<p>
- You can assign your own linked IDs to alignments that are opened from the command-line. To do this put the linked ID in square brackets ('[', ']') <em>immediately following the argument (i.e. before any space or equals sign) like this:
+ You can assign your own linked IDs to alignments that are opened from the command-line. To do this put the linked ID in square brackets ('[', ']') <em>immediately following the argument</em> (i.e. before any space or equals sign) like this:
<pre>
jalview --open[myId1] file1.fa --open[myId2] file2.fa --open[myId3] file3.fa --colour[myId1] gecos-flower --colour[myId2] gecos-blossom --colour[myId3] zappo --image "*.png" --headless
</pre>
+
+ <p>
+ As you can see, if you specify your own linked IDs, the arguments for one alignment do not need to be adjacent as they are when using the default assigned linked ID.
</p>
<p>
- As you can see the arguments for one alignment do not need to be adjacent as they are when using the default assigned linked ID.
+ A specified linked ID will also take precedence over a wildcard or <code>--all</code> set linked ID. e.g.
+ <pre>
+ jalview --open[myID] examples/uniref50.fa --all --colour taylor --colour[myID] gecos-blossom
+ </pre>
+ will open the alignment using the <code>gecos-blossom</code> colour scheme (thank goodness).
</p>
- <h2><a name="moresubstitutions"></a>More substitutions</h2>
+ <h2><a name="moresubstitutions"></a>More substitutions (<code>{n}</code>, <code>{++n}</code>, <code>[*]</code>)</h2>
<p>
- In the <a href="clarguments-basic.html#substutions">basic usage document</a> we have a list of special strings that get replaced in output filename values with parts of input filename values.
+ In the <a href="clarguments-basic.html#substitutions">basic usage document</a> we have a list of special strings that get replaced in output filename values with parts of input filename values.
</p>
<p>
- There is also an incrementor integer value <code>{n}</code> that can be put into both linked IDs and filenames and works across different linked IDs. Whenever you use <code>{n}</code> in a linked ID or filename value it is replaced with the current value of <em>n</em>. The initial value is 0, and it can be incremented by using the argument <code>--npp</code> or <code>--n++</code>, or using a another substitution <code>{++n}</code> in either a linked ID or filename value which increments the value and is replaced with the new incremented value of <em>n</em>.
+ There is also an incrementor integer value <code>{n}</code> that can be put into both linked IDs and filenames and works across different linked IDs. Whenever you use <code>{n}</code> in a linked ID or filename value it is replaced with the current value of <em>n</em>. The initial value is 0, and it can be incremented by using the argument <code>--npp</code> or <code>--n++</code>, or using a another special substitution <code>{++n}</code> in either a linked ID or filename value which increments the value and is replaced with the new incremented value of <em>n</em>.
</p>
<p>
- In the same way that the <code>--all</code> argument enables (some) following arguments to apply to all opened alignments so far, the special linked ID <code>{*}</code> will also apply an individual argument to all opened linked IDs.
+ In the same way that the <code>--all</code> argument enables (some) following arguments to apply to all opened alignments so far, the special linked ID <code>*</code> will also apply an individual argument to all opened linked IDs (in fact when you use the <code>--all</code> argument it simply changes the default linked ID to <code>*</code>).
<pre>
- jalview --open[myId1] fileA.fa --open[myId2] fileB.fa --open[myId3] fileC.fa --colour[{*}] taylor --all --image tmp/image-{++n}.png --headless
+ jalview --open[myId1] fileA.fa --open[myId2] fileB.fa --open[myId3] fileC.fa --colour[*] taylor --all --image tmp/image-{++n}.png --headless
</pre>
The above will produce an image <code>image-0.png</code> for the alignment in <code>fileA.fa</code>, an image <code>image-1.png</code> for the alignment in <code>fileB.fa</code>, etc.
+ If you suddenly decide to colour the last alignment differently you could add to the command:
+ <pre>
+ jalview --open[myId1] fileA.fa --open[myId2] fileB.fa --open[myId3] fileC.fa --colour[*] taylor --all --image tmp/image-{++n}.png --headless --colour[myId3] gecos-blossom
+ </pre>
+ because all of the command line arguments are read and sorted into their linked IDs before starting to be processed, and the <code>[myId3]</code> specified linked ID takes precedence over the <code>[*]</code> wildcard linked ID.
+ </p>
</p>
- <h2><a name="equalsseparatorandfileglobs"></a>Equals separator and file globs</h2>
+ <h2><a name="equalsseparatorandfileglobs"></a>Equals separator and Java file globs</h2>
<p>
- When a Jalview command-line argument requires one (or more) values, you can use the usual space separation, which allows the shell to expand any filename "globs" (or wildcards representing multiple files). To Jalview this appears like a list of filenames supplied to the argument.
+ When a Command-line argument requires one (or more) values, you can use the usual space separation, which allows the shell to expand any file "globs" (that is, filenames with wildcard characters allowing it to represent multiple files). The shell "expands" this file glob and to Jalview it appears like a list of filenames supplied to the argument.
</p>
<p>
- There is a limitation to shell expansion of file globs, as the length of a single command is limited (to different amounts depending on your shell and its configuration).
+ There is a limitation to shell expansion of file globs, as the length of a single command, or number of files the shell is willing to expand a file glob to, is limited (to different amounts depending on your shell and its configuration).
</p>
<p>
</p>
<p>
- Another benefit is that the <em>input</em> filename
+ A bigger benefit is that the <em>input</em> filename is not expanded by the shell but can instead be expanded by Jalview. There is no limit to the number of files that this kind of file glob can match since it is expanded by Jalview, not the shell.
+ </p>
+
+ <p>
+ Jalview uses the Java PathMatcher "glob" scheme to match filenames, which is quite similar, though in some ways more powerful, to most shell glob rules. The usual '<code>*</code>' and '<code>?</code>' characters act the same, but other combinations can be used too. For the full rules see <a href="https://devdocs.io/openjdk~11/java.base/java/nio/file/filesystem#getPathMatcher(java.lang.String)">java.nio.file.PathMatcher.getPathMatcher</a> javadocs at https://devdocs.io/openjdk~11/java.base/java/nio/file/filesystem#getPathMatcher(java.lang.String).
+ </p>
+
+ <p>
+ One such PathMatcher addition to shell file globs is the use of <code>**</code> to match any number of directories and sub-directories (matching across file separator). So to convert every Fasta file under the current working directory to BLC format you can do:
+ <pre>
+ jalview --open=./**/*.fa --output=*.blc --close --headless
+ </pre>
+ or to find every Stockholm and Pfam file under </code>/tmp</code> and convert to Fasta and save in your own folder, do
+ <pre>
+ jalview --open=/tmp/**/*.{stk,pfam} --all --output=~/rescued/{basenamedir}.fa --close --headless
+ </pre>
+ </p>
+
+ <h2><a name="subvaluemodifiers"></a>Sub-value modifiers</h2>
+ <p>
+ Sub-value modifiers are given in square brackets ('[', ']') <em>immediately before the value</em> (i.e. after any space or equals sign, and with no space between it and the value) like this:
+ <pre>
+ jalview --open=examples/uniref50.fa --image=[scale=1.414]picture.png
+ </pre>
+ </p>
+
+ <p>
+ Some arguments (such as <code>--scale=<em>n</em></code>) are used to modify the behaviour of other "primary" arguments (such as <code>--image=filename</code>). These arguments can alternatively be specifed as <em>sub-value modifiers</em> of the values given to the primary argument. If specified as a sub-value modifier, this modifier takes precedence over any following linked argument if given. e.g
+ <pre>
+ jalview --open=[colour=zappo]examples/*.fa
+ </pre>
+ Notice also that if a sub-value modifier is used for a value that is expanded by the application (i.e. using an equals sign ('=') to separate argument and value) then that modifier is applied to all of the values.
+ </p>
+
+ <p>
+ For shell expanded globs this is more problematic since the presence of a sub-value modifier will almost certainly prevent the shell from recognising the file glob, so
+ <pre>
+ jalview --open [colour=zappo]examples/*.fa
+ </pre>
+ will <em>NOT</em> work the same as above. If you need to use sub-value modifiers on a file glob you should use an equals sign ('=') to separate it from the argument.
+ </p>
+
+ <p>
+ You can specify multiple sub-value modifiers separating them with a comma (','). If you wish to specify a "boolean" argument, such as <code>--wrap</code> or <code>--nowrap</code> then simply use the argument name without a value, like this:
+ <pre>
+ jalview --open=[colour=gecos-flower,wrap,noannotations,features=examples/plantfdx.features]examples/plantfdx.fa
+ </pre>
</p>
<hr/>
- Continue to <a href="clarguments-argfiles.html">Jalview Command Line Arguments: argfiles</a>.
+ Continue to <a href="clarguments-argfiles.html">Command Line: argument files</a>.
<br/>
- Return to <a href="clarguments.html">Jalview Command Line Arguments: summary</a>.
+ Return to <a href="clarguments.html">Command Line: summary</a>.
</body>
* along with Jalview. If not, see <http://www.gnu.org/licenses/>.
* The Jalview Authors are detailed in the 'AUTHORS' file.
-->
-<title>Jalview Command Line Arguments: argfiles</title>
+<title>Command Line: argument files</title>
<body>
- <h1>Jalview Command Line Arguments: argfiles</h1>
+ <h1>Command Line: argument files</h1>
<p>
- <a href="clarguments.html">Jalview Command Line Arguments: summary</a>
+ <a href="clarguments.html">Command Line: summary</a>
<br/>
- <a href="clarguments-intro.html">Jalview Command Line Arguments: introduction</a>
+ <a href="clarguments-intro.html">Command Line: introduction</a>
<br/>
- <a href="clarguments-basic.html">Jalview Command Line Arguments: basic usage</a>
+ <a href="clarguments-basic.html">Command Line: basic usage</a>
<br/>
- <a href="clarguments-advanced.html">Jalview Command Line Arguments: advanced usage</a>
+ <a href="clarguments-advanced.html">Command Line: advanced usage</a>
<br/>
- Jalview Command Line Arguments: argfiles
+ Command Line: argument files
</p>
<hr/>
+ <ul>
+ <li><a href="#argumentfiles">Argument files</a></li>
+ <li><a href="#onlyargumentfiles">Only argument files</a></li>
+ <li><a href="#evenmoresubstitutions">Even more substitutions</a></li>
+ </ul>
+ <h2><a name="argumentfiles"></a>Argument files</h2>
+ <p>
+ If you want to save a set of arguments to reuse, you can save them in a text file, say <code>argfile.txt</code>, and read them into Jalview with
+ <pre>
+ jalview --argfile=argfile.txt
+ </pre>
+ </p>
+
+ <p>
+ The argument file has one argument and value per line, still using the double-dash ('--') before the argument name, and separating the argument and value with an equals sign ('=').
+ <br/>
+ Because the argument file is read by the application and not read by the shell, you do not need to escape any values -- all spaces will be read as part of the value until the end of the line.
+ <br/>
+ You can add comments to a line by starting the line with an octothorpe (hash, pound-sign '#').
+ <br/>
+ e.g.
+ <table border="1">
+ <tr>
+ <td>
+ File <code>argfile.txt</code>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <pre>
+--nonews
+--nosplash
+--open=[nowrap,colour=gecos-flower,showannotations]examples/plantfdx.fa
+--features=examples/plantfdx.features
+--annotations=examples/plantfdx.annotations
+--image=images/alignment.png
+--scale=2.5
+#--scale=10
+# let's see what's happening
+#--headless</pre>
+ </td>
+ </tr>
+ </table>
+ </p>
+ <p>
+ Because <code>--argfiles</code> takes a filename argument, and multiple <code>--argfiles</code> can be read on the command line, you can also use file globs to specify multiple <code>--argfile</code> values. If you produce an argument file for each set of alignment files that you wish to associate then you can act on all of them with, e.g.
+ <pre>
+ jalview --argfile=*/argfile.txt --headless
+ </pre>
+ </p>
+
+ <p>
+ You can even read argument files from within argument files, e.g.
+ <pre>
+ jalview --argfile=argfile*.txt --headless
+ </pre>
+ <table border="1">
+ <tr><td>File <code>argfile1.txt</code></td></tr>
+ <tr><td><pre>
+--open=file1.fa
+--argfile=myfavouriteformattingargfile.txt
+--argfile=mysecondfavouriteimageargfile.txt</pre></td></tr>
+ <tr><td>File <code>myfavouriteformattingargfile.txt</code></td></tr>
+ <tr><td><pre>
+--wrap
+--showannotations
+--annotations={dirname}/{basename}.annots</pre></td></tr>
+ <tr><td>File <code>mysecondfavouriteimageargfile.txt</code></td></tr>
+ <tr><td><pre>
+--image=images/{basename}.png
+--width=1920
+--height=1080</pre></td></tr>
+ </table>
+ </p>
+
+ <p>
+ If a "loop" of argument files is detected then Jalview will refuse to play (which is a Good Thing).
+ </p>
+ <h2><a name="onlyargumentfiles"></a>Only argument files</h2>
+
+ <p>
+ When you use an <code>--argfile</code> argument, all other non-initialising arguments on the command line <em>will be ignored</em>. Only the initialising arguments and any and all <code>--argfiles</code> arguments on the command line will be used. You can also set initialising arguments in argument files.
+ </p>
+
+
+ <h2><a name="evenmoresubstitutions"></a>Even more substitutions</h2>
+
+ <p>
+ When adding values that can use substitutions within argument files, there are two additional substitutions that are made:
+ <br/>
+ <code>{argfilebasename}</code> - replaced with the base of the filename of the argument file (i.e. without directory path or file extension).
+ <br/>
+ <code>{argfiledirname}</code> - replaced with the path to the filename of the argument file.
+ </p>
+
+ <p>
+ Another amusing substitution you can make in argument files is the <code>{n}</code> substitution, combined with an <code>-npp</code> increment at the start (or end) of the argument file, which gives the potential of having multiple argument files with the exact same content, or even re-using the same argument file multiple times. e.g.
+
+ <table border="1">
+ <tr><td>File <code>alignment.argfile</code></td></tr>
+ <tr><td><pre>
+--open={argfilebasename}-{n}.fa
+--wrap
+--output={basename}.stk
+--close
+--npp</pre></td></tr>
+ </table>
+ <pre>
+ jalview --argfile alignment.argfile --argfile alignment.argfile --headless
+ </pre>
+ would be processed like
+ <pre>
+ jalview --open=alignment-0.fa --wrap --output=alignment-0.stk --close --open=alignment-1.fa --wrap --output=alignment-1.stk --close --headless
+ </pre>
+ </p>
+
<hr/>
- Return to <a href="clarguments.html">Jalview Command Line Arguments: summary</a>.
+ Return to <a href="clarguments.html">Command Line: summary</a>.
</body>
* along with Jalview. If not, see <http://www.gnu.org/licenses/>.
* The Jalview Authors are detailed in the 'AUTHORS' file.
-->
-<title>Jalview Command Line Arguments: basic usage</title>
+<title>Command Line: basic usage</title>
<body>
- <h1>Jalview Command Line Arguments: basic usage</h1>
+ <h1>Command Line: basic usage</h1>
<p>
- <a href="clarguments.html">Jalview Command Line Arguments: summary</a>
+ <a href="clarguments.html">Command Line: summary</a>
<br/>
- <a href="clarguments-intro.html">Jalview Command Line Arguments: introduction</a>
+ <a href="clarguments-intro.html">Command Line: introduction</a>
<br/>
- Jalview Command Line Arguments: basic usage
+ Command Line: basic usage
<br/>
- <a href="clarguments-advanced.html">Jalview Command Line Arguments: advanced usage</a>
+ <a href="clarguments-advanced.html">Command Line: advanced usage</a>
<br/>
- <a href="clarguments-argfiles.html">Jalview Command Line Arguments: argfiles</a>
+ <a href="clarguments-argfiles.html">Command Line: argument files</a>
</p>
<hr/>
<h3><a name="all"></a><code>--all / -noall</code></h3>
<p>
- When using the <code>--all</code> argument, following arguments will apply to all of the previously opened alignment windows. You can turn this behaviour off for following arguments using the <code>--noall</code> argument. The arguments that can apply to all previously opened alignments are:
+ When using the <code>--all</code> argument, following arguments will apply to all of the previously opened alignment windows. You can turn this behaviour off again for following arguments using the <code>--noall</code> argument. The arguments that can apply to all previously opened alignments are:
<br/>
<code>--colour</code>
<br/>
<h2><a name="alloutputwildcard"></a>The all output wildcard: <code>--output "*.ext"</code>, <code>--image "*.ext"</code></h2>
<p>
- Purely as an intuitive syntactic sweetener, you can use the <code>--output</code> wildcard <code>*</code> <em>at the beginning of the output filename</em> as shorthand for <code>--all --output {dirname}/{basename}</code> followed by whatever you put after the <code>*</code>. For example, to achieve the same as the thumbnails example above, you could use
+ Purely as an intuitive syntactic sweetener, you can use the <code>--output</code> wildcard <code>*</code> <em>at the beginning of the output filename</em> as shorthand for <code>--all --output {dirname}/{basename}</code> followed by whatever you put after the '<code>*</code>'. For example, to achieve the same as the thumbnails example above, you could use
<pre>
jalview --open */*.fa --image "*.png" --colour gecos-flower --width 256 --height 256 --close --headless
</pre>
</p>
<p>
- <strong>Important!</strong> Please note that using a bareword <code>*.ext</code> (i.e. without an escape or quotation marks) in a shell command line will potentially be expanded by the shell to a list of all the files in the current directory ending with <code>.ext</code> <em>before</em> this value is passed to Jalview. This will result in the first of these files being overwritten (multiple times)! If you shell-escape the <code>*</code> (usually with a backslash '\') or enclose the value in quotation marks ('"*.ext"') then the shell will not expand the wildcard.
+ <strong>Important!</strong> Please note that using a bareword <code>*.ext</code> (i.e. without an escape or quotation marks) in a shell command line will potentially be expanded by the shell to a list of all the files in the current directory ending with <code>.ext</code> <em>before</em> this value is passed to Jalview. This will result in the first of these files being overwritten (multiple times)! If you shell-escape the <code>*</code> (usually with a backslash '\') or enclose the value in quotation marks (<code>"*.ext"</code> - that's including the quotation marks) then the shell will not expand the wildcard.
</p>
<p>
</p>
<hr/>
- Continue to <a href="clarguments-advanced.html">Jalview Command Line Arguments: advanced usage</a>.
+ Continue to <a href="clarguments-advanced.html">Command Line: advanced usage</a>.
<br/>
- Return to <a href="clarguments.html">Jalview Command Line Arguments: summary</a>.
+ Return to <a href="clarguments.html">Command Line: summary</a>.
</body>
* along with Jalview. If not, see <http://www.gnu.org/licenses/>.
* The Jalview Authors are detailed in the 'AUTHORS' file.
-->
-<title>Jalview Command Line Arguments: introduction</title>
+<title>Command Line: introduction</title>
<body>
- <h1>Jalview Command Line Arguments: introduction</h1>
+ <h1>Command Line: introduction</h1>
<p>
- <a href="clarguments.html">Jalview Command Line Arguments: summary</a>
+ <a href="clarguments.html">Command Line: summary</a>
<br/>
- Jalview Command Line Arguments: introduction
+ Command Line: introduction
<br/>
- <a href="clarguments-basic.html">Jalview Command Line Arguments: basic usage</a>
+ <a href="clarguments-basic.html">Command Line: basic usage</a>
<br/>
- <a href="clarguments-advanced.html">Jalview Command Line Arguments: advanced usage</a>
+ <a href="clarguments-advanced.html">Command Line: advanced usage</a>
<br/>
- <a href="clarguments-argfiles.html">Jalview Command Line Arguments: argfiles</a>
+ <a href="clarguments-argfiles.html">Command Line: argument files</a>
</p>
<hr/>
</p>
<hr/>
- Continue to <a href="clarguments-basic.html">Jalview Command Line Arguments: basic usage</a>.
+ Continue to <a href="clarguments-basic.html">Command Line: basic usage</a>.
<br/>
- Return to <a href="clarguments.html">Jalview Command Line Arguments: summary</a>.
+ Return to <a href="clarguments.html">Command Line: summary</a>.
</body>
* along with Jalview. If not, see <http://www.gnu.org/licenses/>.
* The Jalview Authors are detailed in the 'AUTHORS' file.
-->
-<title>Jalview Command Line Arguments: summary</title>
+<title>Command Line: summary</title>
<body>
- <h1>Jalview Command Line Arguments: summary</h1>
+ <h1>Command Line: summary</h1>
<p>
- Jalview Command Line Arguments: summary
+ Command Line: summary
<br/>
- <a href="clarguments-intro.html">Jalview Command Line Arguments: introduction</a>
+ <a href="clarguments-intro.html">Command Line: introduction</a>
<br/>
- <a href="clarguments-basic.html">Jalview Command Line Arguments: basic usage</a>
+ <a href="clarguments-basic.html">Command Line: basic usage</a>
<br/>
- <a href="clarguments-advanced.html">Jalview Command Line Arguments: advanced usage</a>
+ <a href="clarguments-advanced.html">Command Line: advanced usage</a>
<br/>
- <a href="clarguments-argfiles.html">Jalview Command Line Arguments: argfiles</a>
+ <a href="clarguments-argfiles.html">Command Line: argument files</a>
</p>
<hr/>
git://source.jalview.org / jalview.git / commitdiff