why does Code assume that *everything* i'm typing/about to expand is going to be PHP?

[iaremarkus]

• VSCode Version: Code 1.11.2 (6eaebe3, 2017-04-13T07:56:42.517Z)
• OS Version: Darwin x64 16.5.0
• Extensions:

Extension	Author	Version
Bookmarks	alefragnani	0.14.1
color-info	bierner	0.4.1
vscode-svgviewer	cssho	1.4.0
divider	dinhani	1.1.0
githistory	donjayamanne	0.2.0
php-debug	felixfbecker	1.10.0
php-intellisense	felixfbecker	1.1.5
auto-close-tag	formulahendry	0.3.11
prettify-json	mohsen1	0.0.3
vscode-less	mrmlnc	0.6.2
color-highlight	naumovs	2.1.3
advanced-new-file	patbenatar	0.4.3
slack	sozercan	0.0.13
Align	steve8708	0.2.0
theme-markcustom	Mark	0.0.1
wordpress-snippet	tungvn	1.1.2

---

Steps to Reproduce:

1. When using Emmet-style HTML, anything I type is always assumed to be PHP which means when I hit 'tab' to complete/expand, it ignores my HTML and opens a PHP tag:

[ramya-rao-a]

In your gif above, you do get the emmet expansion in the end.
How did you get that, if TAB adds php tag?

[iaremarkus]

Tab, (wrong expansion), undo, tab again. It seems that the default expansion is wrong / php but the second time it's right FWIW sometimes I remember to escape first - to clear the default hints / suggestions and then it expands correctly. Also worth noting that the same thing happens in less/css. First option for expansion is some weird, obscure css property and after an escape, THEN, it shows correct Emmet value...

On Tue, 25 Apr 2017 at 5:19 PM Ramya Rao ***@***.***> wrote: In your gif above, you do get the emmet expansion in the end. How did you get that, if TAB adds php tag? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25218 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA5MBhTqVnfZK4Ll93-Dzsk_B2fT3IRpks5rzg7ogaJpZM4NFxzt> .

-- Sent from mobile

[ramya-rao-a]

Ah! got it

The item from the suggestion list gets expanded on TAB (which is not the right one in this case) and when you escape it and TAB again, emmet jumps in.

This is being tracked in #1952

You have a couple of options for working around this.
See #1952 (comment) and #1952 (comment)

We are also working on a way to get the emmet abbreviation expansion in the suggestion list itself.
That work is being tracked in #21943

[ramya-rao-a]

@wondergryphon

See #1952 (comment) for updates on this issue. You can now get emmet abbreviation expansion in the suggestion list. This way <?php will not be accidentally chosen