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

MarkDownFile not work! #6

Closed
kehehee1 opened this issue Jul 3, 2017 · 5 comments
Closed

MarkDownFile not work! #6

kehehee1 opened this issue Jul 3, 2017 · 5 comments

Comments

@kehehee1
Copy link

kehehee1 commented Jul 3, 2017

I install this plugin. When I open a markdown file, it just can't show word suggestions. But when I open a text file, it works fine. Help!

After tried a few times, I found that if set setting like below, it worked finaly.

"[markdown]": {
    "editor.quickSuggestions": true
@atishay
Copy link
Owner

atishay commented Jul 12, 2017

Thanks for the information. I will add this information to the Readme

@atishay
Copy link
Owner

atishay commented Aug 7, 2017

Added this information to the readme

@atishay atishay closed this as completed Aug 7, 2017
@W4RH4WK
Copy link

W4RH4WK commented Sep 30, 2017

Hey there, did you change any of the default configurations lately? At the moment, the extension does not take the regular editor.quickSuggestions option into account for Markdown.

I typically have quick suggestions disabled as I bring them up only when I need them. But today I noticed that they are popping up in Markdown files due to this extension while not having quick suggestions enabled. I have only disabled them toplevel not specifically for Markdown.

If I also add the following entry to my config, quick suggestions are also disabled for markdown:

    "[markdown]": {
        "editor.quickSuggestions": {
            "other": false,
            "comments": false,
            "strings": false
        }
    }

@atishay
Copy link
Owner

atishay commented Sep 30, 2017

Yes. I added markdown to the default list.

@W4RH4WK
Copy link

W4RH4WK commented Sep 30, 2017

Okay, I still think this should not be necessary but it seems to be an issue with VSCode rather than this extension that the special handling for Markdown is necessary.

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

3 participants