This repository has been archived by the owner on Mar 17, 2020. It is now read-only.
Use config.post.default_markup to specify extension for created post files. #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EnigmaCurry
added a commit
that referenced
this pull request
May 3, 2012
Use config.post.default_markup to specify extension for created post files.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
blogofile blog post createcommand is hardcoded to create a file with the extension.markdown. This change uses a new config option,blog.post.default_markupto permit an alternative to be specified. I use RST markup, so have setblog.post.default_markup = 'rst'in my_config.pyfile. Ifblog.post.default_markupis not set the default remains.markdown.This pull requests also contains a few compulsive whitespace and PEP8 cleanup changes. Apologies for mixing them with feature changes.