Incompatibility with other extensions
See original GitHub issueI’m unsure if this is an issue which can be resolved. However, the other major extensions for markdown (BibTeX autocomplete, autocomplete-plus, and nvatom) do not seem to detect the language “Markdown” as suitable. It’s quite frustrating as I am unsure of where all these extensions have compatibility issues, but it appear they are all based off the original gfm package.
Are you able to integrate a method such that other extensions which depend on launguage-gfm
simply revert to your package? Or do those extensions need to change to you? It’s pretty game changing for me, because I would rather have nvatom, BibTeX autocomplete, and simpler language detection in exchange for slightly less glossy highlighting.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Incompatibility with other extensions
When two extensions are incompatible with each other it is the responsibility of both parties to find a solution. At Mailtrack we work...
Read more >Chrome incompatibilities - Mozilla - MDN Web Docs
Extensions built with WebExtension APIs are designed to be compatible with Chrome and Opera extensions. As far as possible, extensions ...
Read more >Virtru compatibility with other Chrome extensions
Virtru does not officially guarantee compatibility with other Chrome extensions. However, most plugins should be compatible and work ...
Read more >Incompatible Browser Extensions - HelpDocs Support
Incompatible Browser Extensions ... Here's a list of the extensions we know interfere and how you can disable them when you're writing on...
Read more >09/Nov/22 | List of incompatible extensions + Guide
Chrome APIs (depends on): Some extensions are heavily bind with google browser and call specific APIs that chromium - Vivaldi and most other ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think those packages need a small change. Documents are either detected by their extension or a base grammar scope. I’ve changed the latter from
source.gfm
totext.md
and it’s possible that those packages tie in to it. I think that’s why it might not work. If you could link all affected packages here (preferably a link to the repo), I’ll have a look.Good luck! Let me know if I can help.