Some improvements with indenting and comments

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enter form>input*3
2. Press the magical combination
3. And watch

What is the expected output? What do you see instead?
Well, the expected output should have some indention and enters in it, but it 
seems to be all 
cluttered togetether, same as select>option*4 would do, or is there a reason 
why there is no 
indention in form elements?

I like it alot with endentation just like div>p*5 would come up with.

What version of the product are you using? On what operating system?
OSX 10.5 - Espresso 1.0.7

Another point is, a function to generate this would be nice.

<!-- container -->
<div id="container">

</div>
<!-- /container -->

I allways love to have that matched in the 'important' sections, so I can 
easily see, what belongs 
to what.

In the CSS I would match the same things up.

/* container */
#container {

}

#container p {

}
/* /container */

Original issue reported on code.google.com by matthijn...@gmail.com on 21 Nov 2009 at 10:37

[GoogleCodeExporter]

Agree with form>input*3: this is really annoying for me, too. This is because 
ZC treads input as inline element, 
so it doesn't do any formatting on it. Will fix it.

About commenting tags: ZC for Aptana as a "Move to matching tag" action which 
traverses between opening and 
closing tag. I will port it to Espresso — hope it will be better solution 
than commenting. For now, you can create 
your own snippets for such elements, like this: <!-- ${id} -->\n<div 
id="{$id}">\n\t${child}\n</div>\n<!-- 
/${id} -->

Original comment by serge....@gmail.com on 22 Nov 2009 at 10:15

• Changed state: Accepted

[GoogleCodeExporter]

Thanks, that is exactly what i'm looking for.

Would be nice that the commenting is only applied when there is an actualy id, 
and else the comments are left 
behind.

Now I created a snipped called divc, so I use that when I feel the need to add 
comments.

Original comment by matthijn...@gmail.com on 22 Nov 2009 at 11:40

[GoogleCodeExporter]

This issue was closed by revision r296.

Original comment by serge....@gmail.com on 9 Feb 2010 at 9:55

• Changed state: Fixed