search

phyllisstein / Pandown

A powerful, versatile, highly Subliminal Pandoc build wrapper for ST2/3
64 stars 12 forks source link

Incompatibility with current Package Control on ST3? #6

Closed luc-j-bourhis closed 11 years ago

luc-j-bourhis commented 11 years ago

I installed Pandown with Package Control[1]. It places a Pandown.sublime-package in /Installed Packages. But reading your pandownTouchProjectConfigCommand.py, you expect os.path.join(sublime.packages_path(), 'Pandown') is an existing directory, where sublime.packages_path() is data-path/Packages. If I understand correctly, it was the policy of ST2 to expand packages there but it has changed with ST3 which prefers to keep the packages as archives in "Installed Packages". So basically, as it stands, I don't see how your code can work with ST3 and Package Control. Users shall install Pandown by hand in data-path/Packages for it to work correctly. I have no idea how to fix the package to work around that problem but at least, meanwhile, you should update the documentation to clarify that point.

Am I missing something?

[1] I installed Package Control by cloning its git repo and checking out the python3 branch: head is May 7, 158717034335b075d45fc6f13dcf2bdbdc5edf8c.

phyllisstein commented 11 years ago

Hi Luc, No, I believe that you're quite right. I'm looking into a workaround right now; for the moment, you can restore functionality immediately by saving default_pandoc_config.json as pandoc_config.json and placing it in your Packages/User directory. Thanks very much for the heads-up; with any luck I'll have it fixed tonight.

luc-j-bourhis commented 11 years ago

Pandown tries to get at some other files inside the package. The only way as I wrote is to unzip Pandown.sublime-package inside data-path/Packages. Thanks to look into this!

phyllisstein commented 11 years ago

Thanks Luc, you're correct about that, too. I'm going through the package now and rewriting the bad bits; should have a fix pushed within the hour.