MarkdownPreview.sublime-settings

/*
    Markdown Preview default settings
*/
{
    /*
        Sets the default opener for HTML files

        default - Use the system default HTML viewer
        other - Set a full path to any executable. ex: /Applications/Google Chrome Canary.app or /Applications/Firefox.app
    */
    "browser": "default",

    /*
        Sets the parser used for building markdown to HTML.

        NOTE: The parser setting is not for the preview commands now.
        The previews have separate commands for each parser markdown.

        Warning for github API: if you have a ST2 linux build, Python is not built with SSL so it may not work

        default - The current default parser is python-markdown parser.
        markdown - Use the built-in python-markdown parser
        github - Use the github API to convert markdown, so you can use GitHub flavored Markdown, see https://help.github.com/articles/github-flavored-markdown/
    */
    "parser": "default",

    /*
        By default, Markdown Preview builds the HTML in the source directory.
        It expects the file to exist on disk.  It pops up the build output panel etc.

        If you wish to override this behavior, you can change "build_action"

        build - The default build behavior.
        browser - Preview the file in your browser.
        clipboard - Copy the HTML output to the clipboard.
        sublime - Export the HTML to a Sublime tab.
        save - Run the normal save command that outputs to the source directory.
            It will also prompt for "save as" if the file does not exit on disk.

        All the build options use the default parser defined above in "parser"
    */
    "build_action": "build",

    /*
        Enable or not mathjax support.
    */
    "enable_mathjax": false,

    /*
        Enable uml support scripts: flowchart.js and sequence-diagram.js.
    */
    "enable_uml": false,

    /*
        Enable highlighting. This enables codehilite extension if not already enabled.
    */
    "enable_highlight": false,

    /*
        Pygments support for syntax highlighting.  Controls whether codehilite extension
        will use Pygments.  If disabled, code blocks will be formatted for javascript
        highighters such as highlight.js.

        If you manually set codehilite as an included extension in "enabled_extensions",
        your settings will override this one.  To configure using pygments manually:
            "enabled_extensions": [
                "codehilite(use_pygments=False)" // <-Turn off pygments usage
            ]
    */
    "enable_pygments": true,

    /*
        Sets whether highlight JS will auto-guess raw block's syntax.
        Alternative is to to only highlight blocks where a language has
        been defined.

        Default is True (guess).

        If you manually set codehilite as an included extension in "enabled_extensions",
        your settings will override this one.  To configure language guessing manually:
            "enabled_extensions": [
                "codehilite(guess_lang=False)" // <-Turn off language guessing
            ]
    */
    "guess_language": true,

    /*
        List of enabled extensions of the selected markdown parser.

        You can get the full list of extensions at:
            * The python markdown parser, the `markdown`: http://pythonhosted.org/Markdown/extensions/index.html


        default - use the default set of extensions, see table later.
        [ "default", "def_list", ... ] - a list of extensions. Use "default" to include the default extensions.

            Parser     | "default" Values
        ------------|---------------------------
            default    | ["extra", "github", "toc", "meta", "sane_lists", "smarty", "wikilinks"]
            markdown   | ["extra", "github", "toc", "meta", "sane_lists", "smarty", "wikilinks"]
            github     | extension's values are not used.

    */
    "enabled_extensions": "default",

    /*
        Enabled parsers for the parser "select parser" command
        Available parsers: markdown, github

        When there are more than one parser in the list, Sublime will prompt
        via the quick panel for which one to use.  If there is only one, it
        will automatically run that parser.
    */
    "enabled_parsers": ["markdown", "github"],

    /*
        Custom external markdown parsers.

        "markdown_binary_map" contains key values pairs.  The key
        is name of the parser and what is used in "enabled_parsers"
        to turn on the access to the parser.  The value is an array
        containing the path to the binary and all the parameters that
        are desired.

        Multimarkdown is provided as an example below.  It's path may differ
        on your system.
    */

    "markdown_binary_map": {
        "multimarkdown": ["/usr/local/bin/multimarkdown"]
    },

    /*
        Default mode for the github Markdown parser : markdown (documents) or gfm (comments)
        see http://developer.github.com/v3/markdown/#render-an-arbitrary-markdown-document
    */
    "github_mode": "markdown",

    /*
        Enables a post process to inject header ids to ensure hrefs to headers work
    */
    "github_inject_header_ids": false,

    /*
        Uses an OAuth token when parsing markdown with GitHub API. To create one for Markdown Preview, see https://help.github.com/articles/creating-an-oauth-token-for-command-line-use.
        Warn: this secret *must not be shared* with anyone and at least you should create it with minimal scopes for security reasons.
    */
    // "github_oauth_token": "secret",

    /*
        Sets the default css file to embed in the HTML

        default - Use the builtin CSS or github CSS, depending on parser config (markdown.css or github.css)
        other - Set an absolute path or url to any css file

        Should be an array, but will take a single string to support legacy convention.
    */
    "css": ["default"],

    /*
        Allow CSS overrides

        true - Any file with matching a .markdown_filetype extension with .css will be loaded as an override
        false - Matching files ignored
    */
    "allow_css_overrides": true,

    /*
        Specify a HTML template file to render your markdown within.

        Available place holders in HTML template:
        {{ HEAD }} - would be replaced by generated stylesheets, javascripts enabled above
        {{ BODY }} - would be replaced by HTML converted from markdown

        By setting "skip_default_stylesheet" to true you can use the styles only in your HTML
        template. In most cases you should turn this setting on to have a full-featured design.

        Refer to 'customized-template-sample.html' as a show case.
    */
    // "html_template": "/ABS_PATH_TO_A_HTML_FILE",
    // "skip_default_stylesheet": true,


    /*
        Sets the JavaScript files to embed in the HTML

        Set an array of URLs or filepaths to JavaScript files. Absolute filepaths will be loaded
        into the script tag; others will be set as the `src` attribute. The order of files in the
        array is the order in which they are embedded.
    */
    // "js": ["http://example.com/script.js", "/path/to/script.js"],

    /*
        Enable or not whether parsed files will be auto-reloaded on save
    */
    "enable_autoreload": true,

    /*
        Sets the supported filetypes for auto-reload on save
    */
    "markdown_filetypes": [".md", ".markdown", ".mdown"],

    /*
        Sets a custom temporary folder for MarkdownPreview-generated HTML files. Useful if you're
        using LiveReload and don't want to use the OS default. The directory will be created if it
        doesn't exist. Relative paths are supported, and are checked against `os.path.isabs`, see
        doc: http://docs.python.org/3/library/os.path.html#os.path.isabs

        Examples: /tmp/custom_folder   (Linux/OSX - absolute path)
                    C:/TEMP/MYNOTES
                    C:\\TEMP\\MYNOTES    (Windows - absolute path, forward slash or escaped back slash)
                    build                (All OS - relative path, current dir)
                    ../build             (Linux/OSX - relative path, in parent dir)
                    ..\\build            (Windows - relative path, in parent dir)
    */
    // "path_tempfile": "/tmp/my_notes",

    /*
        Sets HTML output to a simple form:
            - No head
            - No body tags
            - ids, classes, and style are stripped out
            - Just bare minimum HTML tags and attributes
            - extension modifications included
    */
    "html_simple": false,

    /*
        Sets how image paths are handled.
        Setting is a string value: (absolute | relative | base64 | none)
            absolute: converts relative local paths to absolute
            relative: converts relative local paths to a path relative to the
                        HTML output
            base64: coverts the local file to base64 and embeds it in the HTML
            none: does nothing
    */
    "image_path_conversion": "absolute",

    /*
        Sets how file paths are handled.
        Setting is a string value: (absolute | relative | none)
            absolute: converts relative local paths to absolute
            relative: converts relative local paths to a path relative to the
                        HTML output
            none: does nothing
    */
    "file_path_conversions": "absolute",

    /*
        Sets how multimarkdown critic marks are handled.
        Setting is a string value: (accept | reject | none)
            accept: Accepts the proposed inserts and deletions (comments etc. are discarded)
            reject: Rejects the proposed inserts and deletions (comments etc. are discarded)
            none: does nothing

        Critic marks only affects "github" and "markdown" (Python Markdown).
    */
    "strip_critic_marks": "none",

    /*
        Strips the YAML front matter header and converts title to a heading
    */
    "strip_yaml_front_matter": false,

    /* do we show the panel when build with CMD+B */
    "show_panel_on_build": true,

    /* do we include the CSS when outputting HTML into a new sublime view ? */
    "embed_css_for_sublime_output": true
}