$FG AIRCRAFT: Difference between revisions

→‎Relation between FG_AIRCRAFT/--fg-aircraft and --aircraft-dir: Improve readability and accuracy ("equivalent" has a strong meaning for me) in the Note concerning --fg-aircraft
(Bit of cleanup)
(→‎Relation between FG_AIRCRAFT/--fg-aircraft and --aircraft-dir: Improve readability and accuracy ("equivalent" has a strong meaning for me) in the Note concerning --fg-aircraft)
Line 33: Line 33:
</syntaxhighlight>
</syntaxhighlight>


is equivalent to:
is equivalent to the following command on Linux and on OS X:


<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
Line 39: Line 39:
</syntaxhighlight>
</syntaxhighlight>


on Linux and OS X, but on Windows, it is equivalent to:
On Windows, one would rather use something like this:


<syntaxhighlight lang="powershell">
<syntaxhighlight lang="powershell">
Line 45: Line 45:
</syntaxhighlight>
</syntaxhighlight>


The difference is that Windows uses a semicolon instead colon to separate the path, the paths use backslashes, and a drive letter is given.}}
The differences are that:
* Windows uses a semicolon instead of a colon to separate the paths;
* the paths use backslashes instead of forward slashes, and;
* a drive letter is given.}}


When specified, <tt>--aircraft-dir</tt> bypasses the order defined by <tt>--fg-aircraft</tt>, <tt>FG_AIRCRAFT</tt> and <tt>[[$FG_ROOT]]/Aircraft</tt>. This allows one to use an aircraft that would otherwise be shadowed by an aircraft with the same name placed earlier in the path list built from these three places (note that said order is only reliable when the &lt;path-cache&gt; in <tt>[[$FG_HOME]]/autosave_X_Y.xml</tt> is empty; “cached” entries have a higher priority than entries searched in directories from <tt>--fg-aircraft</tt>, <tt><code>$FG_AIRCRAFT</code></tt> and <tt>[[$FG_ROOT]]/Aircraft</tt>, but <tt>--aircraft-dir</tt> always “wins” if specified, even in the presence of cached entries).
When specified, <tt>--aircraft-dir</tt> bypasses the order defined by <tt>--fg-aircraft</tt>, <tt>FG_AIRCRAFT</tt> and <tt>[[$FG_ROOT]]/Aircraft</tt>. This allows one to use an aircraft that would otherwise be shadowed by an aircraft with the same name placed earlier in the path list built from these three places (note that said order is only reliable when the &lt;path-cache&gt; in <tt>[[$FG_HOME]]/autosave_X_Y.xml</tt> is empty; “cached” entries have a higher priority than entries searched in directories from <tt>--fg-aircraft</tt>, <tt><code>$FG_AIRCRAFT</code></tt> and <tt>[[$FG_ROOT]]/Aircraft</tt>, but <tt>--aircraft-dir</tt> always “wins” if specified, even in the presence of cached entries).
377

edits