Hi,

In Sublime Text 2 when you try to expand:

.step$*17

You get:

        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;
        :;

Cheers.

On pressing Tab key after color in Sublime or Brackets, Emmet is expanding it into below code:
-webkit-column-rule: ;
-moz-column-rule: ;
-o-column-rule: ;
column-rule: ;

Similarly on pressing Tab key for "thin' it is getting expanded to text-indent: ;

Expected: color and thin should not be expanded

Emmet version in Sublime: 2016.08.10.08.24.48
Emmet version in Brackets: 1.2.2

https://www.dropbox.com/s/3c8tsi8fj17447w/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202014-06-20%2011.23.08.png

When I pressed "tab" it make this: https://www.dropbox.com/s/mkvaewxwvanto93/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202014-06-20%2011.23.30.png

When I try to make div>p
https://www.dropbox.com/s/m46xsrippkcrjed/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202014-06-20%2011.24.00.png
It make this: https://www.dropbox.com/s/ulv9fhoi9c9h3tf/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202014-06-20%2011.24.20.png

But few days ago It worked correctly...

Version 0.3??
cant running on grunt v 0.4
"the file name grunt.js changed to grunfile.js"

try to Running local web-site
thx

I found little issue with input arrays in HTML, ex. <input name="foo[]">

Emmet skips closing bracket in attributes (in this case - name):
input[name=foo[]] =>
<input type="text" name="foo[">

input[name=foo[0]] =>
<input type="text" name="foo[0">

input[name=foo[{id}]][value={id}] =>
<input type="text" name="foo[{id}" value="{id}">

Emmet seems to be working fine. Doc type, div, everything but when I try and use the following syntax nothing happens.

ul>li*6

Have removed and installed new.

Any help would be great.

I seem to get this after a clean pull, npm install and docpad run...

Any ideas?

warning: Something went wrong while rendering: /Users/oo/Dropbox/Dev/emmet-docs/src/layouts/default.html.eco
warning: Something went wrong while rendering: /Users/oo/Dropbox/Dev/emmet-docs/src/documents/cheat-sheet/index.html
error: An error occured: 
TypeError: Cannot use 'in' operator to search for '/c/main.css' in null
    at /Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-frontend/out/frontend.plugin.js:173:25
    at Array.map (native)
    at getAssets (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-frontend/out/frontend.plugin.js:171:32)
    at Object.templateData.assets (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-frontend/out/frontend.plugin.js:187:18)
    at Object.eval (eval at <anonymous> (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-eco/node_modules/eco/lib/compiler.js:19:12), <anonymous>:49:19)
    at Object.eval (eval at <anonymous> (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-eco/node_modules/eco/lib/compiler.js:19:12), <anonymous>:91:8)
    at eval (eval at <anonymous> (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-eco/node_modules/eco/lib/compiler.js:19:12), <anonymous>:93:6)
    at Function.eco.render (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-eco/node_modules/eco/lib/index.js:26:25)
    at EcoPlugin.render (/Users/oo/Dropbox/Dev/emmet-docs/node_modules/docpad-plugin-eco/out/eco.plugin.js:22:35)
    at ambi (/usr/local/lib/node_modules/docpad/node_modules/ambi/out/lib/ambi.js:36:27)
    at DocPad.<anonymous> (/usr/local/lib/node_modules/docpad/out/lib/plugin.js:90:18)
    at ambi (/usr/local/lib/node_modules/docpad/node_modules/ambi/out/lib/ambi.js:21:27)
    at Task.<anonymous> (/usr/local/lib/node_modules/docpad/node_modules/bal-util/out/lib/events.js:36:16)
    at ambi (/usr/local/lib/node_modules/docpad/node_modules/ambi/out/lib/ambi.js:21:27)
    at /usr/local/lib/node_modules/docpad/node_modules/taskgroup/out/lib/taskgroup.js:82:19
    at process._tickDomainCallback (node.js:459:13)

Commenting out both <% for url in @assets('css'): %> and <% for url in @assets('js'): %> in default.html.eco allows the rendering to continue.

Node v0.10.6
DocPad. 6.34.2

When using the nesting operator > with input the result is an inline nesting within the parent element rather than having input on separate lines within the nesting.

<!-- Expected -->
form>p*4
<form action="">
  <p></p>
  <p></p>
  <p></p>
  <p></p>
</form>

<!-- Unexpected -->
form>input*4
<form action=""><input type="text"><input type="text"><input type="text"><input type="text"></form>

<!-- Unexpected, it's not a problem with the form element -->
p>input*4
<p><input type=""><input type="text"><input type="text"><input type="text"></p>

(Using Emmet in Visual Studio Code)

I'm relatively new to Emmet so I can't rule out if this is intended behaviour.

I'm attempting to specify where a child element should be inserted with the following code snippet:

   "z1col":"th.columns.first.last.small-12.large-12>table>tr>th{${child}}+(th.expander)",

When I use "z1col>p", the child elements are being inserted into the th.expander element, and not the previous th element. I've tried $1 and ${child} and neither appear to be working.

It struck me that it would be nice to be able to write some BEM pattern quickly using the parent class.

e.g.

footer.footer>div.&__inner 

would result into

<footer class="footer">
  <div class="footer__inner">
  </div>
</footer>

Or let say for buttons

button.btn.&--large.&--primary

would result into

<button class="btn btn--large btn--primary"></button>

In VS Code, I have Emmet automatically add comments.

"emmet.syntaxProfiles": {
    "html": {
        "filters": "html, c"
    }
}

That's great for HTML comments. But, what if you're using Blade or Nunjucks? You still want to use Emmet's automated comments with these languages, but the comments are different.

Blade: {{-- --}}

Nunjucks: {# #}

How do you make Emmet smart enough to realize context?

After recent update, my custom snippets have all stopped working. It feels like they are being overridden by sublimeText3's autocomplete feature maybe? The file types in question are .scss and .blade.php. I have been using and relying on these snippets for over a year and all the sudden nothing. I have "disable_completions": false and "remove_html_completions": true

		"html":
		{
			"filters": "html, blade",
			"profile": "html",
			"snippets":
			{
				"container": "<div class=\"container container--large\">\n\t<div class=\"row\">\n\t\t<div class=\"col-${1}\">${2}</div>\n\t</div>\n</div>",
				"fe": "@foreach($0)\n@endforeach"
			}
		}

^ the above "container" snipped usually opens up into some nested divs but now when i hit tab it expands into just container--large.

Hi,
is it possible to autocomplete a class or id with the open and closing curly braces if i do the following:

.classname -> press tab: result should be classname {} and the cursor within the braces

The documentation says it's ctrl+shift+u, but the default package use ctrl+u

[ using windows 8 and sublime text 2 ]

Does emmet support css grid?

ctrl+e is a rather trivial shortcut for jumping to the end of a line, not expanding emmet expansions :)

RT

Below are the contents of my Emmet.sublime-text file, but Emmet is inserting prefixes whenever I press tab around some properties, regardless.

{
  "preferences": {
    "css.autoInsertVendorPrefixes": false
  }
}

A feature like this should not be enabled by default unless it presents the best solution out there, which it doesn't.

Describe it for:
http://docs.emmet.io/actions/go-to-edit-point/
http://docs.emmet.io/actions/select-item/
http://docs.emmet.io/actions/split-join-tag/
http://docs.emmet.io/actions/remove-tag/

Brackets: Release 1.4 build 1.4.0-16380 (release 273804eb3)
Emmet extension: v1.2.2

Related ticket in Brackets GitHub: adobe/brackets#11425

Basically, the issue is that when you have multiple selections using the Brackets built-in multi-select feature, and you have the Emmet extension enabled, using the carriage return behaves in an unexpected manner. The carriage returns happen in the correct places, but the cursors are passed down to the next line from where they were originally, instead of the accounting for the added lines from inserting all of the earlier carriage returns. For example, if your cursors are on lines 16, 19, and 53, they will be located on lines 17, 20, and 54, instead of 17, 22, and 56.

Have to describe how ! modifier works in CSS

It seems the webkit transform is breaking on the tooltips on the demos.

I see either a black box, or blurry(un-readable text).

http://cl.ly/image/2v2Y1a0n1i0n
http://cl.ly/image/3c1C2c0h2K3G

Chrome:
http://cl.ly/image/2N0X2S3E0I0Z

Although I use sublime text at home, at work I am stuck with VS2010. Are there any plans to support VS2012 or 2012?

Thanks,
Jon

Although not an issue per se, I wasn't able to see where I could modify Emmet's default CSS formatting from "expanded" (properties+values each in a single line) to compact (all properties+values in a single line).

For example, Emmet's current CSS default formatting (expanded):

header {
       width:960px;
       height:120px;
}

To this style (compact):
header { width:960px; height:120px; }

Any idea how to accomplish this?

Thanks.

I think I posted this in the wrong page.

I posted this issue again here: emmetio/emmet#114

I assume you can delete this post since I can't do it.

Thanks.

I am finding an issue in Sublime text 2, where a new line will insert an extra tab, along with subsequent line with one less tab.

I find this in any file type supported, when I hit return anywhere in the document.

Just within this last week, the shortcut "html:xt" stopped working for me in Sublime. Any others having this issue?

I'm not 100% sure this is an issue or not but here's what's happening to me.

I need this HTML:

<label for=""><input type=""></label>
<label for=""><input type=""></label>
<label for=""><input type=""></label>
<label for=""><input type=""></label>

So after reading the cheat sheet seems I need to use this:

[label>input]*4

...but I'm getting this as the result:

<div label=""></div>
<div label=""></div>
<div label=""></div>
<div label=""></div>

Keep in mind that if I do this:

label>input*4

I get this (which is the correct output regardless if is incorrect markup):

<label for="">
  <input type="">
  <input type="">
  <input type="">
  <input type="">
</label>

Am I doing this wrong? Or is there really an issue with Emmet?

Thanks.

btn:b abbreviation not working in Sublime Text

btn:b => <btn:b></btn:b>

Господи, как отключить вендорные префиксы, сил больше нет(((

"preferences": {
        "css.autoInsertVendorPrefixes": false,
 }

Не помогает. Sublime 3 build 3126

The filter.commentAfter preference value looks empty since it contains HTML comment. Need to escape value before outputting.

Hi,

I have seen your post and this link: lorenzos/ZenCodingNetBeansPlugin#19

I have tested the netbeans plugin and would ask about [] and {} they dont work with netbeans 7.1.1. are these features for attributes and text only available in emmet or in zen coding too? Hope it will come soon. Nice tool.

Regards
Chris

Hi, it would be tremendous useful symbols or punctuation speed writing. BTW love your plugin...

snippets.json link is incorrect in "emmet-docs/src/documents/abbreviations/types/index.html.md".

Please add support for rgba().

Maybe something like:

F.5 = rgba(255, 255, 255, .5)

FFF.5 = rgba(255, 255, 255, .5)

white.5 = rgba(255, 255, 255, .5)

In Sublime Text 2, the abbreviation ul>li[title=$]*4, will produce:

<ul>
    <li title="1"></li>
    <li title="2"></li>
    <li title="3"></li>
    <li title="4"></li>
</ul>

Whereas ul>li{$}*4, will produce:

<ul>
    <li>1</li>
    <li>2</li>
    <li>3</li>
    <li></li>
</ul>

Omitting the last digit.

I'm referring to the "|c" tag that you can put at then end of your expression so emmet will generate end tag comments.
Is there any way to set emmet to always do that? Regardless if I add "|c" at the end of my expression or not.

So either perhaps my sublime 3 emmet plugin doesn't implement the correct way, or there is a spelling mistake on http://docs.emmet.io/cheat-sheet/.

Basically, Alias of button[disabled.] should be Alias of button[disabled] same goes for
Alias of select[disabled.]
Alias of fieldset[disabled.]

Google fonts are just removed from list

The HAML filter is great, lack of Zen Coding for templating languages is the main reason I still write in vanilla HTML. I would love to see a filter for [slim](http://slim-lang.com]. :)

Please add support for rgba() in border

Trying to escape characters <> greater than/less with the filter |e in VS Code. Entering the code below, then using tab or enter key. This does not produce the escape the characters like it should:

footer>p>span{Happy Farm}+{© 2021}|e

Is it a bug?

Other filters like comment with |c works fine.

(My System: Windows 11 x64, VS Code 1.60.1)

Hey All,

I am using Compass alongside SCSS (SASS) however I which to remove the vendor short-codes for emmet, as they are slowing down my workflow.

e.g. border radius

Is it possible to do this? I could avoiding needing to delete them, just disable this functionality.

-Neil