ADDBACKGROUND

/S

(no value)

Adds selected images to the list on the Display / Images Preferences page. This makes them available to be used as background images in Listers and toolbars. For example, you could add this command to the context menu for the Imagesfile type group.

Example: Prefs ADDBACKGROUND

BACKUP

/O

(no value)

Automates the configuration backup process. By default all your configuration settings, toolbars, menus and hotkeys are included in the backup, but extra data like images and sounds are not. The optional values for this argument can be used to control which extra data is included in the backup. Use the TO argument to specify the name of the backup file, and the PASSWORD, DESC and QUIET arguments provide additional control.

Example: Prefs BACKUP TO="/desktop/PrefsBackup"

images

When automating a configuration backup, includes image files in your backup (corresponds to the Backup images option in the Backup and Restore Configuration wizard).

Example: Prefs BACKUP=images TO="/desktop/PrefsBackup"

sounds

Includes sound files in the backup (corresponds to the Backup sounds option).

Example: Prefs BACKUP=sounds TO="/desktop/PrefsBackup"

data

Include miscellaneous data in the backup (corresponds to the Backup miscellaneous data option).

Example: Prefs BACKUP=data TO="/desktop/PrefsBackup"

localstate

Include local state data (corresponds to the Backup local state data option).

Example: Prefs BACKUP=data,localstate TO="/desktop/PrefsBackup"

all

Backup everything (equivalent to BACKUP=images,sounds,data,localstate).

Example: Prefs BACKUP=all TO="/desktop/PrefsBackup"

CUSTOMIZE

/O

(no value)

Displays the Customize dialog. The dialog will open on the page that was last used.

Example: Prefs CUSTOMIZE

<page>

Displays the specified tab on the Customize dialog. Allowable values for this argument are commands, toolbars, keys and menus.

Example: Prefs CUSTOMIZE=toolbars

FILETYPES

/S

(no value)

Displays the File Types dialog.

Example: Prefs FILETYPES

FTPSITES

/O

(no value)

Displays the FTP Address Book.

Example: Prefs FTPSITES

<site name>

Displays the FTP Address Book and automatically selects the named site. If the site is in a sub-folder in the address book you need to provide the full path of the site.

Example: Prefs FTPSITES="WorkServers\Production"

LAYOUT

/K

<layout name>

Loads the named Lister layout.

Example: Prefs LAYOUT="Music Albums"

LAYOUTEDIT

/S

(no value)

Opens the Preferences dialog and displays the Layouts and Styles / Layouts page (equivalent to Prefs PAGE=layouts).

Example: Prefs LAYOUTEDIT

LAYOUTIGNORETOOLBARS

/K

yes

When loading a layout with the LAYOUT argument, this overrides the Ignore toolbars saved within this layout flag set for the layout, and forces the layout's toolbars to be ignored, and the default toolbar set to be used instead. When saving a layout with the LAYOUTSAVE argument, it sets the state of that flag within the layout.
 

Example: Prefs LAYOUT="Photos" LAYOUTIGNORETOOLBARS=yes

no

Does not ignore the layout's toolbars.

Example: Prefs LAYOUT="Photos" LAYOUTIGNORETOOLBARS=no

LAYOUTMOUSERELATIVE

/K

yes

When loading a layout with the LAYOUT argument, this overrides the Open layout relative to the monitor the mouse is currently on flag set for the layout, and forces the layout's position to be relative to the mouse. When saving a layout with the LAYOUTSAVE argument, it sets the state of that flag within the layout.

Example: Prefs LAYOUT="Find" LAYOUTMOUSERELATIVE=yes

no

Does not open the layout relative to the mouse pointer.

Example: Prefs LAYOUT="BackupFiles" LAYOUTMOUSERELATIVE=no

LAYOUTSAVE

/O

(no value)

Saves the currently open Listers as a layout. You can use the LAYOUTNAME argument to specify the layout name. You can also use the LAYOUTCLOSELISTERS, LAYOUTIGNOREFORMATS and LAYOUTMOUSERELATIVE arguments to control the state of those flags for the saved layout.

Example: Prefs LAYOUTSAVE

single

Saves only the active Lister as a layout. Any other currently open Listers are not included.

Example: Prefs LAYOUTSAVE=single LAYOUTNAME="CurrentLister"

noupdatesettings

If you do not use the LAYOUTNAME argument to provide a name for the layout, Opus will display a dialog prompting for the name - this dialog also contains various options for the layout (ignore formats, mouse relative, etc). Changes you make to those options will be saved as the default settings for the LAYOUTSAVE function unless you specify the noupdatesettings value.

Example: Prefs LAYOUTSAVE=noupdatesettings LAYOUTMOUSERELATIVE=yes LAYOUTNAME="My Layout" 

updatecurrent

If the current lister is already part of a layout, that layout will be updated and you will not be prompted for a layout name or any further options.

Example: Prefs LAYOUTSAVE=updatecurrent 

LIMITPATH

/K/M

<paths>

When opening a new Layout with the LAYOUT argument, this lets you restrict the newly opened Listers to one or more paths  (and their descendants). Attempts to navigate outside of the allowed paths will display an error.

Example: Prefs LAYOUT="Focus On Work" LIMITPATH "C:\Work"

reset

If a Layout was saved with restricted paths, this lets you override the restrictions when opening the Layout.

Example: Prefs LAYOUT="LockedLister" LIMITPATH=reset

PAGE

/K

<prefs page>

Opens the Preferences dialog to the specified page. If this argument is not supplied the Preferences dialog will open to the last-used page. Valid page keywords are:

advanced	aliases	archivecontext
assignedlabels	arcoptions	autoloading
colors	copyattr	copyopts
dblclkfiles	dblclktaskbar	deflister
deleting	details	display
displaymodetoolbars	doubleclick	email
explorerrep	faves	fayt
fdb	fields	filedisplay
fileop	filterbar	filters
flickr	folderbehavior	folderdisplay
folderformats	foldertabs	globalfilters
iconsets	images	jumplist
labels	language	layouts
logging	metadata	misc
mouse	plugins	powerdetails
powermodebuttons	progress	proxy
recent	rename	scripts
smartfaves	sounds	startup
status	styles	tabappearance
tabgroups	thumbnails	tiles
toolbarappearance	toolbars	toolbarsets
transitionanimations	treeactions	treeappearance
treebehavior	treecontents	updates
vfsplugins	viewer1	viewer2
viewer3	viewerpane	virtualfolders
windowsint	winehotkey	zip

Some pages allow data to be passed to them to indicate the item to edit. For example, scripts allows a script to be selected by name and its configuration dialog to be shown automatically. To do this, append a colon and the appropriate data to the page name.

Example:Prefs PAGE=transitionanimations
Example: Prefs PAGE=scripts:dopstack.js

QUIET

/S

(no value)

Prevents the Backup and Restore Configuration wizard from appearing when the backup or restore are automated (when used with the BACKUP and RESTORE arguments). If specified when restoring a configuration, Opus will be restarted automatically - you can use the Close AUTOLISTER command to control whether a new Lister is opened when Opus restarts this way.

Example: Prefs RESTORE FROM="/desktop/PrefsBackup" QUIET

SCRIPTDISABLE

/O

(no value)

If no script name is given, the command toggles the global option to disable all script add-ins. This will disable any event scripts, command scripts and column scripts you have installed. This is typically used to test if problems are due to scripts or something else.

The global option does not affect the enabled/disabled state of any individual script. In other words, if a script is disabled and you then disable scripting globally, then enable scripting globally again, the script will still be disabled. The other difference between the global setting and individually disabling all scripts is that the global setting will also affect scripts which are installed after the change.

Example: Prefs SCRIPTDISABLE

<script name>

Enable or disable the specified script or scripts. The script name should match the filename(s) of the script add-in(s) you wish to affect.

If the global option to disable all script add-ins is in effect, no individual script can be enabled.

The script name can use simple * wildcards to match multiple filenames. While this can be used to enable or disable multiple scripts at once, it is intended to avoid worrying about whether a script is installed with ".js" and ".vbs" or ".js.txt" and ".vbs.txt" style extensions.

(As a special case, if the script name wildcard is literally "*" or "*.*", the command acts the same as if no script name was specified, and toggles the global option to disable all script add-ins.)

If the script name is the only parameter, the script will be toggled (enabled if currently disabled; disabled if currently enabled). If multiple scripts match the pattern, they will all be set to the same state as the first match, and not toggled individually.

Example:Prefs SCRIPTDISABLE="My Script.js*"

If a script is inside a Script Package (.osp file), the package must be included in the name:

Example:Prefs SCRIPTDISABLE="My Package.osp\My Script.vbs"

Wildcards can make dealing with script packages easier, and can also handle script packages which contain multiple scripts, or where you distribute a script to people as a .osp but work on it privately as a text file:

Example:Prefs SCRIPTDISABLE="My Package.osp*"
Example:Prefs SCRIPTDISABLE="*My Script.vbs*"

enable

Enable the specified script(s), or all scripts if no script name is specified.

Example:Prefs SCRIPTDISABLE="My Script.js*,enable"
Example:Prefs SCRIPTDISABLE=enable

disable

Disable the specified script(s), or all scripts if no script name is specified.

Example:Prefs SCRIPTDISABLE="My Script.js*,disable"
Example:Prefs SCRIPTDISABLE=disable

toggle

Toggle the specified script(s), or all scripts if no script name is specified.

(This is the default, if neither "enable" nor "disable" is specified, but you can include it if you wish to be more explicit.)

Example:Prefs SCRIPTDISABLE="My Script.js*,toggle"
Example:Prefs SCRIPTDISABLE=toggle

Note that when a SCRIPTDISABLE button is a toggle, the button will appear active (e.g. checked or highlighted) when scripts are disabled. As with most commands, you can add @toggle:invert on a new line at the top of the command sequence to reverse this.

Example:
  @toggle:invert
  Prefs SCRIPTDISABLE="Viewer Select.js,toggle"

SHOWICONS

/S

(no value)

Displays icons for dynamic lists generated by the LAYOUTLIST, STYLELIST and VFSPLUGINLIST arguments.

Example: Prefs LAYOUTLIST SHOWICONS

STYLEEDIT

/S

(no value)

Displays the Layouts and Styles / Styles page in Preferences (equivalent to Prefs PAGE=styles).

Example: Prefs STYLEEDIT

STYLESAVE

/O

(no value)

Saves the current appearance of the active Lister as a style.

Example: Prefs STYLESAVE

<style name>

Specifies the name for the style to create. Opus will prompt for a name if one is not provided.

Example: Prefs STYLESAVE="My Style"

TO

/K

<backup file>

Specifies the filename for the configuration backup (used with the BACKUP or BACKUPRESTORE argument).

Example: Prefs BACKUP TO="/mydocuments/OpusPrefsBackup {date|yyyy-MM-dd}"

VFSPLUGINABOUT

/K

<plugin name>

Displays the About dialog for the specified VFS plugin.

Example: Prefs VFSPLUGINABOUT opus7zip.dll

VFSPLUGINDISABLE

/K

<plugin name>

Enable or disable the specified VFS plugin. If the plugin is currently enabled it will be disabled, and vice versa.

Example: Prefs VFSPLUGINDISABLE opus7zip.dll

A single VFS plugin DLL may present itself as multiple types. For example, the Archives plugin (opus7zip.dll) which comes with Opus has separate types for 7z, RAR, ISO, and so on. If you specify just the name of the DLL, the entire plugin will be toggled. You can also toggle individual types (assuming the plugin as a whole is still enabled) by adding a ':' character after the DLL name and then the name of the type, as found in the Preferences VFS Plugins page.

Example:Prefs VFSPLUGINDISABLE opus7zip.dll:rar

enable

Enable the specified VFS plugin.

Example: Prefs VFSPLUGINDISABLE opus7zip.dll,enable

disable

Disable the specified VFS plugin.

Example: Prefs VFSPLUGINDISABLE opus7zip.dll,disable

toggle

Toggling is the default, if neither "enable" nor "disable" is specified, but you can specify "toggle" if you wish to be more explicit.

Note that when a VFSPLUGINDISABLE button is a toggle, the button will appear active (e.g. checked or highlighted) when plugins are disabled. As with most commands, you can add @toggle:invert on a new line at the top of the command sequence to reverse this.

Example:
  @toggle:invert
  Prefs VFSPLUGINDISABLE="opus7zip.dll,toggle"

VFSPLUGINMANAGER

/S

(no value)

Displays the Zip & Other Archives / Archive and VFS Plugins page in Preferences (equivalent to Prefs PAGE=vfsplugins).

Example: Prefs VFSPLUGINMANAGER