search

samholmes / EJS.tmLanguage

An EJS syntax definition specifically for sublime text
47 stars 28 forks source link

highlighting syntax gets messed up with open close brackets #14

Open builtbylane opened 9 years ago

builtbylane commented 9 years ago

screenshot: http://cl.ly/YSH0

harberg commented 9 years ago

Same problem. OSX 10.10.1

scaryguy commented 9 years ago

Same here.

onedr0p commented 9 years ago

+1

zachary95 commented 9 years ago

Totally, very frustrating actually. I hope one day I'll get mad enough for fixing the issue myself and make a pull request!

gpedro commented 9 years ago

+1

zachary95 commented 9 years ago

Finally I'm a coward so I've moved on Handlebars. Punish me.

homerjam commented 9 years ago

+1 (does #8 fix this?)

codeclown commented 8 years ago

+1 I've been struggling with this for a long time.

@homerjam How can I test the updated version? Not familiar with the plugin architecture on Sublime Text.

homerjam commented 8 years ago

@codeclown I think you can just place the plugin files in the sublime packages directory and then restart sublime - depends what platform you're on for the location of this directory.

http://docs.sublimetext.info/en/sublime-text-2/basic_concepts.html#the-data-directory

http://docs.sublimetext.info/en/sublime-text-3/basic_concepts.html#the-data-directory

codeclown commented 8 years ago

Just tested it and didn't work properly (i.e. same syntax issue). This could actually be a bug in Sublime Text since it seems to fail to recognize the ending tag.

MattMorgis commented 8 years ago

This is still an issue. Solved it by simply installing atom.

brentchow commented 8 years ago

+1

bondparkerbond commented 8 years ago

I am having the same issue with messed up colorization. Using ST3 and OSX 10.10.5.

screen shot 2016-03-14 at 2 35 24 pm
chupetoide commented 8 years ago

+1

NicoHinderling commented 8 years ago

Will any of the maintainers fix this?

zachary95 commented 8 years ago

This thread still active since almost 1 year so I think you can just step through and move for another package or solution …

NicoHinderling commented 8 years ago

@TheSuperFly fair enough lol. Unfortunate there isn't a clear alternative

nwoltman commented 8 years ago

@NicoHinderling There is now a clear alternative: EJS 2

NicoHinderling commented 8 years ago

@nwoltman You're awesome. Thanks buddy :)

nwoltman commented 8 years ago

@NicoHinderling No problem :)

samholmes commented 8 years ago

Sorry for the frustration. Somehow, notifications for this repo were turned of on Github, so I wasn't receiving emails about these comments.

I hope this PR merge solved the issue: https://github.com/samholmes/EJS.tmLanguage/commit/0299864473711904e94d781f0b1c09d0725f2497

Please let me know if problems continue.

nwoltman commented 8 years ago

The problem is still there. I don't think the changes in 0299864 actually do anything. To make it easier to copy and paste some example code, here's the code from @bondparkerbond's screenshot above (the current syntax highlighting looks exactly the same as in his screenshot).

<a href="/products">Back</a>
<% if (product) { %>
  <h1><%= product.name %></h1>
  <h3><%= product.description %></h3>
  <h3>$<$= product.base_price %></h3>
  <h3>Qty: <%= product.quantity_on_hand %></h3>
<% } else { %>
  <h1>Product not found</h1>
<% } %>