Closed rebz closed 6 years ago
^ this is the output of a totally different library, it's shpotify! https://github.com/hnarayanan/shpotify/
I think you are having a collusion with your aliases. If you type which spotify
into your terminal, you should see that it's not pointing to the spotify-cli-mac
Well this is embarrassing, lol.
Interesting. This is the first time I've installed a spotify CLI tool on this machine. Looking into how the heck I managed to install this other package, where it's installed, and how to remove.
My apologies.
If you have installed shpotify via Brew, you could try brew uninstall shpotify
Then reinstall spotify-cli-mac using npm, that might fix the symlink.
Already checked brew, it's not installed there. It's not installed in my global either.
No worries, shpotify was the inspiration behind this project in all fairness. Hope you can get it sorted :) Closing this issue.
what do you get from which spotify
?
I'm baffled as to how this was installed; and how to remove it. The first time I've installed a spotify CLI tool was just this morning running npm install spotify-cli-mac -g
. The shpotify obviously has a unique name with the H in it.
Turns out it was pre-built function with oh-my-zsh within the plugins/osx/osx.plugin.zsh
file.
aha! so how does one remove it then?
Looking into that right now. Checking to see if it was part of my dotfiles (computer setup install) or if it something that is inherent with ohmyzsh. Will update once I find out.
Yeah would be good if you could share the steps to remove it. Might be useful for other people if they already installed shpotify beforehand 👍
Entirely my own fault. When installing oh-my-zsh you can configure your plugins within ~/.zshrc
by simply adding plugins=( git composer ...etc )
. The specific plugin that I was osx
. Once removed it fixed the issue. I wasn't using the other shell functions within the osx plugins file.
I am glad you managed to find the root cause of the problem @rebz , closing this issue now.
Feel free to raise another issue if you need support or you find a bug.
I just installed your package last night and haven't had much time to play around with it yet. However I did a second install this morning, on a second device, but this time
spotify token
does not work and the list of commands available do not match what is shown on the README. It's as if I downloaded 2 different versions between last night and this morning.Running
npm install spotify-cli-mac -g
installs v1.2.0 I attemptednpm install spotify-cli-mac@1.1.0 -g
as well and still have the same command list.See screenshot below.