Skip to content

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

@ghost

Description

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

Activity

alerque

alerque commented on Sep 19, 2019

@alerque
Member

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @alerque

        Issue actions

          Make commands available on files that aren't .md · Issue #18 · vim-pandoc/vim-markdownfootnotes