Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sebastian Pfitzner
    @pfitzseb
    problem is that it's broken...
    Gabriel Gellner
    @gabrielgellner
    ha
    Christopher Rackauckas
    @ChrisRackauckas
    :smile:
    Gabriel Gellner
    @gabrielgellner
    so I really have no fix?
    Christopher Rackauckas
    @ChrisRackauckas
    Keep complaining and it'll get fixed :smile:
    Sebastian Pfitzner
    @pfitzseb
    lol
    Gabriel Gellner
    @gabrielgellner
    ha
    Sebastian Pfitzner
    @pfitzseb
    two possibilities: Either use Pkg.clone("https://github.com/JunoLab/Juno.jl") and [Pkg.checkout(x) for x in ["Media", "Blink", "Atom"]] or use git to clone the atom-julia-client and atom-ink repos to get back to the latest working releases.
    First one is more convenient, but will probably break more stuff
    because the refactoring to Juno.jl doesn't really work yet
    or rather, is still buggy
    Gabriel Gellner
    @gabrielgellner
    ha
    Blink needs 0.5+
    Sebastian Pfitzner
    @pfitzseb
    or something that might work: Go to ~\atom\packages\julia-client\script\boot.jl and change the using Juno statement in line 31 to using Atom
    Gabriel Gellner
    @gabrielgellner
    well time to man up I guess. I will use me some rc4
    hmmm
    Christopher Rackauckas
    @ChrisRackauckas
    rc4 is supposed to end up being the release
    so it's probably a good idea to start
    Gabriel Gellner
    @gabrielgellner
    Thanks so much by the way for all the help. I really appreciate it
    yeah. I have been meaning too. Just some of the "performance" regressions have scared me ;) Though the .( call syntax gets me stupid excited ... so we shall see how much of my code breaks
    Sebastian Pfitzner
    @pfitzseb
    that last one actually has a real chance of working, so try that first :D
    Christopher Rackauckas
    @ChrisRackauckas
    The performance regressions are mainly due to extra boxing occuring , i.e. parts of the type-inference broke
    Just run @code_warntype and throw a few type annotations / type declarations in and you're fine
    Gabriel Gellner
    @gabrielgellner
    ohhh good to know
    Christopher Rackauckas
    @ChrisRackauckas
    Also it happens if you count compile time: v0.5 let's you compile with -O3 so the compiled code, when correctly typed, should actually be faster
    Gabriel Gellner
    @gabrielgellner
    Is it expected to get a bunch of warnings about overwriting symbols: require(Symbol) from base, and some stuff in Gallium?
    (using rc4 of 0.5, with all the checkouts described above). My atom works at least :) but wasn't sure if messed something up with the warnings
    Sebastian Pfitzner
    @pfitzseb
    yes, that's expected
    we actually try to hide those, but that doesn't work well on Windows so far
    Gabriel Gellner
    @gabrielgellner
    perfect. Thanks again for all the help/tips. happy to be rocking my oh so lovely Juno again
    Camilo Roca
    @carocad
    hey guys, is there any progress in making the inline-results or console output copyable? If not, please let me know if I can help you :)
    Christopher Rackauckas
    @ChrisRackauckas
    They are copyable
    well, you can copy the whole thing
    It would be nice to be able to select though
    Mike J Innes
    @MikeInnes
    @carocad is being able to select results what you're going for?
    You could try just setting the CSS to allow that and see where it goes from there
    I don't have any particular ideas beyond that, so if you experiment a bit then any ideas you come up with are welcome
    Well, I have a very rough idea that we (in the ideal case) need some way to associate copy text with dom nodes, and then when a selection + copy is made we have to selectively override the default behaviour
    But that's what we need in julia-client – your needs could well be simpler given that you're pretty much just showing the plain text output
    Sebastian Pfitzner
    @pfitzseb
    I think there's more to this than css rules -- you can select text in results in the console (with the correct css), but not if the result is in a decoration with the exact same css. Not sure why... I've asked on the Atom slack, maybe someone there knows
    Mike J Innes
    @MikeInnes
    But we have a rule that turns off selection in ink's styles, right?
    Sebastian Pfitzner
    @pfitzseb
    and if you disable that rule, you can select text in results there
    but not when they are overlays in the editor
    Mike J Innes
    @MikeInnes
    Ah I see what you mean now
    It could be that Atom now includes that by default now though, right?
    Sebastian Pfitzner
    @pfitzseb
    Couldn't find any css that would do that
    Camilo Roca
    @carocad
    hey guys, sorry for the quick silence here. I saw that you updated the gifs on the atom-ink readme :)
    Nice one
    Sebastian Pfitzner
    @pfitzseb
    uh, we didn't? :P
    Dorian C Brown
    @DorianCBrwn
    Screen Shot 2016-10-05 at 2.55.46 PM.png