You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not super familiar with Sublime Text plugins, but some quick Googling pointed at /Users/<username>/Library/Application Support/Sublime Text 3/Packages/User/ (I'm on OSX).
Apparently if you git clone https://margo.sh/GoSublime into that directory, menu items show up but don't work, and margo never gets set up correctly. After banging my head against the wall for a while, I tried the same git clone up a directory, in /Users/<username>/Library/Application Support/Sublime Text 3/Packages, which immediately worked, and as a cherry on top created a GoSublime subdirectory of /Users/<username>/Library/Application Support/Sublime Text 3/Packages/User/ with the layout the rest of the docs implied.
This narrative is the long way of asking, any reason not to explicit put the correct plugin parent directory into https://margo.sh/b/migrate/ for each supported platform?
The text was updated successfully, but these errors were encountered:
I'm not super familiar with Sublime Text plugins, but some quick Googling pointed at
/Users/<username>/Library/Application Support/Sublime Text 3/Packages/User/
(I'm on OSX).Apparently if you
git clone https://margo.sh/GoSublime
into that directory, menu items show up but don't work, andmargo
never gets set up correctly. After banging my head against the wall for a while, I tried the samegit clone
up a directory, in/Users/<username>/Library/Application Support/Sublime Text 3/Packages
, which immediately worked, and as a cherry on top created aGoSublime
subdirectory of/Users/<username>/Library/Application Support/Sublime Text 3/Packages/User/
with the layout the rest of the docs implied.This narrative is the long way of asking, any reason not to explicit put the correct plugin parent directory into https://margo.sh/b/migrate/ for each supported platform?
The text was updated successfully, but these errors were encountered: