system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-21 18:24:38 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
systemd/shell-completion/zsh/_coredumpctl

48 lines
2 KiB
Plaintext
Raw Normal View History

shell-completion: revert c1072f6473bafa063cbf700c86524083d2857031 fixing https://github.com/systemd/systemd/issues/19689
2021-06-16 19:35:12 +00:00
#compdef coredumpctl
license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 04:23:58 +00:00
# SPDX-License-Identifier: LGPL-2.1-or-later
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
zsh completion: Prevent functions from clobbering each other, &c. - Don't redefine helpers on every call - Prefix helper names with main function name - Adjust some helper names for consistency and convention adherance
2018-12-24 11:15:38 +00:00
(( $+functions[_coredumpctl_commands] )) ||
_coredumpctl_commands(){
coredump: coredumpctl is so useful now, make it a first-class citizen Drop the "systemd-" prefix, renaming it from "systemd-coredumpctl" to "coredumpctl".
2014-06-19 11:46:01 +00:00
local -a _coredumpctl_cmds
_coredumpctl_cmds=(
shell-completion: use 4 space indentation too The same as in other places, indentation levels were all over the place.
2019-04-05 09:39:14 +00:00
'list:List available coredumps'
'info:Show detailed information about one or more coredumps'
'dump:Print coredump to stdout'
'debug:Start debugger (gdb) on a coredump'
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
)
if (( CURRENT == 1 )); then
coredump: coredumpctl is so useful now, make it a first-class citizen Drop the "systemd-" prefix, renaming it from "systemd-coredumpctl" to "coredumpctl".
2014-06-19 11:46:01 +00:00
_describe -t commands 'coredumpctl command' _coredumpctl_cmds
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
else
local curcontext="$curcontext"
local -a _dumps
coredump: coredumpctl is so useful now, make it a first-class citizen Drop the "systemd-" prefix, renaming it from "systemd-coredumpctl" to "coredumpctl".
2014-06-19 11:46:01 +00:00
cmd="${${_coredumpctl_cmds[(r)$words[1]:*]%%:*}}"
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
if (( $#cmd )); then
zsh/coredumpctl: don't print warnings from completion function
2018-12-31 20:27:09 +00:00
_dumps=( "${(f)$(coredumpctl list -q --no-legend | awk 'BEGIN{OFS=":"} {sub(/[[ \t]+/, ""); print $4,$0}' 2>/dev/null)}" )
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
if [[ -n "$_dumps" ]]; then
zsh/coredumpctl: Never sort the completion candidates That way, they're always sorted by date. I do not know how to make ZSH sort them by PID through some option, but that doesn't seem very useful in the first place.
2018-01-13 14:23:28 +00:00
_describe -V -t pids 'coredumps' _dumps
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
else
_message "no coredumps"
fi
else
_message "no more options"
fi
fi
}
_arguments \
improve zsh completion (#32098) * fix error * remove options that are no longer supported * add missing options * stop completion if an option `--help` or `--version` is supplied [[[ zjs: a note for the reader: zshcompsys(1) in the section about optspecs in _arguments says: > Each of the forms above may be preceded by a list in parentheses of option names and argument num‐ > bers. If the given option is on the command line, the options and arguments indicated in parentheses > will not be offered. For example, ‘(-two -three 1)-one:...' completes the option ‘-one'; if this ap‐ > pears on the command line, the options -two and -three and the first ordinary argument will not be > completed after it. ‘(-foo):...' specifies an ordinary argument completion; -foo will not be com‐ > pleted if that argument is already present. > > Other items may appear in the list of excluded options to indicate various other items that should > not be applied when the current specification is matched: a single star (\*) for the rest arguments > (i.e. a specification of the form ‘\*:...'); a colon (:) for all normal (non-option-) arguments; and a > hyphen (-) for all options. For example, if ‘(\*)' appears before an option and the option appears on > the command line, the list of remaining arguments (those shown in the above table beginning with > ‘\*:') will not be completed. The intended effect of the change is to remove irrelevant completion matches from the completion. tl;dr: (- : ) prevents further completion ]]]
2024-04-15 08:58:48 +00:00
'(-o --output)'{-o+,--output=}'[Write output to FILE]:output file:_files' \
'(-F --field)'{-F+,--field=}'[Show field in list output]:field' \
zsh-completion: add missing completions for coredumpctl
2015-01-12 20:26:27 +00:00
'-1[Show information about most recent entry only]' \
improve zsh completion (#32098) * fix error * remove options that are no longer supported * add missing options * stop completion if an option `--help` or `--version` is supplied [[[ zjs: a note for the reader: zshcompsys(1) in the section about optspecs in _arguments says: > Each of the forms above may be preceded by a list in parentheses of option names and argument num‐ > bers. If the given option is on the command line, the options and arguments indicated in parentheses > will not be offered. For example, ‘(-two -three 1)-one:...' completes the option ‘-one'; if this ap‐ > pears on the command line, the options -two and -three and the first ordinary argument will not be > completed after it. ‘(-foo):...' specifies an ordinary argument completion; -foo will not be com‐ > pleted if that argument is already present. > > Other items may appear in the list of excluded options to indicate various other items that should > not be applied when the current specification is matched: a single star (\*) for the rest arguments > (i.e. a specification of the form ‘\*:...'); a colon (:) for all normal (non-option-) arguments; and a > hyphen (-) for all options. For example, if ‘(\*)' appears before an option and the option appears on > the command line, the list of remaining arguments (those shown in the above table beginning with > ‘\*:') will not be completed. The intended effect of the change is to remove irrelevant completion matches from the completion. tl;dr: (- : ) prevents further completion ]]]
2024-04-15 08:58:48 +00:00
'(-S --since)'{-S,--since}'[Print entries since the specified date]' \
'(-U --until)'{-U,--until}'[Print entries until the specified date]' \
'(-r --reverse)'{-r,--reverse}'[Show the newest entries first]' \
zsh_completion: Split out zsh _coredumpctl
2013-07-29 19:09:10 +00:00
'--no-pager[Do not pipe output into a pager]' \
zsh-completion: add missing completions for coredumpctl
2015-01-12 20:26:27 +00:00
'--no-legend[Do not print the column headers]' \
improve zsh completion (#32098) * fix error * remove options that are no longer supported * add missing options * stop completion if an option `--help` or `--version` is supplied [[[ zjs: a note for the reader: zshcompsys(1) in the section about optspecs in _arguments says: > Each of the forms above may be preceded by a list in parentheses of option names and argument num‐ > bers. If the given option is on the command line, the options and arguments indicated in parentheses > will not be offered. For example, ‘(-two -three 1)-one:...' completes the option ‘-one'; if this ap‐ > pears on the command line, the options -two and -three and the first ordinary argument will not be > completed after it. ‘(-foo):...' specifies an ordinary argument completion; -foo will not be com‐ > pleted if that argument is already present. > > Other items may appear in the list of excluded options to indicate various other items that should > not be applied when the current specification is matched: a single star (\*) for the rest arguments > (i.e. a specification of the form ‘\*:...'); a colon (:) for all normal (non-option-) arguments; and a > hyphen (-) for all options. For example, if ‘(\*)' appears before an option and the option appears on > the command line, the list of remaining arguments (those shown in the above table beginning with > ‘\*:') will not be completed. The intended effect of the change is to remove irrelevant completion matches from the completion. tl;dr: (- : ) prevents further completion ]]]
2024-04-15 08:58:48 +00:00
'(- *)'{-h,--help}'[Show this help]' \
'(- *)--version[Show package version]' \
zsh/coredumpctl: complete argument for --debugger= This way external commands (i.e. executables in the PATH) are suggested at --debugger=<TAB>. Upon starting a path (e.g. --debugger=/<TAB> or --debugger=./<TAB>), filenames of executables are completed.
2018-12-25 18:30:50 +00:00
'--debugger=[Use the given debugger]:debugger: _command_names -e' \
improve zsh completion (#32098) * fix error * remove options that are no longer supported * add missing options * stop completion if an option `--help` or `--version` is supplied [[[ zjs: a note for the reader: zshcompsys(1) in the section about optspecs in _arguments says: > Each of the forms above may be preceded by a list in parentheses of option names and argument num‐ > bers. If the given option is on the command line, the options and arguments indicated in parentheses > will not be offered. For example, ‘(-two -three 1)-one:...' completes the option ‘-one'; if this ap‐ > pears on the command line, the options -two and -three and the first ordinary argument will not be > completed after it. ‘(-foo):...' specifies an ordinary argument completion; -foo will not be com‐ > pleted if that argument is already present. > > Other items may appear in the list of excluded options to indicate various other items that should > not be applied when the current specification is matched: a single star (\*) for the rest arguments > (i.e. a specification of the form ‘\*:...'); a colon (:) for all normal (non-option-) arguments; and a > hyphen (-) for all options. For example, if ‘(\*)' appears before an option and the option appears on > the command line, the list of remaining arguments (those shown in the above table beginning with > ‘\*:') will not be completed. The intended effect of the change is to remove irrelevant completion matches from the completion. tl;dr: (- : ) prevents further completion ]]]
2024-04-15 08:58:48 +00:00
'(-D --directory)'{-D,--directory=}'[Use the journal files in the specified dir]:directory: _directories' \
'(-q --quiet)'{-q,--quiet}'[Do not show info messages and privilege warning]' \
coredump: Add --all option This option has coredumpctl look at all journals instead of only the local ones. This allows coredumpctl to show information about remote coredumps if the coredumps are made available in /var/lib/systemd/coredump and the corresponding journals are made available in /var/log/journal. This is already possible using the --directory option but --all makes it more user friendly since users don't have to enter the journal directory anymore as long as it's available under /var/log/journal.
2021-10-06 12:47:46 +00:00
'--all[Look at all journal files instead of local ones]' \
zsh completion: Prevent functions from clobbering each other, &c. - Don't redefine helpers on every call - Prefix helper names with main function name - Adjust some helper names for consistency and convention adherance
2018-12-24 11:15:38 +00:00
'*::coredumpctl commands:_coredumpctl_commands'
Reference in a new issue Copy permalink