-
Notifications
You must be signed in to change notification settings - Fork 10
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
Autocomplete Suggestions never pop up, even when clicking ctrl+space #5
Comments
That sounds troubling, but at least the log says that the file is being parsed.
If it still doesn't work, then I'll add a few more log events so that we can figure out whats going wrong. |
I tried the sample bib file and it still does not work, neither does browser work. Sorry for the trouble! |
I can't reproduce the problem.
Anyways, I added a new log event in the recent release (0.3.4) which might help us figure out what's going wrong.
|
Had the same issue today. |
@vjagodnik If you have time, could you tell me what the output log shows when using version 0.4? Specifically: does it parse the bib file and whether it mentions anything when trying to add a citation. |
No. It just shows the words used in md file. |
Ok, this is somewhat frustrating now. |
No worries. It's great to hear that it works! |
I have the same problem and I follow the suggestions you give above @notZaki . It turns out to be a very strange problem. I started from a fresh install of vs code on mac os and pandoc citer is the only plugin I installed. I followed all steps until the step to open a blank markdown file and |
Thanks for the insight @joezhouchenye |
Same issue here! LMK if there is anything I can do to help |
"[markdown]": {
"editor.quickSuggestions": true,
}, by default, markdown won't provide any suggestion untill this setting is turned up. |
also, remember to add |
Thanks for the tips @ilcpm! @okbel, what does the output log show? That would help narrow down whether the issue is with intellisense or with finding/parsing the bib file. I will add that I have recently noticed intellisense not working for citations on a few occasions. It seems to happen after every vscode update, but I haven't yet been able to figure out why. The log says that the extension was loaded and that the bib file was parsed, but the citations still don't show up. Reloading the window (or closing/reopening vscode) seems to fix it. |
adding the configuration @ilcpm suggested and restarting VSCode worked for me on v0.70 |
Configuration @ilcpm suggested also worked for me |
@ilcpm is right, just add the code to your |
Something strange happens. When I restart my vscode, the code by @ilcpm was replaced by
and the PandocCiter stopped working. |
I am having the same issue with @ autocomplte not working using v0.9.3 on macos. I disabled almost every extension in my workspace (left the color themes and some others active). I get basically the same behavior as others - output log says the .bib file is found and parsed, but @ does not trigger anything. Tried a .bib file with one single entry and a more complex one. Like @THyanNK mentioned, the boolean is no longer an option with "[markdown]": {"editor.quickSuggestions": ... so I tried adjusting the three available options and it didn't matter. Hope someone can find a solution! |
Just add it again
|
I should have been more specific about what I tried. Basically I tried everything in the three separate issues on this topic, including the hack you suggested to put the old and new editor.quickSuggestions syntax in settings.json, but it did not work. Referring to the suggested test steps, at the point where typing @ should bring up Showing suggestions I get nothing. Some things I tried: Note that "Tried it all again" means using the two editor.quickSuggestions syntaxes, using a simple test.bib file with only one entry, reloading vscode, opening a new md file, typing @, then adding bibliography header, typing @, and so on (all the various suggestions). One thing I noticed that I don't understand is the following setting in my global user settings (not workspace): Hovering over this the popup says "automaticallyOverrodeDefaultValue: (DO NOT SET THIS MANUALLY) IntelliCode will set this to record that configuration has been automatically modified to override a default value" I have no idea when or why this was set automatically by IntelliCode or if this is relevant at all, but as mentioned, I disabled my entire settings.json file and did not work. |
I'm having what I think may be the same issue. If I set I do get other inline suggestions from other extensions, etc. without issue, however. |
I just had a chance to try this out on a Windows machine tonight, and I do get completions using the inline view setting there. However, I still get nothing on macOS. I'm using the latest versions of VSCode and the extension on both. I've tried the logging, and it reports that it's showing the correct number of entries/results, but the popup never shows. |
I just installed this and there seem to be no errors during installation. It just doesn't work for me. I also updated VSCode in case it was an issue with versions.Any ideas why this isn't working? I have the .bib file in the same folder so I have
and also set a default .bib file just in case.
This is the output log so it seems to see my .bib file
Thoughts? Thanks for making this package.
The text was updated successfully, but these errors were encountered: