Tab autocomplete problem in Aptana 3
Hi,
In Aptana 3 Tab key for expanding abbreviation has some strange behavior. For example:
pos:ris expanded to:
position: relative;
but
pos:ais expanded to:
pos:p[name="string"] property: value
(should be position: absolute).
When I expand abbreviation with some other shortcut (for ex. Ctrl + E) expanded abbr is ok. This issue is only for Tab. I think this is some issue in Aptana 3, because in Aptana 2 everything works fine.
Aptana 3’s Tab key handler takes precedence over ZC one. So, in your case you’re expanding Aptana snippet (read notes in README: https://github.com/sergeche/eclipse-zencoding).
Thanks! I removed all snippets but still have problem with "h" Aptana 3 abbreviation. Do you know what I must remove to get "h" works with, for ex., "ov:h". Now "h" abbreviation is some kind of comment for new files.
I don’t use Aptana. It may be some sort of bundle action or dynamic contribution through bundles. You should ask Aptana devs
@sergeche the plugin is crazy good, keep it up
@castus I am using Aptana 3 and found that when I checked the checkbox in:
Window>Preferences>Zen Coding>Upgrade web editors
It seemed to fix any issues I was having with the plugin. One thing to note though, I tried using the filters and Aptana blocks ZC from doing it's magic, but if you add an extra| ('pipe') at the end and the plugin works.
The “Upgrade web editors” option is used for Eclipse WTP editors: it better handles line breaks between tags (i.e. when you hit Enter key) and between curly braces in CSS
Zen coding works fine only when I deleted all snippets included in Aptana 3. I have only one problem with "h" abbreviation.
Wysłane z Androida za pomocą K-9 Mail. Prosze wybaczyć lakoniczność.
sergeche [email protected] napisał:
The “Upgrade web editors” option is used for Eclipse WTP editors: it better handles line breaks between tags (i.e. when you hit Enter key) and between curly braces in CSS -- Reply to this email directly or view it on GitHub: https://github.com/sergeche/eclipse-zencoding/issues/18#comment_1154366