Now that I think about it, this doesn't cover some other cases.  I'll fix
those as I come across them.

Move indent related settings from syntax to index.
Fix #126

Use just markdown as filetype.

. for multiple filetypes does not work with autocmd.

There seems to be no known workaround:
http://vi.stackexchange.com/questions/4893

This is a breaking change as it would break user scripts
who used autocmd, but we have already broken them
with this compound filetype, so let's just finish the job.

Semi-reverses: https://github.com/plasticboy/vim-markdown/pull/217

Add the indent part of the plugin to the registry

swap mkd to markdown

Signed-off-by: yuexin <yuecn41@gmail.com>

Use compound filetype for plugins using "markdown"

README.md: add a section about issue reporting

Build latest vim quickly from git mirror.

* Executes test against travis package vim & latest 7.4.x
* Fixes #201

Version aware netrw browseX call

Fix typo plugging

Document <Plug>Markdown_OpenUrlUnderCursor

Add TOC to README

Allow users to disable individual maps with hasmapto checks

Update Markdown_GetUrlForPosition function b: to s:

Improve style of ftplugin/mkd.vim

- remove Markdown_ prefix from s: functions
- always add one empty line between commands and methods

Remove parenthesis from <Plug> maps

gx works from anywhere inside Markdown links

Fix #99.

Change the README h1 to "Vim Markdown"

Improve README formatting

Add test for Toc nomodifiable #170

Remove nosmartindent: indentexpr overrules it.

Prevent setting other buffers to nomodifiable.

Fix #169

Add tilde-fenced code blocks.

Remove automatic setting of foldlevel

Vim already has a well known way of dealing with this:
let's not create another configuration which only raises
the entry barrier.

Undo noremap, add header map tests

Reverts #141 which @cirosantilli wrongfully merged.

Add regression tests that would have prevented that.

Correction pointed out by @shanesmith at #147.

Use `noremap` for mappings