sublime-strapdown-preview icon indicating copy to clipboard operation
sublime-strapdown-preview copied to clipboard

Preview Fails in ST 3

Open gooddadmike opened this issue 11 years ago • 8 comments

When I install with the package manager and hit preview, nothing comes up. When I chose preview in Sublime Text the

`<script src="///C:/Users/mike/AppData/Roaming/Sublime%20Text%203/Installed%20Packages/Strapdown%20Markdown%20Preview.sublime-package/strapdown/strapdown.js"></script>

When I check that location Strapdown%20Markdown%20Preview.sublime-package points to a file. How could this direct the browser to strapdown.js? Is it supposed to be a folder reference? Is there a settings file where I can change this?

gooddadmike avatar Jan 28 '14 20:01 gooddadmike

I am experiencing the same problem.

dainkaplan avatar Feb 28 '14 18:02 dainkaplan

Ditto. Console shows

Traceback (most recent call last): File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 543, in run_ return self.run(edit, **args) File "Strapdown Markdown Preview in /Users/adams/Library/Application Support/Sublime Text 3/Installed Packages/Strapdown Markdown Preview.sublime-package", line 101, in run AttributeError: 'module' object has no attribute 'open'

drobertadams avatar Mar 03 '14 12:03 drobertadams

I'm having the exact same problem.

yijia-zhan avatar Mar 27 '14 06:03 yijia-zhan

Me too.

yuricamara avatar Jun 04 '14 02:06 yuricamara

I have the same problem both in Windows and on Mac. If I install with Package Manager, the preview in browser does not work. If I clone the github repo into my packages folder it works fine.

Windows Console

Traceback (most recent call last):
  File "C:\Program Files\Sublime Text 3\sublime_plugin.py", line 543, in run_
    return self.run(edit, **args)
  File "Strapdown Markdown Preview in C:\Users\********\AppData\Roaming\Sublime Text 3\Installed Packages\Strapdown Markdown Preview.sublime-package", line 101, in run
AttributeError: 'module' object has no attribute 'open'

Mac Console:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 543, in run_
    return self.run(edit, **args)
  File "Strapdown Markdown Preview in /Users/********/Library/Application Support/Sublime Text 3/Installed Packages/Strapdown Markdown Preview.sublime-package", line 101, in run
AttributeError: 'module' object has no attribute 'open'

thomscode avatar Aug 27 '14 15:08 thomscode

I'm getting the same error upon attempting to preview in browser. my console spits out:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 543, in run_
    return self.run(edit, **args)
  File "Strapdown Markdown Preview in /Users/will/Library/Application Support/Sublime Text 3/Installed Packages/Strapdown Markdown Preview.sublime-package", line 101, in run
AttributeError: 'module' object has no attribute 'open'

this is the only feature which I require from this plugin (which I think is a great idea!), so I was wondering, what are the chances of a fix on this?

WillChilds-Klein avatar Jan 27 '15 20:01 WillChilds-Klein

Will, I have not seen any updates to this code or issue in several months. I don't have much hope that it will be fixed in the Package control version. However, if you download the code and manually add the package to Sublime, it has been working for me.

Hope that helps, Thom

On Jan 27, 2015, at 12:51 PM, Will Childs-Klein [email protected] wrote:

I'm getting the same error upon attempting to preview in browser. my console spits out:

Traceback (most recent call last): File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 543, in run_ return self.run(edit, **args) File "Strapdown Markdown Preview in /Users/will/Library/Application Support/Sublime Text 3/Installed Packages/Strapdown Markdown Preview.sublime-package", line 101, in run AttributeError: 'module' object has no attribute 'open' this is the only feature which I require from this plugin (which I think is a great idea!), so I was wondering, what are the chances of a fix on this?

— Reply to this email directly or view it on GitHub.

thomscode avatar Jan 27 '15 21:01 thomscode

I see, I'll try that. thanks @thomscode !

WillChilds-Klein avatar Feb 06 '15 15:02 WillChilds-Klein