I thought it had to do with Sublime Text but, Marked seems to be crashing
each time I run it and open a file. It crashes hard, every time. Can you
help? I reinstalled from App store and that didn't help!
p.s. This issue will be resolved in the next major release by a) reducing dependency on Ruby, b) searching for Ruby in System/Frameworks and c) providing better error catching if the binary isn't found.
on 18 Mar, 2015 03:52 PM
As someone who has never set up a build system in Sublime Text, I was confused by the instructions given. It's one of those (many) things that's simple if you know how, but it took me about an hour of trawling the internet for different sets of instructions.
For others in my boat, here are step by step instructions to make Sublime Text 3 preview documents in Marked 2.
Assuming Marked 2 is installed, everything is done inside Sublime Text 3.
In Sublime Text 3, click on:
Tools > Build System > New Build System
You'll be presented with a blank document containing the following text:
Replace the text with this:
"shell_cmd": "open -a 'marked 2' \"$file\""
Save the file. You'll be prompted for a filename - the default is untitled.sublime-build - change "untitled" to Marked2
This adds the option to use Marked 2 to Sublime Text 3's build options. (As far as I could see, no restart was required.)
Now click Tools>Build System and change your default Build System to Marked2, which should now be listed at the bottom.
After that, pressing Command-B (or clicking Tools>Build) should automatically open the current document in Marked 2.
As addendum to Duncan's instructions, you have to save the file before you build it. I had a test file I created and Duncan's instructions "weren't working." When I got an error message from Marked2 that there was no file for it to display, I tried saving the test file. BAM! Worked like a charm!
On behalf of MultiMarkdown writers who aren't developers, thank you, Duncan!