Give example of `config` usual location
This commit is contained in:
parent
119279f749
commit
390b9d1cb6
|
@ -100,9 +100,10 @@ more information).
|
|||
|
||||
### Configuration `config` File Format
|
||||
|
||||
The file (which is always named `config`) uses the simplest possible
|
||||
format to facilitate standard UNIX parsing and filtering with any number
|
||||
of existing tools (and no `jq` dependency).
|
||||
The file (which is always named `config` and almost always located at
|
||||
`~/.config/cmd/config`) uses the simplest possible format to
|
||||
facilitate standard UNIX parsing and filtering with any number of
|
||||
existing tools (and no `jq` dependency).
|
||||
|
||||
* One KEY=VALUE per line
|
||||
* KEYs may be anything but the equal sign (`=`)
|
||||
|
@ -160,5 +161,5 @@ Displays a summary of usage.
|
|||
|
||||
----
|
||||
|
||||
*Autogenerated Mon Aug 23 10:09:44 PM EDT 2021*
|
||||
*Autogenerated Mon Aug 23 10:14:22 PM EDT 2021*
|
||||
|
||||
|
|
7
cmd
7
cmd
|
@ -230,9 +230,10 @@ more information).
|
|||
|
||||
### Configuration `config` File Format
|
||||
|
||||
The file (which is always named `config`) uses the simplest possible
|
||||
format to facilitate standard UNIX parsing and filtering with any number
|
||||
of existing tools (and no `jq` dependency).
|
||||
The file (which is always named `config` and almost always located at
|
||||
`~/.config/'"$EXE"'/config`) uses the simplest possible format to
|
||||
facilitate standard UNIX parsing and filtering with any number of
|
||||
existing tools (and no `jq` dependency).
|
||||
|
||||
* One KEY=VALUE per line
|
||||
* KEYs may be anything but the equal sign (`=`)
|
||||
|
|
Loading…
Reference in New Issue