aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/completion/pass.zsh-completion (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Escape colons in zsh completion to show url portsGuido Cella2021-06-111-1/+1
| | | | | | zsh completion cuts filenames after colons, for example port numbers. This is fixed by escaping colons. This will also escape backslashes after the first.
* zsh-completion: add prefix zstyleBenjamin Richter2016-02-061-1/+11
| | | | | This option can be used to select a different pass repository for completion. A configuration example is given inside the completion file.
* Fix zsh completion when path contains \Simon Gomizelj2016-02-061-1/+1
|
* Fix pass zsh completion and autoloadingMarc Cornellà2014-07-291-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When autocompleting from `pass <TAB>', sometimes the following errors appear: _values:compvalues:10: not enough arguments find: `/home/user/.password-store': No such file or directory _values:compvalues:10: not enough arguments find: `/home/user/.password-store': No such file or directory The `_values' error happens when there is no password-store folder *or* there are no passwords in pass; the `find' error only when there is no password-store folder. We can trace it back to line 108, which contains the only `_values' statement that is executed when we autocomplete from pass. We confirm this by following the trail of execution, which is _pass -> _pass_cmd_show -> _pass_complete_entries -> -> _pass_complete_entries_helper If we try running the command inside `$()' on line 104, we see that it returns nothing and the output is blank. This means that `_values' only receives 1 of its 2 mandatory parameters, therefore the above error is triggered (not enough arguments). That is unless we don't have a password-store folder, in which case the `find: [...] no such file or directory' error is *also* triggered. We solve the first error by supplying a default value of "" if the command outputs nothing, using the zsh construct ${var:-else}. We solve the second error by redirecting the find command's stderr output to /dev/null, so the error is effectively suppressed. * * * * This patch also fixes the first tab completion, which currently only loads the completion function definition. We do this by adding a `_pass' statement at the end of the file, which runs the `_pass' completion function after loading its definition. This is the standard way an autoloaded function works; for other examples look at zsh's official completion files.
* completion: add new generate flagsJason A. Donenfeld2014-05-081-1/+5
|
* zsh: posix compatible sed fix for zsh-completionJason A. Donenfeld2014-05-081-1/+1
| | | | | This reverts commit 56381287a16792b4c6410f07db68e02f3574c213, and further fixes things.
* zsh-completion: regression when using BSD sedKyle Marek-Spartz2014-05-061-1/+1
| | | | | | | | | | | | | Made sed expression GNU and BSD compatible. A recent change in pass.zsh-completion broke autocompletion when using BSD sed. I’ve made the relevant sed expression compatible with GNU and BSD sed. Previous change with regression: http://lists.zx2c4.com/pipermail/password-store/2014-April/000773.html http://git.zx2c4.com/password-store/commit/src/completion/pass.zsh-completion?id=f82e9d6cf3bc3a12bdfce89bf319d76f79e66efc
* zsh-completion: only remove next char if /Jason A. Donenfeld2014-04-221-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From Kevin: I found a small bug in the zsh completions. Basically when the PASSWORD_STORE_DIR ends in a slash the first character of the result is eaten, making completion essentially useless. (It does this before determining matches). This can be fixed by changing what is line 106 in my version from: _values -C 'passwords' $(find -L "$prefix" \( -name .git -o -name .gpg-id \) -prune -o $@ -print | sed -e "s#${prefix}.##" -e 's#\.gpg##' | sort) to _values -C 'passwords' $(find -L "$prefix" \( -name .git -o -name .gpg-id \) -prune -o $@ -print | sed -e "s#${prefix}/\\?##" -e 's#\.gpg##' | sort) The difference is the first sed regex expression. The original version assumed that the next character was a slash and removed it while the new version only removes it if it is a slash. "s#${prefix}.##" -> "s#${prefix}/\\?##" Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Reported-by: Kevin Cox <kevincox@kevincox.ca>
* reencrypt: remove option, do automaticallyJason A. Donenfeld2014-04-181-5/+1
|
* reencryption: add to completion filesJason A. Donenfeld2014-04-181-0/+2
|
* move/copy: always reencrypt passwords at destinationJason A. Donenfeld2014-04-171-1/+2
|
* mv: Add pass mv/rename supportJason A. Donenfeld2014-04-171-0/+7
| | | | | Based-on-work-by: Matthieu Weber <mweber@free.fr> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* grep: add to completion filesJason A. Donenfeld2014-04-151-0/+1
|
* find: add find/search commandJason A. Donenfeld2014-04-151-0/+1
| | | | | | | This relies on a patched version of tree to work, unfortunately. Hopefully upstream will accept our patch. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* Update zsh completion.Johan Venant2014-03-241-2/+7
|
* Makefile: do not use recursion and organizeJason A. Donenfeld2014-03-221-0/+116
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.