Transform your source code into easy to publish Markdown
- Total 252
- Win 134
- OS X 83
- Linux 35
|Jan 22||Jan 21||Jan 20||Jan 19||Jan 18||Jan 17||Jan 16||Jan 15||Jan 14||Jan 13||Jan 12||Jan 11||Jan 10||Jan 9||Jan 8||Jan 7||Jan 6||Jan 5||Jan 4||Jan 3||Jan 2||Jan 1||Dec 31||Dec 30||Dec 29||Dec 28||Dec 27||Dec 26||Dec 25||Dec 24||Dec 23||Dec 22||Dec 21||Dec 20||Dec 19||Dec 18||Dec 17||Dec 16||Dec 15||Dec 14||Dec 13||Dec 12||Dec 11||Dec 10||Dec 9|
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.