-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spicetify-cli: Some scripts are not recognised as cmdlet, scripts, ... #66
Comments
@jacob-thanh See https://spicetify.app/docs/getting-started/advanced-installation#scoop. Spicetify is already in the official repos #65 (comment), do not use this bucket. |
@TheRandomLabs You may want to consider cutting this package if the official repos contain spicetify in the same capacity, especially with the compile/install errors yours has? Just an idea. |
@Ama1999 TheRandomLabs has been absent for over a year, and everything here is just run by CI now. This is why the Nonportable bucket has been mirrored to the official org instead of being transferred (ScoopInstaller/Nonportable#1) |
@sitiom Ah okay. Thanks for letting me know! |
As @itsmeboy0 suggests, I recommend just using spicetify-cli from the official buckets now. The spicetify-marketplace custom app is great and extensions/themes installed from there auto-update. |
When I first installed and later updated this bucket through scoop, I got this error message:
Basically it's not in path, and failed the rest of the installation process.
It seems that all the scripts from this bucket's
scripts folder
are not copied into wherespicetify-cli
is installed. I did a manually fix by copying all scripts into where it's needed, but each update is troublesome. So I submit a new issue.This error may happened because there is another
bucket (main)
which also containsspicetify-cli
, and this line inyour spicetify-cli
:Without
find_manifest($app, $bucket)
specifying which bucket, it's set to default as main bucket, whose script folder does not contains necessary scripts likeinit-spicetify-config-and-apply.ps1
,spicetify-apply.ps1
, ... and thefollowing line
fail, never made it into
spicetify-cli
installation directory.I suggest changing that line into
as
both will be passed as array into
$app
param.I'm sorry for the verbosity, hope this help anyone who encounter the same problem as I did.
The text was updated successfully, but these errors were encountered: