-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Cannot expand HTML abbreviation in PHP tags #85
Comments
Hi! I have the same issue. I try change syntax_scopes on Emmet.sublime.settings but not works :(
|
You should change |
Thank you. This is the solution: #50 (comment) |
Hi! I resolve this copy / paste on key bindings user this code: #50 (comment) |
@soysoluble Hi, I tried putting this in my user key bindings, but it didn't seem to work for me. Trying to expand an abbreviation inside PHP strings still isn't working. For example: <?php
'div.foo'; // My string
'<div class="foo"></div>'; // What it should expand into
'div.foo ' // What it is doing instead
?> @sergeche Could you elaborate on how I can alter the |
@brodenbrett you're right. Try this: echo ' |
Here’s a recipe for adding abbreviation capturing with interactive previews for PHP strings. You should open Preferences > Package Settings > Emmet > Settings:
"html": "text.html - source - meta.attribute-with-value.style, text.html source.php string",
Save the file: now typing words in string literal will follow the same logic as in HTML. I’ve also pushed v2.1.13, it improves logic of abbreviation extraction inside string literals so you’ll be able to expand it right before quote, e.g. |
Also note that in suggested solution to mimic old Emmet behaviour with Tab key, you can limit |
@sergeche thanks. Sorry for the question but not find documentation for add css auto prefix on this version :) |
@sergeche Thank you! This solved my issue. Appreciate the quick response and update as well |
Hello,
Before the update I could expand HTML tag abbreviations within PHP strings, and now I am unable to do so. Has this been discontinued, and if so is it possible to downgrade to v1?
The text was updated successfully, but these errors were encountered: