Go to the first, previous, next, last section, table of contents.
PENG understands the following command-line options:
- `-h', `--help'
-
Output a short option summary and exit
- `-v', `--version'
-
Output version information and exit
- `-N', `--no-builtin-tools'
-
Suppress loading of the built-in tools.
- `-n', `--no-default-config'
-
Suppress loading of the default configuration files. There can be
two default config files, a global one (loaded first) and a per-user
one, loaded after the global one.
They do not have to exist, but if they exist, unless this option is
given, they are automatically loaded after the built-in tools
(unless `-N' or `--no-builtin-tools' is given) and before
any project specific config files specified with the `-c' or
`--config' options (see below).
The names of the default config files are `/etc/peng.conf' and
`~/.peng' under Unix. Under Dos, they are `peng.ini',
either in the directory `$DJDIR\etc\' (if DJGPP is
installed) or in the directory where `peng.exe' is installed,
and `peng.cfg', either in the directory `$HOME' (if
you set the environment variable `HOME') or in the directory
where `peng.exe' is installed.
- `-c config-file', `--config config-file'
-
Load config-file (after the built-in tools and/or default
configuration files depending on the `-N',
`--no-builtin-tools', `-n' or `--no-default-config'
options -- therefore it must be given after possible
`-N', `--no-builtin-tools', `-n' or
`--no-default-config' options). When the configuration is saved
later, it will be written to the last configuration file loaded with
this option or via the `Options/Load config file'
(see section The Menu Entry `Options/Load config file') menu. Only items that were
changed from the default, or from the previously loaded
configuration file, are written, in order to keep the files small.
This also makes it possible to store global options in a global file
and project specific options in other files, so that changing global
options only requires changing one file, not every project
configuration file. The desktop (information about open
windows, contents of input boxes and history lists) is also stored
in the last configuration file -- but note `Options/Save
minimal config' (see section The Menu Entry `Options/Save minimal config').
- `-d', `--dump-tools'
-
Dump the built-in tools to standard output and exit
- `-R', `--read-only'
-
This option causes all following files on the command-line to be
opened read-only -- but not files opened from the `File/Open'
menu (see section The Menu Entry `File/Open'), so an alias like `peng -R' can
be used as a file viewer.
- +line[:column]
-
Specify the position to move to in the next file or info reader given
on the command-line (see below). This is used (line only) e.g., by
`less(1)', so PENG can be used as the editor invoked by less by
setting the environment variable `EDITOR' to `peng'.
- `-i node', `--info node'
-
Open an info reader for node (see section The Format Of An Info Node Description).
Note: Remember to quote parentheses on the command-line when
necessary.
- `-r filename', `--view filename'
-
Open filename read-only.
- `filename'
-
Open filename read-write (unless the `-R' or
`--read-only' option was given before).
Windows opened from the command line are not kept as opened windows
in the config file, and therefore are not opened again automatically
when running PENG again, but can be easily re-opened with
`Window/Last windows' (see section The Menu Entry `Window/Last windows').
However, additional windows opened while running PENG, or windows
closed and opened again are kept as opened windows. This is to
prevent many windows from accumulating when using PENG often with
command line arguments to quickly edit a few files.
Go to the first, previous, next, last section, table of contents.