Skip to content
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

Package Path on OSX #86

Open
nfarrar opened this issue Oct 11, 2015 · 2 comments
Open

Package Path on OSX #86

nfarrar opened this issue Oct 11, 2015 · 2 comments

Comments

@nfarrar
Copy link

nfarrar commented Oct 11, 2015

So I've been trying to get more than just the basic snippets working. I can't get any of the advanced features to run. Out of the box, none of the keymaps work. I messed around with it a bit and I think I know why it's not working on OSX (I assume this doesn't work for anyone).

  • I copied the packages Default (OSX).sublime-keymap to Packages/User/Default (OSX).sublime-keymap. Once I did that, some of the very basic features work.
  • I opened up the console, and tried some of the table keybindings - and the log starts filling up with:
Unable to open /Users/nfarrar/Library/Application Support/Sublime Text 3/Packages/sublime-rst-completion/sublime-rst-completion.sublime-settings
Unable to open /Users/nfarrar/Library/Application Support/Sublime Text 3/Packages/sublime-rst-completion/Default (OSX).sublime-keymap

So - I went and checked - and sure enough, the files are not there. In fact, there is no 'sublime-rst-completion' directory at all. I think this issue may have to do with either of the following two things (I've never built a sublime text plugin, so i'm stabbing in the dark here):

  1. The way you're referencing the package path doesn't look the way it's commonly done. I looked up the API - and checked a couple other plugins ... and they were using specific API calls to get the paths - I'm not sure, but I'm guessing that maybe these are hooked by package control to provide the correct paths (guessing).
  2. Package control installs packages as "packed" .sublime-package files by default (https://packagecontrol.io/docs/customizing_packages) - unless you put a .no-sublime-package in the root of the repository.

So - git cloned the plugin into my packages directory, restarted sublime - and now some of the keymaps are working, however I think there are some other issues, specifically to do with the keymaps that are set for OSX:

If you’re developing a package, keep this in mind:

Ctrl+Alt+ should never be used in any Windows key bindings.
Option+ should never be used in any OS X key bindings.
In both cases, the user’s ability to insert non-ASCII characters would be compromised otherwise.

Key bindings in a keymap file are evaluated from the bottom to the top. The first matching context wins.

from the unofficial documentation

@cadu-leite
Copy link

well, I had the same issues,
and thanks to @nfarrar I coud get some features working... .
and I belive the 2 tips @nfarrar give, will do the job.

anf thanks to the app. usefull.

@pauricthelodger
Copy link

Similar situation here (on Linux)

sublime-rst-completion is being installed into the Installed Packages directory though Package Control seems to only be looking in Packages for it? Also, it only affects viewing the settings and key-bindings from the Package Control options as the functionality of the package is still there.

Unable to open /home/padraic/.config/sublime-text-3/Packages/sublime-rst-completion/sublime-rst-completion.sublime-settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants