Any ideas why this might be happening?

I have a line that uses multiple interpolation blocks e.g. #{@var}, #{@var2}

The parser takes the second # to be the start of a comment. If I remove the comma then the second block is highlighted properly. When it's highlighted incorrectly all code below it in the document is then not highlighted correctly.

Syntax highlighting don't work when using a single quote in new haml syntax :

Or is this somthing I can configure myself? Would be great to add Inky-Haml support.

@ezekg You asked for feedback and this is the only odd thing I've noticed since the last release (0.22.2):

This :javascript filter is highlighted properly:

While this one isn't:

If I remove the new line between the first var declaration and the second, the highlighting turns back on:

According to its original creator, it's spelled "Haml", not "HAML":

https://twitter.com/hcatlin/status/301173144453005312

OS: Ubuntu 14.04 64 Bit

Atom Version: 0.137.0

Tried to install this extension, and got this message

gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp http GET https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v0.18.0/node-v0.18.0.tar.gz
gyp http 200 https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v0.18.0/node-v0.18.0.tar.gz
gyp WARN install got an error, rolling back install
gyp ERR! install error 
gyp ERR! stack Error: read ECONNRESET
gyp ERR! stack     at errnoException (net.js:904:11)
gyp ERR! stack     at TCP.onread (net.js:558:19)
gyp ERR! System Linux 3.13.0-37-generic
gyp ERR! command "/opt/atom/resources/app/apm/node_modules/atom-package-manager/bin/node" "/opt/atom/resources/app/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "install" "--target=0.18.0" "--dist-url=https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist" "--arch=x64"
gyp ERR! cwd /home/likewise-open/ZANECDEV1/karthikeyan.ak/.atom
gyp ERR! node -v v0.10.32
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok 

I took this screenshot with One Dark Syntax so that we'd have a common test ground. The markup:

%span.this#works-fine
%input.uh-oh{               |
  type: 'text',             |
  name: 'oh-no',            |
  title: "what's going on?" |
}                           |
%div.not-highlighted-correctly
  %span.neither-are-children
%a.having-more-brackets{ href: "fixes it" }
%span= "See?"

%span.note {                             |
  this: 'fixes the syntax highlighting'  |
}
%div= "But it will break if you try to render it."

It appears that pipe characters break the syntax highlighting. They also are highlighted differently (under my usual syntax theme, photon syntax) sometimes. Randomly they'll be white or purple, and I can't really figure out why. Also if you have an id before the attribute braces in the anchor tag above, it doesn't fix the highlighting (everything after the # is comment colored)

:scss filter is not recognised and breaks syntax highlighting.

As a best-effort fix, you could make :scss be synonymous with :css. It should also be possible to get actual scss highlighting, which might be worth the effort.

Commands split accross multiple lines ending in commas or piples lose all syntax highlighting

Both of these formats are supported by HAML

I've discovered that you can mix text and variables using Ruby/Haml interpolation like this:

%p Lorem ipsum #{variable} dolor sit amet

I think it would be nice if it were in other color and not white like it is right now:

Maybe I'm wrong and I shouldn't be doing that because it's not a good practice or something, so, what do you think guys?

When a newline is created in a haml file, the cursor starts with no indentation. It would be nice if the indentation was at least as far as the previous line.

In Atom:

In Sublime:

Thanks for the package!

Store package settings files in the settings/ directory instead of scoped-properties/

Package.loadSettings (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/src/package.js:565:9)
<unknown> (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/src/package.js:187:43)

I don't get any results in the Atom package manager when I search for language-haml. Is it still available?

I use grunt-haml-php that insert a new filter :php, is possible to integrate in this package?

This kind of bug started very recently:

Broken:

Not broken:

In our app we use some conditional html tags for versions of IE. In the 23.4 version of this plugin I was able to successfully see all correct syntax highlighting, but in the latest version, and at least 23.9, I see everything that's indented in the IE conditional comment as being read by language-haml as a comment.

This makes sense, and is "correct" as the body of the code is technically within the comment, but I don't want that behavior. Perhaps there is a way to ignore these type of IE comments? I will paste screenshots.

Thank you! :)

It works when the nested attributes are last.

Trying to type multiple siblings in a row tends to create child elements instead.

Type the following:

.test
.test
.test

and you'll see it come out as:

.test
  .test
    .test

Trying to be smart about indentation might be a bit more trouble than it's worth because there's no way to tell if you want empty elements or nested elements. Even in cases with no ambiguity, such as inline content, it wants to indent everything. I'd rather have to hit the tab key myself than have to realign five tds in a row.

Not working comment in hamlc

Store package settings files in the settings/ directory instead of scoped-properties/

Package.loadSettings (C:\Users\uSide\AppData\Local\atom\app-0.189.0\resources\app\src\package.js:565:9)
<unknown> (C:\Users\uSide\AppData\Local\atom\app-0.189.0\resources\app\src\package.js:187:43)

I haven't used Atom in a quite a while now so I'm probably not the best person to keep this package up to date. Anyone out there want to take over?

Store package settings files in the settings/ directory instead of scoped-properties/

Package.loadSettings (/opt/atom/share/atom/resources/app/src/package.js:539:9)
<unknown> (/opt/atom/share/atom/resources/app/src/package.js:188:43)

I no longer use Atom. Please comment below if you are interested in taking over this package.

I'm using the language-haml package to edit haml-coffeescript files in Atom 1.17.0 on my MBP running OSX 10.11.6.
I updated the package yesterday and since then the cmd-/ key binding no longer comments out lines. I used the keybinding resolver panel to make sure that it does resolve to editor:toggle-line-comments but I'm running out of ways to troubleshoot this issue, any idea ?

Thanks

multiline code highlighting doesn't work in ruby haml.

=link_to settings_campaign_url(@campaign),
            class: active_page == "settings" ? "active" : "" do

Not sure what technical limitations you're working with, but attempting to comment javascript using cmd-/ instead prepends the usual -# instead of // to that line. Is this fixable or are you limited to having a single commenting style per filetype?

Sorry if I'm misunderstanding something - this could turn out to just be my settings.

It seems like language-haml calls into various autocompletions from the language-ruby.

When a line ends with do, it adds a line below with end, which would be correct in Ruby but not in Haml. The same thing doesn't happen for if-statements so I'm guessing whatever override you have for those should also apply to blocks?

Eg
.some-div{data-attribute: 'test'}

Will work but the data- won't have the correct highlight.

Syntax highlight is not showing block comments as comments. It happens either on html and haml comments. Eg on a haml comment:

-#
    .phones
      %ul
        - unless @professional.phone.blank?
          %li= format_phone @professional.phone
        - unless @professional.phone2.blank?
          %li= format_phone @professional.phone2

The hole block above should be shown as a comment.

Here's the screenshot

I've just updated the package and now I get this one and I think I am not they only one check - atom/atom#8970

Here's a stack trace

SyntaxError: Syntax error on line 241, column 18: evalmachine.<anonymous>:1
"#\\{" "end": "\\}"
       ^^^^^
Unexpected string
  at nodeTransforms.Literal (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:100:15)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at /usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:114:17
  at Array.reduce (native)
  at nodeTransforms.Obj (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:107:30)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at Array.map (native)
  at nodeTransforms.Arr (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:104:27)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at /usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:114:17
  at Array.reduce (native)
  at nodeTransforms.Obj (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:107:30)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at /usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:114:17
  at Array.reduce (native)
  at nodeTransforms.Obj (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:107:30)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at /usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:114:17
  at Array.reduce (native)
  at nodeTransforms.Obj (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:107:30)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Value (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:79:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at nodeTransforms.Block (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:76:14)
  at transformNode (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:197:12)
  at Object.parse (/usr/share/atom/resources/app/node_modules/season/node_modules/cson-parser/lib/parse.js:203:12)
  at parseObject (/usr/share/atom/resources/app/node_modules/season/lib/cson.js:42:23)
  at parseContents (/usr/share/atom/resources/app/node_modules/season/lib/cson.js:91:16)
  at /usr/share/atom/resources/app/node_modules/season/lib/cson.js:179:24
  at FSReqWrap.oncomplete (fs.js:100:15)
  at /home/user/.atom/packages/language-haml/grammars/ruby haml.cson:1:1

Ideas ?

atom 0.209
language-haml 0.21

= foo
- if link_to "Home", root_path
  %div

I believe that the - and root_path at the 2 line shouldn't be greyed when I comment out the 1st line.

I've been using atom + haml in all my rails projects for years, so am basically addicted :-)

Now i am coding more js, mostly snippets in haml, and have got Sam Ruby's excellent ruby2js to work with haml. It basically lets you write ruby syntax but it transforms it one to one to js. So ruby syntax, js semantics.

Basically i would like a ruby2js highlighting. This should not be too difficult as a :ruby filter is already supported. If you want i can try, but i suspect it's almost a one-liner.

Thanks for taking this over (if i understood right)

Code starting with != or &= doesn't get highlighted as per the documentation: http://haml.info/docs/yardoc/file.REFERENCE.html#unescaping_html

&= "I like cheese & crackers"
!= "I feel <strong>!"

Please see here - AtomLinter/linter-rubocop#145 (comment)

In haml files that use String Interpolation '#{}', it seems to be using an incorrect scope.

I'd like to fix the link_to snippets. Currently they are as follows:

'link_to (route)':
  'prefix': '='
  'body': '= link_to "${1:Anchor Text}", ${2:route}_url'
'link_to (url)':
  'prefix': '='
  'body': '= link_to "${1:Anchor Text}", "${2:#}"'
'link_to (wrap selected text)':
  'prefix': '='
  'body': '= link_to "Anchor text...", ${1:"${2:$0}"}'

But as you can see the prefix is the exact same for all 3 options, so the last takes precedence I think and the others don't actually do anything.

IMO the options aren't well suited to, well suit everyones needs either.

1. link_to (route) not everyone would use the _url scheme. I personally never use that instead I use _path. I recommend we just change that to ${2:route} and let the user type it out. OR we add a 3rd ${2:route}_${3:path}`
2. link_to (wrap selected text) would be nice if ${1:Anchor Text} was the first.
3. Because all of these current snippets are the same we'd need to define how they are triggered by different prefixes and be sure we are not over-riding something else with them.

Thoughts?

Code that should have ruby syntax highlighting:

%p This is #{h quality} cake!

See reference.

This is valid haml, interpolation can occur in plain lines :

%p
  This is test #{test.number}

Here test.number is not colored as ruby.

So I'm using this package along with Atom Material theme and Atom Material Dark syntax.

Seems like the colors don't color correctly on classes, ids, and other various things and it blends together too much with regular words.

Hi,

When i use a framework like Ionic, the highlight element with multi words stop after the first word :

Store package settings files in the settings/ directory instead of scoped-properties/

Package.loadSettings (/Applications/Atom.app/Contents/Resources/app/src/package.js:565:9)
<unknown> (/Applications/Atom.app/Contents/Resources/app/src/package.js:187:43)

Hey all - cannot install this ATOM plug-in without getting an error:

Installing “[email protected]” failed.Hide output…
Unable to download https://www.atom.io/api/packages/language-haml/versions/0.31.1/tarball: 500 Internal Server Error

I am running on MACOSX High Sierra.

Granted, this is a ridiculous line of haml, but looks like it runs into a string parsing bug somewhere near the end of the line:

Here is the code:

%table#order-vendor-products-table.table.table-striped.table-bordered.table-hover.table-highlight{"data-ajax" => "true", "data-ajax-source" => products_path(format: :json, vendor_id: @order.vendor.try(:id) || 0), "data-display-rows" => "10", "data-info" => "true", "data-length-change" => "true", "data-paginate" => "true", "data-provide" => "datatable"}
  .not-a-string
    .also-not-a-string