Just a kind suggestion: update the example of launching preview using chrome in OS X

[ashfinal]

I've tried the new version OmniMarkupPreviewer. Glad to see Markdown's strikeout and subscript can work well at the same time(Before that if the two are loaded, only strikeout can work ), and jquery.min.map problem also been solved.

At the same time, previewing markdown in Safari is a little disturbing. Because Safari continuously scrolls up and down as you type in ST3, which makes you almost cannot preview. Finally I decided to give chrome a try, and the result is exciting. It works perfect with any problems! But when I followed the example of launching preview using chrome in default OmniMarkupPreviewer.sublime-settings file, which told me to set browser_command to ["open", "-a", "chrome", "{url}"], it didn't launch chrome(actually nothing happened). And finally I found ["open", "-a", "Google Chrome", "{url}"] worked well for me ...

If you can fix the Safari issue, that will be best. :) Otherwise, chrome browser seems to be the better choice. And please update the example of launching preview using chrome in OS X. That may help a lot of people(In last few days I've been used Safari to preview and endure the terrible scrolling).

Thanks for your awesome app! :)

[ashfinal]

I found why strikeout and subscript can't work well at the same time before.

Actually I made a mistake. When using default github theme they can work together. But when using your own theme, you need to place customized css&template files into ${packages}/User/OmniMarkupPreviewer/ folder, which is recommended. If you unfortunately place your files into OmniMarkupPreviewer installed folder(~//Library/Application\ Support/Sublime\ Text\ 3/Packages/OmniMarkupPreviewer/), it will result Markdown's strikeout and subscript can work well together.

Sorry for bothering.

[timonwong]

@ashfinal Thanks for you comprehensive information, but I can't reproduce it on OSX Safari, does your markdown contains any special elements, large images, for example?

[ashfinal]

Thank you for reply. No special elements, Not too much images(4-5 pieces), and the resolution is all below 600x600. Safari works well only when have one page to render, if your markdown is over than one page. You continue typing in ST, Safari will scroll up then quickly down. You type a few character, it scroll up and then down … so on and so on. Chrome don't have this problem. It scrolls smoothly. I think maybe it's because Safari's render strategy is different? BTW, I'm on Yosemite 10.10.2 Safari 8.0.3 Anyway, Chrome works well. So far, that's enough for me. : ) If you still want to figure what's happening, someday I can give you a screencast.

[vongoh]

When using this browser_command setting in the Preferences -- where do we find the specific name of the browser that will get the setting to work?

ie. "browser_command": ["open", "-a", "WHERE DO WE FIND BROWSER NAMES THAT WILL WORK", "{url}"],

I'm on Win10 trying to target Firefox Development Edition .. thanks