HTML snippets

[qqq]

Thanks, that helped.

I've one more question though. If I type say "table" and it completes after TAB and then inside of

Code: Select all

<table></table>

I type "tr" and press TAB again no completion is made only caret goes beyond table tag. Is this default behaviour?

[jps]

It is, because you're still within the snippet fields. There are two options:

* Press escape, to cancel the snippet fields
* OR use Ctrl+Space, rather than tab, to insert the tr snippet

[qqq]

Ok.

I'm not exaclty happy with the fact that input->TAB gives simply:

Code: Select all

<input>

instead of:

Code: Select all

<input type="text" name="test" value="value" />

I can easily correct this in HTML.sublime-completions.

The question is what would be the best action if I want to protect my changes in this file from being overwritten? Should I copy it to the "User" folder (this works only if I add a new completion, if completion with the same trigger exists in the original file though it has higher priority)? Copying the whole "HTML" folder to "User" is basically doing the same thing so I don't expect it to work either.

[atomi]

It is, because you're still within the snippet fields. There are two options:
...

Will this always be the case.

The idea of triggering a snippet within snippet field seems like a good one to me.

[qqq]

The idea of triggering a snippet within snippet field seems like a good one to me.

And the idea isn't new because that is how it worked (should say works) in ST 1.4.

[qqq]

I'm still geting some problems here.

1) I've set tab completions to true,
2) the scope is text.html.basic,
3) changed the scope of HTML.sublime-completions file to:

Code: Select all

text.html - source - meta.tag, punctuation.definition.tag.begin, source.php, source.js

Now some triggers work fine and some don't. For example when I press a->tab HTML trigger for <a> loses with PHP one for abs() though the latter should be triggered by abs->tab not by a->tab.

And this had already worked fine, it got bad on the last build or the one before.

Is it possible to change priority of these completions? So that those defined in HTML.sublime-copletions will always prevail over PHP ones, or at least when I'm in heredoc, string etc. Why would I want to type a php function there? And especially one like "cairo_ps_surface_dsc_begin_page_setup()"?

Edit:

As a makeshift solution I deleted the file PHP.sublime-completions. It was pretty useless anyway and with over 4000 (!) hardly-ever used functions getting in the way of whatever you type.

[fred]

good posts!