manual: document configuration files.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
This commit is contained in:
parent
a48ce88ac1
commit
bdb8691bd0
1 changed files with 14 additions and 0 deletions
|
|
@ -49,3 +49,17 @@ automatically create a version 0 schema file and upgrade it to the latest
|
|||
version on start. newfol does not accept schema files that have a newer version
|
||||
than it currently supports, but it ignores directives it does not understand,
|
||||
and so can be manually downgraded by editing the `fmt` directive.
|
||||
|
||||
=== Configuration File
|
||||
|
||||
Configuration files are identical to schema files except that instead of the
|
||||
text `newfol schema file` in the `fmt` entry, the text `newfol config file` is
|
||||
substituted. Because newfol parses both files in the same way, any entry that
|
||||
is valid in a schema file is also valid in a configuration file. That said,
|
||||
some directives make more sense in a configuration file than others.
|
||||
|
||||
Common directives that are useful in a configuration file are transaction
|
||||
settings, colors, and keybindings.
|
||||
|
||||
The default location is +_$XDG_CONFIG_HOME_/newfol/defaults+. If
|
||||
`$XDG_CONFIG_HOME` is not defined, it defaults to +_$HOME_/.config+.
|
||||
|
|
|
|||
Loading…
Reference in a new issue