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

added mdx filetype identifier #1679

Merged
merged 2 commits into from Mar 23, 2020
Merged

added mdx filetype identifier #1679

merged 2 commits into from Mar 23, 2020

Conversation

onichandame
Copy link
Contributor

Problem

As I tried to transplant a vscode plugin, activationEvents does not trigger on opening mdx files.

Cause

mdx is not a built-in filetype of vscode language server at the moment.

The contributes.languages feature of allows vscode extensions to define their own filetype, i.e. extensions mapped to language identifier. Therefore vscode-mdx works fine without the official support of mdx filetype from vscode.

However coc.nvim is lack of this feature at the moment.

Fix

I will eventually try to implement this feature. But I wish to focus on the original problem, which is to transplant vscode-mdx to coc. So a dirty and temporary workaround is made.

The change has been kept minimal. Please check if anything will be broken by this PR.

@fannheyward fannheyward merged commit 7192266 into neoclide:master Mar 23, 2020
chemzqm added a commit that referenced this pull request Mar 24, 2020
@chemzqm
Copy link
Member

chemzqm commented Mar 24, 2020

Use g:coc_filetype_map instead.

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

Successfully merging this pull request may close these issues.

None yet

3 participants