mirror of
https://github.com/AsamK/signal-cli.git
synced 2026-05-21 13:44:18 +00:00
Updated FAQ (markdown)
parent
f26d26b0ec
commit
89f27fc113
6
FAQ.md
6
FAQ.md
@ -28,10 +28,14 @@ System entropy is more likely to get depleted on headless servers. There are pro
|
||||
|
||||
### Error parsing arguments
|
||||
|
||||
The `signal-cli` program has a set of options, and each subcommand may have its own options. The correct order is:
|
||||
`signal-cli` [SIGNAL-CLI_OPTIONS] [SUBCOMMAND] [SUBCOMMAND_OPTIONS]
|
||||
|
||||
So, for example:
|
||||
$ signal-cli receive --output=json
|
||||
signal-cli: error: unrecognized arguments: '--output=json'
|
||||
|
||||
The `--output=...` option needs to be in front of the `receive` subcommand:
|
||||
The `--output=...` option belongs to the main program, and needs to be in front of the `receive` subcommand:
|
||||
|
||||
$ signal-cli --output=json receive
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user