go/task
go/task
1
0
Fork 0
mirror of https://github.com/go-task/task.git synced 2025-03-21 21:27:07 +02:00
Code Issues Releases Activity
task/completion/bash/task.bash

27 lines
536 B
Bash
Raw Normal View History

Address shellcheck warnings in task.bash
2022-05-22 16:15:15 +02:00
#!/bin/bash
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
Make progname easier to configure in task.bash As task is a very generic name that conflicts with for example taskwarrior, some packagers might choose to change it. See my package in the AUR: https://aur.archlinux.org/packages/go-task. This change makes it easier to configure the name for downstream packagers.
2022-05-22 16:16:50 +02:00
GO_TASK_PROGNAME=task
_go_task_completion()
Add initial version of bash autocomplete
2019-08-30 09:59:03 +10:00
{
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
local cur
_get_comp_words_by_ref -n : cur
Add initial version of bash autocomplete
2019-08-30 09:59:03 +10:00
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
case "$cur" in
--*)
Address shellcheck warnings in task.bash
2022-05-22 16:15:15 +02:00
local options
options="$(_parse_help task)"
mapfile -t COMPREPLY < <(compgen -W "$options" -- "$cur")
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
;;
*)
Address shellcheck warnings in task.bash
2022-05-22 16:15:15 +02:00
local tasks
Make progname easier to configure in task.bash As task is a very generic name that conflicts with for example taskwarrior, some packagers might choose to change it. See my package in the AUR: https://aur.archlinux.org/packages/go-task. This change makes it easier to configure the name for downstream packagers.
2022-05-22 16:16:50 +02:00
tasks="$($GO_TASK_PROGNAME --list-all 2> /dev/null | awk 'NR>1 { sub(/:$/,"",$2); print $2 }')"
Address shellcheck warnings in task.bash
2022-05-22 16:15:15 +02:00
mapfile -t COMPREPLY < <(compgen -W "$tasks" -- "$cur")
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
;;
esac
Add initial version of bash autocomplete
2019-08-30 09:59:03 +10:00
bash-completion refactoring 1. 'compgen -c' lists _all_ command names on the system, which is not appropriate for this script, furthermore echo does not read from stdin so the output is lost. 2. use _get_comp_words_by_ref and __ltrim_colon_completions to handle task names with colons. "...modifying COMP_WORDBREAKS in your completion script is not safe (as it is a global variable and it has the side effect of affecting the behavior of other completion scripts" Ref.: https://stackoverflow.com/a/12495727/7044304 3. Add options completion 4. Use task --list-all
2022-02-13 20:20:01 +01:00
__ltrim_colon_completions "$cur"
Add initial version of bash autocomplete
2019-08-30 09:59:03 +10:00
}
Make progname easier to configure in task.bash As task is a very generic name that conflicts with for example taskwarrior, some packagers might choose to change it. See my package in the AUR: https://aur.archlinux.org/packages/go-task. This change makes it easier to configure the name for downstream packagers.
2022-05-22 16:16:50 +02:00
complete -F _go_task_completion $GO_TASK_PROGNAME
Reference in New Issue Copy Permalink