It looks like this got broken with a Sublime update

[davidkrider]

I was using this plugin to force Rails HAML files to use the TextMate HAML syntax format instead of the built-in Rails one. It broke for me a couple months ago, and I've been trying another editor, but today I thought I'd open the console, and this is the traceback I got:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 478, in run_callback
    expr()
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 517, in <lambda>
    run_callback('on_load', callback, lambda: callback.on_load(v))
  File "/Users/davidkrider/Library/Application Support/Sublime Text 3/Installed Packages/ApplySyntax.sublime-package/ApplySyntax.py", line 348, in on_load
    self.detect_syntax(view)
  File "/Users/davidkrider/Library/Application Support/Sublime Text 3/Installed Packages/ApplySyntax.sublime-package/ApplySyntax.py", line 382, in detect_syntax
    self.set_syntax(syntax.get("syntax"))
  File "/Users/davidkrider/Library/Application Support/Sublime Text 3/Installed Packages/ApplySyntax.sublime-package/ApplySyntax.py", line 448, in set_syntax
    path = os.path.dirname(n)
  File "./python3.3/posixpath.py", line 151, in dirname
AttributeError: 'NoneType' object has no attribute 'rfind'

[facelessuser]

Can you run the "Support Info" command from the Preferences/ Package Settings/ApplySyntax menu?

I believe this issue is already fixed.

[davidkrider]

• ST ver.: 3211
• Platform: osx
• Arch: x64
• Plugin ver.: 3.0.0
• Install via PC: True
• mdpopups ver.: 3.5.0
• markdown ver.: 3.1.1
• pygments ver.: 2.1a0
• jinja2 ver.: 2.10.1

[facelessuser]

Ugh, okay we somehow have another case of this. I'll probably have a fix for it sometime today. I'll track it down.

[facelessuser]

@GirBot add T: bug, S: confirmed
@GirBot remove S: triage

[facelessuser]

@gir-bot add T: bug, S: confirmed
@gir-bot remove S: triage

Whoops, have to call the right name...

[facelessuser]

3.0.1 will fix your issue once it's available in package control.

[davidkrider]

I've updated now. Thanks for fixing the bug. The new "feature" in ST3 for "Open all with current extension as..." absolutely will not work to select a different HAML syntax file over the default, which is why I'm trying this. I thought this plugin forced it. I can't find the spot where I got the original snippet to make sure that my config is correct. Here's what I have. Does it look right?

"syntaxes":
 [
 	{
 		"extensions":
 		[
 			"haml"
 		],
 		"name": "Haml/Syntaxes/Ruby Haml",
 		"rules":
 		[
 			{
 				"file_name": ".*\\.haml$"
 			}
 		]
 	}
 ]

[facelessuser]

Did you mean to use file_path: http://facelessuser.github.io/ApplySyntax/usage/#file-path-rule?

On a side note, please open a new issue for separate problems.