| Age | Commit message (Collapse) | Author |
|---|
|
In particular, people were encountering exceptions when `empty?` was
called on a `nil` grouping.
|
|
The output of pass may contain "%", which will cause `message` to throw
the error: "Not enough arguments for format string".
For example, `pass rename foo bar` outputs:
[master c33f7a9] Rename foo to bar.
1 file changed, 0 insertions(+), 0 deletions(-)
rename foo.gpg => bar.gpg (100%)
|
|
It seems this file doesn't use spaces any more.
|
|
In 87ec1489fa98, I forgot that some people like to store more than one line in
their password files. We should only pass the first line to xdotool.
|
|
This works around a bug in xdotool parsing when encountering quotes, see
https://github.com/jordansissel/xdotool/issues/72.
Thanks to Gerd Wachsmuth for the report.
|
|
|
|
|
|
|
|
|
|
|
|
putput to a file named "-"
|
|
|
|
|
|
Uses the PASSWORD_STORE_GPG_OPTS environment variable.
Can be used to (e.g.) change the keyrings or trust model used.
|
|
Multiline insert errors gave a exit code of 0, now correctly propagated.
|
|
|
|
|
|
|
|
|
|
Use delq instead of -reject from the dash package.
|
|
|
|
This fixes a problem where gnupg-agent messages would get mixed with the
password content.
|
|
|
|
|
|
|
|
|
|
instead of cygwin's gpg binary
|
|
|
|
|
|
|
|
This reverts commit ec8140b0f1a422aad16d41d0c322f3a6ceef74fe.
The needed option is only available on GnuPG 2.1, and we need to support
GnuPG 2.0 too.
|
|
|
|
|
|
Symlinks inside password-store make sense when using passff in firefox, and
have the same LDAP password in different websites.
In order to have passff working correctly then, we need to strip the .gpg
extension from symlinks as well. Example output of `pass find site1` or `pass
| grep site1` before this commit:
site1.job.com.gpg -> site2.job.com
and after:
site1.job.com -> site2.job.com
|
|
xclip will return a non-zero exit code if $DISPLAY is not set, which
might happen, for example, if you're running pass in a tmux session
remotely or something like that. xclip itself will also show an error
message ("Can't open display") which provides enough context to figure
out what the problem is.
There might be other reasons for xclip to return a non-zero exit code,
but the man page doesn't list them.
|
|
|
|
|
|
|
|
|
|
Quote shell arguments for insert so that it handles passwords and entry
names that contain special characters.
|
|
The latest gpg-agent from the 2.1 series no longer requires these
environment variables and will instead start gpg-agent as it needs.
|
|
over stdin later.
|
|
Signed-off-by: David Adam <zanchey@ucc.gu.uwa.edu.au>
|
|
|
|
|
|
|
|
Some users may use MacPorts instead of Homebrew. If brew fails to
return a prefix for getopt, check if the user has 'port' installed and
use the MacPort ${prefix} /opt/local.
Avoids an issue where pass terminates because getopt cannot be resolved
in the assumed location /usr/local/bin. Provide support to resolve
absolute path of getopt from a MacPorts installation.
Signed-off-by: Jamie Couture <jamie.couture@gmail.com>
|
|
|
|
|
|
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.
|