Configuration File
The command-line utility looks for a configuration file in your home directory. On UNIX systems and Mac OS it's called ".cp2rc", while on Windows it's called "_cp2rc". The easiest way to figure out where it lives and what it's called is to use the version command:
cp2 version
CiderPress II Command-Line Utility v1.0.0 + DiskArc Library v1.0.0 + Runtime: .NET 6.0.25 / win10-x64 Settings file is 'C:\Users\fadden\_cp2rc' Copyright 2023 faddenSoft - https://ciderpress2.com/ See http://www.apache.org/licenses/LICENSE-2.0 for license.
The output will show where the config file is, or if it doesn't exist, where it should be placed.
The config file is not created automatically. The CiderPress II installation package comes with a sample config file, called "sample.cp2rc", that can be used as a starting point.
The config file recognizes two kinds of statements. The first is used to change the default values used for command options. It's simply the command name, followed by a colon, then one or more options.
For example, if you wanted the catalog command to use --depth=shallow and show the notes for any problems found in the archive, you could add a line:
catalog: --show-notes --depth=shallow
Or maybe you want the default file extraction preservation mode to be AppleSingle:
extract: --preserve=as
If you want to specify that an option should be applied to all commands, you can use the special command name "global". For example, to reduce the verbosity of all commands:
global: --no-verbose
The second kind of statement sets the default options for import and export converters. These options take effect even when exporting with the "best" specifier. For example, if you wanted to to export Apple II hi-res images in black & white, you could add:
>export hgr,bw=true
To change the text importer to treat input as ISO 8859-1 rather than UTF-8:
>import text,char=latin
See the CLI manual for a complete list of import/export converters and their associated options.