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

Since VSCode vs 1.6.0 - snippet options not being chosen by default when hitting the tab key #16

Closed
BrandonRice opened this issue Oct 13, 2016 · 3 comments

Comments

@BrandonRice
Copy link

  • VSCode Version: Code 1.6.0 (e52fb0bc87e6f5c8f144e172639891d8d8c9aa55, 2016-10-10T18:37:40.189Z)
  • OS Version: Windows_NT ia32 10.0.14393
  • Extensions: abusaidm.html-snippets-0.0.17, anseki.vscode-color-0.1.11, asp, bradgashler.htmltagwrap-0.0.3, ecmel.vscode-html-css-0.0.28, eg2.vscode-npm-script-0.0.20, fabianlauer.vs-code-xml-format-0.1.2, HookyQR.beautify-0.4.0, MattiasPernhult.vscode-todo-0.8.0, ms-vscode.Theme-3024Kit-0.1.1, msjsdiag.debugger-for-chrome-1.1.0, robertohuertasm.vscode-icons-3.0.4, seanmcbreen.Spell-0.8.6, tron.asp-0.0.1, wcwhitehead.bootstrap-3-snippets-0.0.7, xabikos.JavaScriptSnippets-1.2.0, Zignd.html-css-class-completion-1.0.3

Steps to reproduce:

  1. Type any tag
  2. When the snippet selector comes up, the correct auto-complete snippet would be at the top of the list but now I have to hit the up arrow on my keypad to get it to work correctly.

Demonstration video:

2016-10-13_09-45-50

@cottrellio
Copy link

I just fixed this by sorting the snippets to appear at the top of the suggestions menu. I don't know if you're having the same problem I was, but it's worth a try.

Try adding "editor.snippetSuggestions": "top", to your settings.

@BrandonRice
Copy link
Author

Yes! This worked for me! Thank you @cottrellio !!

@abusaidm
Copy link
Owner

Hello @BrandonRice
this is a late reply, since you got this resolved by @cottrellio , I will close this issue. I can't do much in the snippet code because vscode takes snippets as secondary priority by default, the solution @cottrellio provided is the most accurate one to my knowledge.

Thank you @BrandonRice for the report and thank you @cottrellio for providing the quick solution.

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