Usage
$ neverest [OPTIONS] <COMMAND>
Commands
doctor
: check up the state of the given accountconfigure
: configure the given account (prompt keyring passwords)sync
: synchronize the given accountman
: generate manual pages for theman
commandcompletion
: generate completion script for the given shell
Options
These options are global, which means they can be used in all commands and subcommands.
-c|--config
Override the default configuration file path.
The given paths are shell-expanded then canonicalized (if applicable). If the first path does not point to a valid file, the wizard will propose to assist you in the creation of the configuration file. Other paths are merged with the first one, which allows you to separate your public config from your private(s) one(s).
-o|--output
Customize the output format
The output format determine how to display commands output to the terminal. The possible values are:
json
: output will be in a form of a JSON-compatible objectplain
: output will be in a form of either a plain text or table, depending on the command
-C|--color
Control when to use colors
The default setting is ‘auto’, which means neverest will try to guess when to use colors. For example, if neverest is printing to a terminal, then it will use colors, but if it is redirected to a file or a pipe, then it will suppress color output. neverest will suppress color output in some other circumstances as well. For example, if the $TERM
environment variable is not set or set to dumb
, then neverest will not use colors.
The possible values are:
never
: colors will never be usedalways
: colors will always be used regardless of where output is sentansi
: like ‘always’, but emits ANSI escapes (even in a Windows console)auto
: neverest tries to be smart
--debug
Enable logs with spantrace.
This is the same as running the command with RUST_LOG=debug
environment variable.
--trace
Enable verbose logs with backtrace.
This is the same as running the command with RUST_LOG=trace
and RUST_BACKTRACE=1
environment variables.