The line location code should be fixed now.
On Thu, Nov 20, 2014 at 12:50 AM, Tomas Krehlik
wrote:
> I just stumbled upon this post, I have the linter working in sublime for
> some time, trying it from time to time. Often it gets wrong lines, etc, but
> I guess it is going to improve as well as
I just stumbled upon this post, I have the linter working in sublime for
some time, trying it from time to time. Often it gets wrong lines, etc, but
I guess it is going to improve as well as the time needed to actually do
the lint. (About 10s because julia needs to start up.) Anyway, if anybody
It was shockingly easy once I figured out how to get the bleepin regex to
work. And how to use rx syntax.
On Thursday, September 18, 2014 12:29:46 AM UTC-5, Tony Fong wrote:
>
> This is so cool.
>
> On Thursday, September 18, 2014 11:43:38 AM UTC+7, Patrick O'Leary wrote:
>>
>> On Sunday, Septemb
This is so cool.
On Thursday, September 18, 2014 11:43:38 AM UTC+7, Patrick O'Leary wrote:
>
> On Sunday, September 14, 2014 12:12:49 AM UTC-5, Viral Shah wrote:
>>
>> I wonder if these can be integrated into LightTable and IJulia, so that
>> they always automatically are running in the backgroun
On Sunday, September 14, 2014 12:12:49 AM UTC-5, Viral Shah wrote:
>
> I wonder if these can be integrated into LightTable and IJulia, so that
> they always automatically are running in the background on all code one
> writes.
>
For Emacs users, I threw together a Flycheck extension for Lint.jl:
Jacob,
I recently got my eyes on integrating this with in ST somehow too, so let
me know if I can help (I'm @tlycken at github). I was thinking that
integration through SublimeLinter (http://www.sublimelinter.com/en/latest/)
might be a good way to do it, but I haven't had time to look further i
Jacob, Mike,
I just made a 2-line change to help you with that. You can do (block of
code as text) + (file/line info) -> Array( LintMessage,1 )
using Lint
ctx = LintContext()
ctx.file = file
ctx.path = path # optional, to direct include() correctly
msgs = lintstr( code, ctx, lineoffset ) # lineo
We can get really nice integration for Lint.jl and Light Table – I've
actually already got some of the GUI parts worked out, so it won't be crazy
difficult to do.
Quick question: How's Lint.jl's support for modules? For LT it's pretty
essential that the API looks like (block of code as text) +
I've definitely been meaning to work on integrating this with
Sublime-IJulia. Hopefully in the next week or so.
-Jacb
On Sun, Sep 14, 2014 at 10:19 AM, Adam Smith
wrote:
> This looks awesome. Regarding the Array parameter issue (which I'm really
> glad to see in the linter; this issue really tr
This looks awesome. Regarding the Array parameter issue (which I'm really
glad to see in the linter; this issue really tripped me up when learning
Julia), if https://github.com/JuliaLang/julia/issues/6984 ever finds a
resolution, it would be great to suggest that new syntax in the lint
message.
That's a good question. They can be used together, obviously. I can easily
speak for Lint. The key trade-off made in Lint is that it does not strive
for very in-depth type analysis. The focus is finding dodgy AST, where it
is located in the source file, and with a bit of explanation around issue
I wonder if these can be integrated into LightTable and IJulia, so that
they always automatically are running in the background on all code one
writes.
-viral
On Sunday, September 14, 2014 8:38:09 AM UTC+5:30, Spencer Russell wrote:
>
> Any comments on how Lint.jl and @astrieanna's also-awesome
Any comments on how Lint.jl and @astrieanna's also-awesome TypeCheck.jl
relate? Are you two working together, or are there different use cases for
the two libraries?
peace,
s
On Sat, Sep 13, 2014 at 3:34 PM, Tony Fong wrote:
> Fellow Julians,
>
> I think it is time to post an update on Lint.jl
Right, the correct way to say this should be Array{Number,1} in a function
signature would not match an input of Array{Int,1} etc. so in your example
if I do
julia> f( [1,2] )
ERROR: `f` has no method matching f(::Array{Int64,1})
Anyway, Lint catches that.
On Sunday, September 14, 2014 8:55:02
It's callable, but probably not what you want:
julia> f(A::Vector{Number}) = println(A)
f (generic function with 1 method)
julia> f(Number[1.0; 1])
Number[1.0,1]
On Sat, Sep 13, 2014 at 9:51 PM, Tony Fong wrote:
> I think a container type with a non-leaf eltype won't match anything. The
> right
I think a container type with a non-leaf eltype won't match anything. The
right way to declare such a function should be instead
function f{T<:Number}( x::Array{T,1} )
...
end
On Sunday, September 14, 2014 5:09:39 AM UTC+7, Tim Holy wrote:
>
> Wow, this is really impressive. I'm going to have t
Wow, this is really impressive. I'm going to have to take a close look again.
What do you mean below about "wrong signatures"? That signature looks correct
to me, albeit not very useful and probably not what the programmer intended.
--Tim
On Saturday, September 13, 2014 12:34:44 PM Tony Fong wr
17 matches
Mail list logo
