bordaigorl / sublime-markdown-editing

Powerful Markdown package for Sublime Text with better syntax understanding and good color schemes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Difficulty setting up

fredcallaway opened this issue · comments

What is the proper way to set up this package? I tried removing MarkdownEditing via package control and then cloning into /Packages with git. This gave me a missing theme file error. After some mucking about (to be honest, I'm not sure what I did), I have managed to get things to work, but there's no pandoc-specific syntax. Any help would be greatly appreciated!

I think the "missing theme" problem is common to every fork of Markdown Editing, just restart ST and it should be fine.
You should find a "Markdown Pandoc" entry in the Syntax Menu.
Some of Pandoc's extras are highlighted but this is by no means complete.

I swear I tried looking for a pandoc syntax earlier… Anyway, I've got it working now, but the theme doesn't automatically switch to markdown editing (as it does with normal markdown syntax. Any idea what to do here?

Also, I'd like to contribute to this project, and I think have regexes that could define some useful scopes—the first thing that jumps out at me is that currently the citation scope only captures citations that lead with @, missing e.g. [c.f. @chater09]. However I'm unfamiliar with the syntax that sublime uses (or their basic file structures as you can see above). Can you recommend a resource to learn the basics of sublime development? I think it's about time that I contribute to this community that I've gained so much from.

Cheers,
Fred

On Oct 16, 2014, at 6:46 AM, bordaigorl notifications@github.com wrote:

I think the "missing theme" problem is common to every fork of Markdown Editing, just restart ST and it should be fine.
You should find a "Markdown Pandoc" entry in the Syntax Menu.
Some of Pandoc's extras are highlighted but this is by no means complete.


Reply to this email directly or view it on GitHub #1 (comment).

Hey @fredcallaway it would be great if you could contribute!
There are unofficial docs explaining the basics, TextMate docs — Sublime Text based its theming on it — documenting scope selectors and naming conventions.
Personally, I learned a lot by just reading other package's syntax definitions.
If you find all this is too much work you are welcome to draft a new page in the wiki (it is public) with your proposal, or fork the repo and submit a partial pull request to start the discussion.

As for the syntax switching, have you tried using the Syntax menu at the bottom right (there is an "Open all with current extension as..." entry)?

Thanks for the pointers; I'll look into those.

Regarding my own difficulties, it's not the syntax switching but rather the automatic association of the markdown .tmTheme with the Markdown Pandoc syntax. If I set the syntax of a file to Markdown, the color scheme automatically switches to my markdown theme, but not so for Markdown Pandoc. I think this is because there is no .sublime-settings for the Markdown Pandoc syntax (as there is for markdown, multimarkdwon, and GFM).

Cheers,
Fred

On Oct 16, 2014, at 10:28 AM, bordaigorl notifications@github.com wrote:

Hey @fredcallaway https://github.com/fredcallaway it would be great if you could contribute!
There are unofficial docs http://sublime-text-unofficial-documentation.readthedocs.org/en/latest/extensibility/syntaxdefs.html explaining the basics, TextMate docs — Sublime Text based its theming on it — documenting scope selectors http://manual.macromates.com/en/scope_selectors#scope_selectors and naming conventions http://manual.macromates.com/en/language_grammars#naming_conventions.
Personally, I learned a lot by just reading other package's syntax definitions.
If you find all this is too much work you are welcome to draft a new page in the wiki (it is public) with your proposal, or fork the repo and submit a partial pull request to start the discussion.

As for the syntax switching, have you tried using the Syntax menu at the bottom right (there is an "Open all with current extension as..." entry)?


Reply to this email directly or view it on GitHub #1 (comment).

Ah! Well you can set the color theme in the "Syntax Specific" settings:
Open a markdown file, select the Pandoc syntax then go to Preferences > Settings - More > Syntax Specific

Of course! Thanks for all your help.

Cheers,
Fred

On Oct 16, 2014, at 11:04 AM, bordaigorl notifications@github.com wrote:

Ah! Well you can set the color theme in the "Syntax Specific" settings:
Open a markdown file, select the Pandoc syntax then go to Preferences > Settings - More > Syntax Specific


Reply to this email directly or view it on GitHub #1 (comment).