Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make commands available on files that aren't .md #18

Open
leliamesteban opened this issue Sep 18, 2019 · 1 comment
Open

Make commands available on files that aren't .md #18

leliamesteban opened this issue Sep 18, 2019 · 1 comment

Comments

@leliamesteban
Copy link

I spent quite a while figuring out why Vim didn't recognise any of the commands this plugin uses until I realised they only work if the current file has the .md limitation.

Is this a hard requirement? What settings can I modify so that it works on other files?

For example, I use markdeep which uses the file extension .md.html

Thank you for any help

@alerque
Copy link
Member

alerque commented Sep 19, 2019

It is not linked to the file extension, it has to do with the filetype that vim detects. Right now this plugin is set to inject the extra commands whenever either markdown or pandoc file types are detected. I don't see any vim support for markdeep as a file type, otherwise we could probably add it to the plugin by default. In the mean time if the ft value is something you are setting manually then you could add support for this plugin by adding a symlink in the ftplugin directory after this plugin is installed linking markdeep to markdown much like the existing pandoc link.

Alternatively if you are not actually setting the ft at all in vim and it thinks you are editing html files, then you could just set that to markdown manually:

:set ft=markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants