-
Notifications
You must be signed in to change notification settings - Fork 145
Losses syntax highlighting and text becomes grey when adding erb tags in Ruby #261
Comments
Thanks for the report, reproduce in 1.34.0 with macOS 10.12.6. |
I can still reproduce this in Atom 1.39.0 |
Still here in 1.40.1 |
I can reproduce in Atom 1.40.1, with Ubuntu 18.04.3 LTS |
Atom 1.40.1 / MacOS 10.14.6 still experiencing the same issue with ERB. |
Tested today on Atom 1.41.1 and 1.42 this is no longer happening. Consider this resolved? |
unfortunate no we cant. Even on 1.43 this still happens fairly often. I am on Mac |
Same here. Found this while hoping there was a fix. |
still a problem in Atom 1.45 |
I've have experienced this issue, and now (1.47) I've got a new one that I think might be related. I can open some erb files that have full color, then open another erb file with no color. With the problem described above, closing and reopening the file would fix it. With this new problem there is no highlighting from open. Also, adding code above the gray lines seems to do full highlighting, while adding below only highlights the I also have the (non-treesitter?) HTML (Rails) and HTML (Ruby - ERB) grammars, and switching to one of those gives full highlighting. |
Tinkering further, I believe the following is the problem: <% if @thing %>
<script></script>
<% end %> That code will cause the issue in other files, BUT the following does not cause the problem: <% if @thing %>
<script>
<% end %> (no close to the script tag) |
This is occuring on |
Having the same problem. It seems as soon as I enter a <script></script>, everything goes grey, with occasional, random highlighting. Frustrating because I'm a newbie and the highlighting was very helpful (when it was working). |
I am also experiencing this issue on 1.48. |
Still 1.48, and still experiencing this after adding </script> in a .html document. |
Same here 1.48.0 |
Still got this issue in 1.5 |
Can confirm random greyed out lines and/or script tags v1.5.0 pretty annoying |
Ah sublime text is up to v4, might have to check it out - came from sublime to atom because there was a nice package called html preview which updates the page on the fly and runs inside atom |
I'm also still seeing this, in Atom 1.52.0 on MacOS 10.15.7 Was this bug possibly introduced with #240? |
Any progress of this? Getting a LOT of issues with ERB files... I mean, A LOT! BTW, I noticed that if I narrow the width of the editor, the syntax works again in some points. I don't know if it's because part of the code is hidden or if the width has something to do with it. |
Just install Sublime Text save yourself the headache |
I'm using VS Code as main editor for Ruby projects. It's a lot of headache for a simple syntax highlight... TBH, the Atom highlight is very good, it marks the right words even with the name of functions outside the "dictionary". But the problem of colors deactivating is really annoying. |
Prerequisites
Description
Code after inserted erb text becomes grey and losses syntax highlighting.
Closing the file and then reopening it fixes the issue.
I did see this mentioned in issue #18342 but that was closed and the syntax highlighting doesn't seem to be fixed.
Safe mode does not solve this problem.
Steps to Reproduce
Edit by @rsese to add more detailed repro steps
<%=@owner.id%>
after the "/owners/" in the<input>
tag.**Interesting note:
If I add the "=" after i close the tag it highlights and formats correctly, see 2nd screen recording.
Expected behavior: [What you expect to happen]
Highlighter should highlight syntax correctly
Actual behavior: [What actually happens]
After typing the
>
in<%=@owner.id%>
, the rest of the content loses highlighting (as mentioned above, closing and reopening the file seems to clear things up).See screen recording:
Screenshot:
When adding the "=" after closing the tag:
Reproduces how often: [What percentage of the time does it reproduce?]
Everytime.
Versions
Atom : 1.34.0
Electron: 2.0.16
Chrome : 61.0.3163.100
Node : 8.9.3
MacOS Mojave 10.14.2 (18C54)
The text was updated successfully, but these errors were encountered: