Wes McNamee
Wes McNamee
It seems I could write something fairly simple, at least for `oh-my-zsh` by using `mage -l`, e.g. https://github.com/sawadashota/go-task-completions The problems I see right now are that `mage -l` is fairly...
for the time being though, the autocomplete script could do something like this: ```bash if [ -x ./mage ]; then out=$(./mage -l) else out=$(mage -l) fi echo "${out}" | tail...
so, I figured out the script, naively assuming that the built binary is `./mg` ``` #compdef _mg mg function _mg { _complete_commands () { if [ -x ./mg ]; then...
haha, just found out that `mg` is a text editor. ``` man mg ... mg -- emacs-like text editor ```
@jpopadak that's why I filed #295 such that `mage` can passthru to the compiled binary and not be required to read/parse in order to autocomplete.
I think this is possibly similar to #178 basically, the ability to use tasks (or vars for that matter) kind of like functions. Thus supporting return values, and being to...
I kind of like the idea of an "uncachable" variable, because it would act kind of like a _function_. Though the solution to this problem may be lazy variables discussed...
I kind of see namespaces in `task` as subcommands, and maybe that makes sense for how they should be treated (more or less). There's currently no enforcement of this concept...
linking this to #694 to track for v4
Why is it desirable to hide success output?