You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2019. It is now read-only.
If my pick.safe is at a non-default location and a ~/.pick/pick.safe is missing, the --safe switch doesn't load the pick.safe from the supplied location.
Example:
> pick --safe ~/temp/pick.safe ls
pick not yet initialized. Please run the init command first
I noticed some discussion on #173 around the path being relative to ~/.pick, however, that doesn't work either. I'd expect the filename to point to an absolute file; but please correct me if I'm wrong with regards to the usage.
The text was updated successfully, but these errors were encountered:
Please try to create an empty `config.toml` in `~/.pick/`:
```sh
$ touch ~/.pick/config.toml
```
This is something I‘ve noticed as well and it is related to cobra / viper (libraries for CLI argument and command parsing). I haven't found a fix so far (except to ensure a config file exists).
Bug report @ upstream: spf13/viper#472
I'm using the 0.8.0 release binary (darwin)
If my
pick.safe
is at a non-default location and a~/.pick/pick.safe
is missing, the--safe
switch doesn't load thepick.safe
from the supplied location.Example:
I noticed some discussion on #173 around the path being relative to
~/.pick
, however, that doesn't work either. I'd expect the filename to point to an absolute file; but please correct me if I'm wrong with regards to the usage.The text was updated successfully, but these errors were encountered: