Transform your source code into easy to publish Markdown
- Total 280
- Win 152
- OS X 86
- Linux 42
|Jun 16||Jun 15||Jun 14||Jun 13||Jun 12||Jun 11||Jun 10||Jun 9||Jun 8||Jun 7||Jun 6||Jun 5||Jun 4||Jun 3||Jun 2||Jun 1||May 31||May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3|
SourceDown plugin for Sublime Text
Convert your commented scripts into Markdown documents. Can be useful for blog/forum posts, tutorials, basic literate programming/scripting.
The comments get uncommented and the code gets fenced/indented. Your comments are copied verbatim so if they contain valid Markdown it will be rendered correctly. The package supports any language supported by Sublime Text (it uses scopes to detect comments).
- Install Sublime Text
- Install the plugin either:
- with **Package Control** (recommended): see <https://sublime.wbond.net/docs/usage>, or - **manually**: by cloning this repository in your Sublime Text Package directory
source_down command transforms the contents of the current view into a Markdown file containing code snippets as raw text and comments as main text.
# # This is an example # # This `script` is *awesome*! # Just run it with # # > python awesome.py # # And enjoy! print("awesome") # TODO: add functionality
is turned into
# This is an example This `script` is *awesome*! Just run it with > python awesome.py And enjoy! ```python print("awesome") ``` TODO: add functionality
Which in turn can be compiled to
This is an example
scriptis awesome! Just run it with> python awesome.py
TODO: add functionality
Use the fenced GFM syntax for code snippets. If the snippet contains backticks than the fence will be extended until it is not ambiguous where it ends (see Pandoc).
This only processes the comments for producing the Markdown version.
Line comments are the ones starting with a marker and ending with the end of the line. This setting can take the values:
"all": all line comments will be converted to Markdown text;
"none": all line comments will be left as comments in the raw code block they belong to;
"lonely": only the “standalone” line comments, i.e. the ones taking the full line, will be converted.
This setting controls whether the block comments (the ones with start and end delimiters) are converted to Markdown text or left as comments in the raw code block they belong to.
Comments indented at a level greater than the one indicated will be kept as comments in a raw code block.
If true, the raw code blocks generated from code snippets will be deindented.
If true, the Markdown text extracted from comments will be deindented.
If true, the indentation level will take in account where the first line of a block comment starts. For example
a = 0 /* The following line will be deindented to level 0 */
gets converted to
```c a = 0 ``` The following line will be deindented to level 0
This is the file extension associated to Markdown files.