2018-03-07 16:34:05 -05:00
|
|
|
#compdef alacritty
|
|
|
|
|
|
|
|
|
|
_alacritty() {
|
|
|
|
|
local context curcontext="$curcontext" state line
|
|
|
|
|
typeset -A opt_args
|
|
|
|
|
|
|
|
|
|
_arguments \
|
|
|
|
|
"(-h --help)"{-h,--help}"[Prints help information]" \
|
|
|
|
|
"(-V --version)"{-V,--version}"[Prints version information]" \
|
|
|
|
|
"(--no-live-config-reload)--live-config-reload[Enable automatic config reloading]" \
|
|
|
|
|
"(--live-config-reload)--no-live-config-reload[Disable automatic config reloading]" \
|
Display errors and warnings
To make sure that all error and information reporting to the user is
unified, all instances of `print!`, `eprint!`, `println!` and
`eprintln!` have been removed and replaced by logging.
When `RUST_LOG` is not specified, the default Alacritty logger now also
prints to both the stderr and a log file. The log file is only created
when a message is written to it and its name is printed to stdout the
first time it is used.
Whenever a warning or an error has been written to the log file/stderr,
a message is now displayed in Alacritty which points to the log file
where the full error is documented.
The message is cleared whenever the screen is cleared using either the
`clear` command or the `Ctrl+L` key binding.
To make sure that log files created by root don't prevent normal users
from interacting with them, the Alacritty log file is `/tmp/Alacritty-$PID.log`.
Since it's still possible that the log file can't be created, the UI
error/warning message now informs the user if the message was only
written to stderr. The reason why it couldn't be created is then printed
to stderr.
To make sure the deletion of the log file at runtime doesn't create any
issues, the file is re-created if a write is attempted without the file
being present.
To help with debugging Alacritty issues, a timestamp and the error
level are printed in all log messages.
All log messages now follow this format:
[YYYY-MM-DD HH:MM] [LEVEL] Message
Since it's not unusual to spawn a lot of different terminal emulators
without restarting, Alacritty can create a ton of different log files.
To combat this problem, logfiles are removed by default after
Alacritty has been closed. If the user wants to persist the log of a
single session, the `--persistent_logging` option can be used. For
persisting all log files, the `persistent_logging` option can be set in
the configuration file
2018-11-17 09:39:13 -05:00
|
|
|
"(--persistent-logging)--persistent-logging[Keep the log file after quitting Alacritty]" \
|
2018-03-07 16:34:05 -05:00
|
|
|
"--print-events[Print all events to stdout]" \
|
|
|
|
|
{-q,-qq}"[Reduces the level of verbosity (min is -qq)]" \
|
|
|
|
|
{-v,-vv,-vvv}"[Increases the level of verbosity (max is -vvv)]" \
|
|
|
|
|
"--ref-test[Generates ref test]" \
|
|
|
|
|
"--config-file[Specify an alternative config file]:file:_files" \
|
|
|
|
|
"(-d --dimensions)"{-d,--dimensions}"[Window dimensions]:dimensions:_guard '<->' width: :_guard '<->' length" \
|
|
|
|
|
"--title[Defines the window title]:title:" \
|
|
|
|
|
"--working-directory[Start shell in specified directory]:directory:_dir_list" \
|
|
|
|
|
"(-e --command)"{-e,--command}"[Execute command (must be last arg)]:program: _command_names -e:*::program arguments: _normal"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
_alacritty "$@"
|