This commit assumes that the user-provided variable for the filename
will start with '.zcomp'. This is used in the .zlogin for zcompiling the
completion file. Sourcing the .zimrc file within the .zlogin file is
something I'd rather not do, and this seems like a good compromise. If
this becomes an issue, the file can be sourced an the var can be used
instead.
Closes#42
[zlogin] zcompare fasd and all functions
[fasd] trim non-zsh options
[fasd] merge PR #75 from clvv/fasd
[fasd] partial merge PR #77 from clvv/fasd
This closes#24
* moves check for yaourt into the other zpacman_frontend checks
* remove hardcoded sudo vs non-sudo; uses zpacman_frontend[_priv]
instead.
* these vars are set in the zpacman_frontend value sanity check.
* for values != yaourt, prepend sudo for zpacman_frontend_priv
* remove unneeded explination and authorship comments (as it's
noted in the README.md)
* s/git/command git/ (see issue #30)
* add is-true function, as it is required by a few other functions.
Alternative approach to determine if aliasing safe-rm is viable.
If safe-rmdir is available, the OS is Suse (which has it's own safe-rm).
Note to Suse: you're making problems for me. Stop.
Closes#27
The code in the utility module only checks if the value is 'true'. There
is no need to set it to 'false'; just don't set it at all.
This should make it easier to enable/disable (uncomment vs value
change).
Only bind keys if length of var > 0
Hopefully these are the only keys that will require this testing. If
anyone encounters issues like issue #17 with additional keys, please
create an issue.
Closes#17
The old test, [[ ${var} ]] tests for unset AND zero-length strings.
Checking for zero length strings probably isn't that important. It is
enough to ensure that the variable is set.
Closes#18