MacOS holds the GPG agent socket in a different directory than
Linux-based systems. Asking gpgconf for the correct path is the
most straightforward approach to fix this problem.
* Remove older shpotify code from the macOS plugin
* Add Shpotify 2.0.1 from the upstream repository at https://github.com/hnarayanan/shpotify/releases/tag/2.0.1
* Wrap the Shpotify script in a function and import into the macOS plugin
* Fix import path of the shpotify script
* Add shpotify permission notice in the macos plugin rREADME
* Merge with the upstream shpotify project
- Fix playlist playback
- Add a 'stop' command
* Fix the terraform function name
Current function name do worse. I always use `terr<TAB>` and before those prompt it was add space in the end. Now because we have multiple functions and binaries started with terraform there are no space.
* Updated terraform readme
Updated the name of new function name
`pacaur -Syua` only updated AUR pakcages, wihch is incompatible with semantics of `pacupg` and `yaupg`. Removing `-a` here it would work for both main repos and aur.
* Plugin for iTerm2 on OSX
iTerm2 is a popular terminal emulator for OSX (https://www.iterm2.com).
The plugin currently implements one function, iterm2_profile, which
allows easily changing the currently selected user settings profile,
without creating a new tab or window, just by calling the function.
For example, this is handy for switching from a dark to a light colored
profile without having to re-open anything.
In addition, it also works within tmux running inside iTerm2.
* iTerm2 Plugin: Run any iTerm2 command
Refactored the plugin so that it can run arbitrary iTerm2 commands.
Should work with any of the supported commands, see
https://iterm2.com/documentation-escape-codes.html
* iTerm2 Plugin: Add functions to change tab color
The gpg-agent plugin did not work for gpg versions above or equal to
2.1 because of the `--write-env-file` option deprecation. This new version
works fine and also enables the ssh-agent support only if it is enabled in the
gpg-agent config file.
This is the default behavior of rbenv and what users are expecting
most of the time.
It allows users to have their own set of rubies and gems. It also
prevents losing all rubies when rbenv is updated using Homebrew which
is not true when RBENV_ROOT is set to /usr/local/opt/rbenv.
