From 8c34d810af95fae0ef846f54370a8c88bfab7123 Mon Sep 17 00:00:00 2001 From: "netop://ウィビ" Date: Sat, 11 Apr 2026 14:24:49 -0700 Subject: initial commit --- remarks/WR-001.txt | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 remarks/WR-001.txt (limited to 'remarks/WR-001.txt') diff --git a/remarks/WR-001.txt b/remarks/WR-001.txt new file mode 100644 index 0000000..fca8767 --- /dev/null +++ b/remarks/WR-001.txt @@ -0,0 +1,43 @@ + + + + + + + +Document: WR-001 P. Webb + 2024.11.04 + + Package Control issues? Here's a fix! + +Body + + I recently updated my computers to macOS Sequoia and Sublime Text + went on the fritz. Being my IDE of choice, I spent the better part of + two days trying to get my plugins working. Thankfully, a year-old + issue on Github[1][2] got everything working again: + + > FOR ANYONE STILL STRUGGLING WITH THIS PROBLEM + > Maintainer @deathaxe has explained several times in this thread + > that you can solve the problem simply by downloading the latest + > edition[3] (4.0+) of Package Control! + + Clicking the second link will download + "Package.Control.sublime-package" but we need to replace the period + with a space ("Package Control.sublime-package"). Then we need to + place this file in the correct place. + + The quickest method is to open Sublime Text and navigate to + Settings… → Browse Packages… to open that directory in Finder. Go one + level up, navigate to "Installed Packages," and move that + Package Control.sublime-package file there. + + Restart Sublime Text and you should be back in business. + + 🕸 + +References + + [1]