gistpad
gistpad copied to clipboard
version 0.1.8 will suppress string autocompletion in Markdown
Describe the bug
When this extension GistPad of version 0.1.8 and/or the extension :emojisense: of a recent version is enabled, string autocompletion in Markdown will be suppressed.
To Reproduce Steps to reproduce the behavior:
- Make sure GistPad of version 0.1.8 and
:emojisense:of any version disabled or uninstalled - Enable autocompletion in Markdown with below settings
{ "editor.quickSuggestions": { "comments": true, "other": true, "strings": true }, "[markdown]": { "editor.quickSuggestions": true }, } - Open any Markdown file, and the autocompletion works as the first screenshot shows, where GistPad is of version 0.1.7
- Install or enable GistPad of version 0.1.8. Alternatively, install or enable
:emojisense: - The autocompletion is now suppressed and broken, like in the second gif screenshot. You can see the string completion is suppressed almost immediately
Expected behavior Autocompletion should remain intact and completions should not be suppressed.
Screenshots

Desktop (please complete the following information):
- VS Code Version v1.47.2
- GistPad Version v0.1.8
Additional context
- I rely on autocompletion heavily when writing Markdown
- Since
:emojisense:is shipped along with this extension and can also be the culprit, it is mentioned too - Annoyingly, the extension "GitHub Pull Requests and Issues" can also be the culprit under some circumstances.
@tangentyh Hmm, I’m sorry you ran into this! Just to confirm: does this issue only occur if emojisense is enabled? If so, then it sounds like I should like I should remove that dependency.
@lostintangent both actually. This problem occurs if any of the below:
- GistPad v0.1.8 is enabled (v0.1.7 is fine) or
- emojisense is enabled or
- both emojisense and GistPad v0.1.8 are enabled
I am seeing the same, but emojisense on its own is fine. It only breaks when GistPad is enabled.
Before I dive into the code, is there a place you would suggest looking to debug?
Edit: After a quick glance, perhaps completionProvider is conflicting with vscode-markdown-notes (which Foam is using)?
I'm seeing the same thin across vscode-markdown-notes and gistpad (no emojisense installed) as of 11/15/2020.
@da5is Out of curiosity: do you see this behavior if you disable GistPad, but enable vscode-markdown-notes? I’m just curious if it’s a GistPad issue, or maybe an issue with VS Code and extensions that contribute Markdown completion support.
I don't see the issue if GistPad is disabled but vscode-markdown-notes is enabled - just when GistPad is enabled. Odd.
Closing this since I haven't seen any reports of the issue in a while, and I'm not sure it still repros. Please feel free to re-open it if you're still encountering this problem