Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 06 17:01
    palango closed #95
  • Jan 08 2019 17:20
    mmagnuski closed #219
  • Oct 12 2018 13:40
    gdkrmr closed #218
  • May 19 2018 02:07
    yehielliv commented #223
  • May 19 2018 02:03
    yehielliv opened #223
  • Feb 10 2018 11:08
    currymj closed #171
  • Jul 25 2016 19:04
    jingpengwu commented #203
  • May 24 2016 12:19
    JonWel commented #183
  • May 24 2016 12:19
    JonWel closed #183
  • Apr 12 2016 11:11
    MikeInnes closed #185
  • Apr 12 2016 11:11
    MikeInnes closed #163
  • Apr 12 2016 11:11
    MikeInnes closed #166
  • Apr 12 2016 11:11
    MikeInnes closed #101
  • Apr 12 2016 11:11
    MikeInnes closed #82
  • Apr 12 2016 11:11
    MikeInnes closed #73
  • Apr 12 2016 11:11
    MikeInnes closed #69
  • Apr 12 2016 11:11
    MikeInnes closed #68
  • Apr 12 2016 11:11
    MikeInnes closed #61
  • Apr 12 2016 11:10
    MikeInnes closed #59
  • Apr 12 2016 11:10
    MikeInnes closed #57
Sebastian Pfitzner
@pfitzseb
@one-more-minute Yep, the new release fixes the problem with the jump menu is fixed. Although the behaviour is not quite consistent with other programs under windows, since a click on the icon does not minimize the window should it be in focus.
Okay, that's not the real problem. The window just isn't minimizable (is that even a word?!), the minimize button is greyed out and hence doesn't work.
(And the github login thingy is great!)
Mike J Innes
@MikeInnes
hmm, the minimising issue is odd, haven't seen that myself
Sebastian Pfitzner
@pfitzseb
I could reproduce it on three different machines running Windows 8.1 or the newest Windows Server 2012 with the newest binaries (I think, those that are linked in the discuss forum).
Nils
@nilshg
Is the forum down?
I was trying to post about a potentially troubling issue (if it isn't my fault, and can be reproduced, which I can't do right now for a lack of access to other machines): I think the inline display gets negative decimals wrong by a factor of at least 10
Consider randn(10,10)/100, when doing this in the REPL I get lots of -0.0x and -0.00x numbers as expected, but in Juno all the negative numbers are displayed as -0.x
E.g. -0.00675 is displayed as -0.7 - if I multiply by -1, the inline display shows 0.00675
Nils
@nilshg
I just spent an hour looking for a bug in my code but it appears that it's actually just the display that gets it wrong...
Mike J Innes
@MikeInnes
Yeah, just doing some maintenence
I'll take a look at that
Nils
@nilshg
Can you reproduce this? Or is it my installation?
And while I'm at it, one other slightly annoying thing: whenever I start a multiline comment, immediately upon typing #= I get a warning about an unterminated multi-line comment... which of course is not technically incorrect, but maybe there's a way for Juno to give me the chance to close the comment before issuing warnings?
Mike J Innes
@MikeInnes
That's probably a bug ;)
Juno shouldn't give any lint warnings yet, you're just seeing a leak from the internal parser
Same as the errors from adding/removing characters
0.4, right?
Ok yeah, I'm seeing the decimals issue
That's kinda bad, sorry about that
I'll fix ASAP
Nils
@nilshg
I'm on 0.3.3 at the moment, due to said parser issue when adding/removing characters. I.e. the unterminated multi-line comment warning appears for 0.3.3 as well
Mike J Innes
@MikeInnes
Ah ok
Nils
@nilshg
for the sake of completeness:
WARNING: LightTable.jl: incomplete: unterminated multi-line comment #= ... =#
 in skip_multiline_comment at C:\Users\tew207\.julia\v0.3\JuliaParser\src\lexer.jl:658
 in readchar at C:\Users\tew207\.julia\v0.3\JuliaParser\src\lexer.jl:322
 in lexcomment at C:\Users\tew207\.julia\v0.3\Jewel\src\parse\scope.jl:24
Mike J Innes
@MikeInnes
Yeah, leaking out of JuliaParser.jl
Ok, I see this too
If you open an issue for that I'll fix it as well
Hopefully today but just so I don't forget
Nils
@nilshg
Alright, I'll open an issue for the comment warning
Mike J Innes
@MikeInnes
Forum's back up, should be a bit snappier now
Mike J Innes
@MikeInnes
@nilshg I fixed both of those errors, you should be fine if you checkout Jewel. The 0.4 warnings come from JuliaParser.jl's incompatibility with 0.4 so there's not much I can do about that, unfortunately
Mike J Innes
@MikeInnes
@Varanas I just tried Gadfly on Windows and it's awful. Even basic plots end up basically crashing LT for seconds at a time. Is that what you were seeing before?
Mike J Innes
@MikeInnes
Ok, it actually seems to happen when generating loads of plots by pressing ctrl-enter repeatedly. Hopefully that's not a sign of a memory leak, but either way it shouldn't be too much of an issue for normal use
Sebastian Pfitzner
@pfitzseb
@one-more-minute Yup, that really is a problem - especially when using Reptile (at least I guess that's what the sliders over number literal are called?), because it then automatically generates the plot for all those different values... And sometimes a result appears that is not result, e.g. it doesn't have the right context menu and massively slows down LT (although that could be because there's too many points in that plot).
LT is usually still snappy with 100-1000 points in a plot, but if there are more it's totally unusable. I don't have access to a Linux-PC or a Mac right now, is performance better on those OS'es?
Mike J Innes
@MikeInnes
I haven't noticed problems so much on OS X, but I haven't pushed gadfly that far either to be fair
So, has this gotten worse for since node-webkit?
Either way, my Blink.jl work will allow you to put Gadfly plots in their own windows, which should help a lot
Sebastian Pfitzner
@pfitzseb
No clue if there was any change during the transition from node-webkit to atom -shell - I hadn't seriously tried Gadfly before. And Blink.jl sounds interesting, I'll have a look!
Mike J Innes
@MikeInnes
Give me a minute and I'll add a build step for windows
Sebastian Pfitzner
@pfitzseb
Oh, and thanks for fixing the issue with minimizing Juno on Windows!
Mike J Innes
@MikeInnes
Don't thank me, I just upgraded atom-shell ;)
Sebastian Pfitzner
@pfitzseb
But it works, so thanks anyways :D
Mike J Innes
@MikeInnes
Fair enough :)
Sebastian Pfitzner
@pfitzseb
(slightly OT, but if I want to tag a new version for a LT plugin, do I need to do this?)
Mike J Innes
@MikeInnes
Yup, go for it
Ok, check this out: clone Blink.jl, Pkg.build("Blink"), Graphics.docs()
Sebastian Pfitzner
@pfitzseb
That's pretty amazing!
Sebastian Pfitzner
@pfitzseb
Is the fullscreen property working for you on OSX?
I've played around a bit and really like it so far; the api is easy to understand, too.