Indentation is broken after one-line for..end and if..end blocks. "Reindent Lines" results in this:

function func(n)
    a = 0
    for i in 0:n a = a + i; end
        return a
    end

Last two lines are over-indented. Same for if...end.

Sublime Text 3.0, Julia-sublime 2017.08.25.20.37.31

Auto-indentation is broken for me on SublimeText3. It's been broken for a couple of weeks I think:

If I switch to a different language (Matlab, Python) indentation works.

Input to functions are highlighted as for function definitions

I have trouble with indentation of code using struct, mutable struct and do.
Sublimetext does not indent the line following one of those keywords. The first two seem to be undefined in indentation but do is defined but does not trigger indentation.

Similar as in #13, doesn't match a comment without the space in between (for both line comment and block comment), see picture on line 7-8, 13-15. I tried to fix it and make a PR but scratching my head why this is not capturing the case on line 7-8.

See the third to last line here:

For example:

This is when I install the latest through Package Manger with sublime. Not sure if this is already fixed but not on a tagged release? Or is this intentional?

Thanks for your support on this.

Hi, thanks for the package! There seems to be a bug in the version I installed today (via Sublime Packages) with matrix inversion syntax. The matrix inversion apostrophe gets parsed as a string apostrophe. (See, e.g. julia/examples/colorimetry.jl.)

    rgbxyzsc = [(rgbxyz[1,:] ./ rgbw[1])';
                (rgbxyz[2,:] ./ rgbw[2])';
                (rgbxyz[3,:] ./ rgbw[3])']

All subsequent code in the file has string-like syntax highlighting.

Here's another small nitpick. In general, things are looking pretty beautiful though!

As the title says, it seems folding is not properly performed for functions with arguments distributed over multiple lines, see attached picture, showing the function repeated twice for convenience, with the first occurence folded.

Thanks for the great package.

I'm using Sublime Text 3 build 3126 on macOS Sierra. When I execute \mu+[tab] I get 𝑈. I haven't noticed any other problems with completion and it works in the REPL.

This should be parsed as "a not equal to 4" and not as assignment of 4 to variable a!

Would it be possible to have Unicode completion in the search window? (i.e. the window that appears after CMD+F)

Reality:

Ideal:

Note: the first doesn't happen if the end was initially higher up and was moved down, or if the function definition at one point had parens.

The combination of e and a number seem to be incorrectly highlighted? Does not happen with other letters, this probably happens because e on its own is highligted as the constant?

I know it's unrelated post but couldn't help asking, can you share the name of the font you're using in screenshot from README.md? I'd really appreciate if you do.

In Julia:

julia> :function
:function

But the syntax highlighting treats this as the beginning of a function declaration.

Why does folding sometimes not work?

Thanks!

This is handy to use sometimes:

e.g.

function test end

let
global test 

x = 323.23
y = 23.2323

function test(x)
    x
end

Typing r"\\\\" inside a julia file breaks syntax highlighting for the rest of the file even though it is valid julia syntax.

Hi,
and thanks for your efforts to improve the julia/sublime cooperation.

I've noticed that the newest version (v2016.08.14...) causes some problems on my Win7 machine.
For instance, the lines

println("sqrt(4) = 2")
a0 = 1

show everything from 2 and onward in red (string, I think).

Btw. the Julia package seems to update itself. Why is that?

Best, Paul S

Test:

foo(bar, :baz=>3)

In my Sublime:

Screenshot

I have noticed the following problem.
Please, could you have a look at it?

b = transpose(a)
This line does not cause any harm.

b = a'
But this line switches off syntax highlighting for the code that follows.
Syntax highlighting only comes back after a second transpose sign occurs.

Seems a little aggressive to overpower user's desire to use 2 space width

Using = in a string for calling a function with a parenthesis makes the parser believe it is a function definition instead of a function call.

If the setting to draw white space is turned on in sublime ("draw_white_space": "selection" or "draw_white_space": "all") the space-dot after function is colored with the same color as the function keyword.
Here the dot is red:

The first line below looks good, but the z in the second line should be orange. I think the problem generally occurs when you call a function (here the constructor MyType()) while defining default values. (Not so sure about this anymore, see below)

Like #26, but for new syntax:

The develop branch now contains a rewrite from Julia.tmLanguage to Julia.sublime-synax. It fixes and improves a lot of things.

• Syntax parsing is much easier and flexible, allows for more complex highlighting and easier maintenance.
• Improved syntax highlighting for all sorts of declarations (types, functions, macros). Parameters in function and macro definitions are highlighted.
• String interpolation is highlighted for double quoted strings (without string modifiers, this can of course be enabled for all strings). Do we want this? Check it out.
• Proper automated syntax tests in syntax_test_julia.jl (Run tests by running the build command.)
• Julia.tmLanguage will be kept for backward compatibility. The sublime-syntax format was introduced in sublime text build 3084 more than a year ago.

Check it out by cloning the repo into .../sublime_path/Packages/ and checkout develop.

Comments, thoughts and reactions to this?

The $ at the end of a regex with triple quotes breaks the syntax highlighting.

r"\n a \" b $"x  # Works.
r"""\n a \" b $"""x  # Broken.

print("""Hello World""")  # Messed up.

The $ makes the syntax highlighter think """x is a variable so the multiline string doesn't end.

• don't highlight variables
• regular function call should be variable.function only and the arguments should be meta.function-call.arguments variable.parameter
• supported function should be support.function only and parameters should be meta.function-call.arguments variable.parameter.

** Updated screenshot for julia**

This is minor, but I think the colon should be red here on the second line. Happy to keep opening these if they are helpful for you!

If one types TAB begin ENTER 3 ENTER end, one gets:

    begin
        3
    end

but if one types TAB 1 + begin ENTER 3 ENTER end, one gets:

    1 + begin
    3
end

This occurs commonly when writing e.g., macros which take block arguments.

This is a somewhat bizarre case I found while viewing this in sublime. Seems to be that a double quote (") can end a triple quote (""") segment, but only if string interpolation is used within the string.

In particular:

• immutable -> struct
• type -> mutable struct
• where-syntax (highlight where as a keyword? and the T after where should perhaps be highlighted as a type also?)
  

Complete list of changes in Julia 0.6.

This one should be simple to fix?

@ViktorQvarfordt

I have justed add a conversion functionality in UnicodeCompletion which basically converts between \alpha and α, which is quite useful in LaTeX documents. However, while I am writing a julia script file, I usual have

mu = 0
sigma = 1
z = sqrt(mu/sigma)

It would be interesting to convert this to

μ = 0
σ = 1
z = √(μ/σ)

So the questions are

1. Shall we ship this functionality in this package or a separate package?
2. Obviously, not all symbols should be supported, besides greeks, what symbols should be included?

This is on the develop branch. Seems like the * and / should be purple:

Coming up with descriptive titles is so much harder than pasting an image 😄 .

Thanks for this. I'm terrible with regex, otherwise I'd fix myself.

In the scope of #21 we currently

Fixing this requires some elaborate trickery with lookahead regexes, which are needed to distinguish a function call from an assignment-form function declaration. The issue is the round parenthesis inside the type annotation.

Currently all macros are set in plain color for me. It would be nice if it had a prettier color default

A picture is worth a thousand words...

See the last line here. I think the x and the comma should be white. Thanks again -- all your fixes are working for me and are well appreciated 😄

Perhaps it thinks x,f is the function name, which should be an easy fix?

Main.foo()
Base.length()
Core.eval()

I guess they should be support.module according to the office docs and there may be missing important modules.

I also added this to the wiki:

I think it would make sense for MyModule to inherit the same color as MyType/myfunc in these examples. When you are overloading an imported function, everything looks 👍 to me -- we want something similar for the examples above: