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
Error after installing via Package Control #46
Comments
Same here on Windows. |
I just got this error on Sublime Text after a fresh install of this via package control. I can confirm that the workaround (from #46 (comment) ) does seems to work. I was able to do it by modifying the zipped up |
Workaround worked for me as well. Unzip, change the file, rezip as EDIT: Looks to be same issue as #34 Maybe the Package Control package just needs to be updated? Latest is 1.4.5 (both on GitHub and Package Control), but the issue was fixed after the latest version. |
I do not encounter the problem when cloning the repo into |
For anyone wondering: Sublime packages are zip archives, as you’ll find by running #!/usr/bin/env -S bash -euET -o pipefail
shopt -s inherit_errexit 2>/dev/null || true
ZIP_DEST="$(mktemp -d)"
ZIP_SRC="$HOME/Library/Application Support/Sublime Text 3/Installed Packages/Zig Language.sublime-package"
SRC_FILE=Support/Comments.tmPreferences
DEST_FILE=Preferences/Comments.tmPreferences
printf 'Unarchiving "%s"\n' "$(basename "$ZIP_SRC")"
unzip "$ZIP_SRC" {Preferences,Support}/Comments.tmPreferences -d "$ZIP_DEST"
printf '\nOverwriting "%s" with the contents of "%s"\n' "$DEST_FILE" "$SRC_FILE"
ln -fv "$ZIP_DEST/$SRC_FILE" "$ZIP_DEST/$DEST_FILE"
printf '\nRe-zipping "%s" with the new "%s"\n' "$(basename "$ZIP_SRC")" "$DEST_FILE"
pushd "$ZIP_DEST"
zip -Tv -b "$ZIP_DEST" "$ZIP_SRC" Preferences/Comments.tmPreferences
popd
printf '\nRemoving temporary files\n'
rm -fRv "$ZIP_DEST" |
I keep getting this error popup after installing the plugin via package control:
The error seems to happen when I interact with Package Control (add/remove packages). Syntax highlighting still works, so it's not a big deal.
I'm using the master branch of Package Control, and the beta version of macOS 11 – so this could definitely be an issue on my end and I just need to wait. Is anyone else having this happen?
The text was updated successfully, but these errors were encountered: