You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<tdclass="cmdhintcell">Open file in the <ahref="viewer.html">viewer program</a>.<br>
544
544
<br>
545
-
The command supports one parameter that allows to force a viewing mode<spanclass="versionref"><sup>(Beta version)</sup></span> (in this case, plugins will be ignored, but you can switch the mode later in the viewer window).
545
+
The command supports one parameter that allows to force a viewing mode (in this case, plugins will be ignored, but you can switch the mode later in the viewer window).
546
546
See the description of the modes on <ahref="viewer.html#mnu_view">this page</a>.<br>
<tdclass="cmdhintcell">Add plugin: Double Commander will prompt you to select a plugin file, automatically detect its type (WCX, WDX, WFX, WLX or DSX), open the required settings section and add it to the list.<br>
1047
-
The plugin filename can be passed as a parameter.
1046
+
<tdclass="cmdhintcell">This command makes it easy to add plugins, two ways are supported:<br>
1047
+
1) Select a plugin file and Double Commander will automatically detect its type (WCX, WDX, WFX, WLX or DSX), open the required settings section and add it to the list.<br>
1048
+
2) Select the archive that contains the plugin and a special file <tt>pluginst.inf</tt> (the plugin file and <tt>pluginst.inf</tt> must be located in the root of the archive):
1049
+
the content of the archive will be extracted to the appropriate directory, the plugin will be added to the settings and Double Commander will open the corresponding settings section. If settings are stored in the user profile, Double Commander will use the "plugins" folder in the user's directory:
1050
+
<ul>
1051
+
<li>Windows XP: <i>C:\Documents and Settings\<UserName>\Local Settings\doublecmd\plugins</i></li>
In the portable version, Double Commander will use the "plugins" folder in the program directory.<br>
1056
+
<br>
1057
+
Note: The first method of adding plugins requires to first place the files in a suitable location, however, in this case, Double Commander will report an error if the plugin could not be loaded (for example, if the operating systems does not contain the necessary libraries).<br>
<tdclass="cmdhintcell">Load list of files/folders from the specified text file (plain text file containing full file names, one per line). Use UTF-8 without BOM.<br>
<tdclass="cmdhintcell">Will copy the full path of the current selected items including an ending directory separator.</td>
1545
+
<tdclass="cmdhintcell">Will copy the full path of the current selected items including an ending directory separator.<br>
1546
+
One parameter is available, we can specify the preferred directory separator, see the description of <ahref="#cm_CopyFullNamesToClip">cm_CopyFullNamesToClip</a>.</td>
<tdclass="cmdhintcell">Will copy the full path of the current selected items excluding an ending directory separator.</td>
1551
+
<tdclass="cmdhintcell">Will copy the full path of the current selected items excluding an ending directory separator.<br>
1552
+
One parameter is available, we can specify the preferred directory separator, see the description of <ahref="#cm_CopyFullNamesToClip">cm_CopyFullNamesToClip</a>.</td>
<p>Note: macOS command line has a some specificity, use the <code>open</code> command with the full application name ("Double Commander" with <code>-a</code>) and <code>--args</code> to pass parameters. For the second and subsequent instances, add <code>-n</code>.</p>
43
45
<pclass="navback"><ahref="#topofpage">(back to top)</a></p>
0 commit comments