Provide option to disable default mappings about vim-textobj-markdown

[coachshea]

Thank you for the suggestion. I'll take a look as soon as I can.

[mawkler]

Also it would be nice if there were a setting one could use to easier remap for instance f/F. Right now if I want to use c/C ('c' for 'code') instead of f/F I would have to do the following:

augroup markdown
  autocmd!
  autocmd FileType markdown omap <buffer> ac <plug>(textobj-markdown-chunk-a)
  autocmd FileType markdown xmap <buffer> ac <plug>(textobj-markdown-chunk-a)
  autocmd FileType markdown omap <buffer> ic <plug>(textobj-markdown-chunk-i)
  autocmd FileType markdown xmap <buffer> ic <plug>(textobj-markdown-chunk-i)
  autocmd FileType markdown omap <buffer> aC <plug>(textobj-markdown-Bchunk-a)
  autocmd FileType markdown xmap <buffer> aC <plug>(textobj-markdown-Bchunk-a)
  autocmd FileType markdown omap <buffer> iC <plug>(textobj-markdown-Bchunk-i)
  autocmd FileType markdown xmap <buffer> iC <plug>(textobj-markdown-Bchunk-i)
augroup END

which is quite a few lines.

It would be nice if there were a setting that could be set like so:

let g:textobj_markdown_fence_mapping = ['c', 'C']

where the first element remaps f, and the second remaps F, or something similar.

And an equivalent one could exist for "text text objects", i.e. m/M:

let g:textobj_markdown_text_mapping = ['t', 'T']

Also, I just realized that there already is a setting for disabling the default mappings: let g:__textobj_markdown_no_mappings = 1. However, it's only mentioned in the README but not in the helpfiles and that's why I missed it. Perhaps it should be mentioned in the helpfiles as well :)