Vanilla 1.1.1 is a product of Lussumo. More Information: Documentation, Community Support.
I noticed Intype highlights CSS somewhere incorrect, i.e.:
abbr,acronym {border:0}
highlighted incorrectly. BUT with
abbr,acronym {border:0;}
everything’s OK (semicolon at the end on border:0).
Which release are you are you using?
Is any of the line highlighted with out the semicolon?
Both seem to highlight correctly for me in 0.2.0.236.
Hm. I’m using .236 too
0.2.0.236 — also cannot duplicate
border is bold in both instances
Default theme…default everything actually. Did you customize your previous version’s itBundle for CSS?
Vlad: maybe you could upload some screenshot of the problem and tell us which theme do you use.
Screenshots.
State 1: http://img201.imageshack.us/my.php?image=state14js.png
State 2: http://img201.imageshack.us/my.php?image=state26na.png
State 3: http://img144.imageshack.us/my.php?image=state38kj.png
The first one is a state of an editor when file is just opened. (Notice that 6th line is active — it’s highlighted)
Next, I removed the semicolon and 6th line becomes highlighted.
The third state is the state when an editor is opened, but 6th line ain’t active it becomes black.
Also, I noticed that in some HTML pages I have the same problem. But, both CSS and HTML files are sophisticated. In simple files I have no such problems.
Finally, I noticed that this bug ONLY when loading big file in Intype — so at the moment when Intype parses syntax highlighting (when all text ain’t highlighted) try to click at some line and this line won’t be parsed.
I think I found another highlighting bug
<script type="text/javascript" src="includes/iframe.js"></script>
doesn’t render the same as
<script type="text/javascript" src="includes/iframe.js"> </script>
Note the space between the tag pair
The first script tag’s scope is “entity.name.tag.html”
The second one is “entity.name.tag.script.html”
It can be easily spotted by using the Eiffel theme for example.
Place the caret between > and < and press the space key
=> highlighting changes (because of changed scope)
Edit: In fact, I think it’s more a scope/parser bug than highlighting bug or even a javascript grammar bug
Looking at the regex for source.js.embedded.html (“parent” for entity.name.tag.script.html) in the HTML grammar:
## Regex 1
begin: (?:^\s+)?<((?i:script))\b(?![^>]*\/>)
end: (?<=<\/(script|SCRIPT))>(?:\s*\n)? <--- unrelated: "newline" (see below)
Newline: The end regex in Regex 1 shouldn’t match a line like this “test <script>test</script> test” because of the requirement to match a newline character, “\n”. Yet in Intype, it seems that it does.
and for meta.tag.any.html (“parent” for entity.name.tag.html):
## Regex 2
begin: <([a-zA-Z0-9:]+)(?=[^>]*><\/\1>)
end: >(<)\/(\1)>
We see that Regex 1 and 2 will match
<script></script>
but only Regex 1 will match
<script> </script>
Given that Regex 1 is defined in the HTML itGrammar file further down than Regex 2, shouldn’t it override Regex 2?
dvhthomas
Just open Intype\bundles\Rails.itBundle\snippets\migration_create_column_continue_mccc.itSnippet, and change this line:
content: 't.column "${1:title}", :${2:string}
mccc$0'
To (and I suppose the “mccc” at the end of the line is useless as well?):
content: 't.column :${1:title}, :${2:string}
$0'
And welcome to the Intype forums ;)
1 to 10 of 10