Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 13 11:30
    szhorvat commented #173
  • Oct 12 02:23
    halirutan commented #173
  • Sep 30 22:56
    halirutan closed #174
  • Sep 30 22:56
    halirutan commented #174
  • Sep 30 18:24
    subhodipbiswas assigned #174
  • Sep 30 18:24
    subhodipbiswas opened #174
  • Sep 18 08:25
    szhorvat commented #173
  • Sep 13 10:55
    halirutan labeled #173
  • Sep 13 10:55
    halirutan commented #173
  • Sep 13 06:52
    szhorvat assigned #173
  • Sep 13 06:52
    szhorvat opened #173
  • Aug 11 03:41
    halirutan closed #170
  • Aug 11 03:41
    halirutan commented #170
  • Aug 07 11:10
    halirutan closed #172
  • Aug 07 03:40
    simonkeys commented #172
  • Aug 07 01:56
    halirutan commented #172
  • Aug 07 00:23
    simonkeys edited #172
  • Aug 07 00:18
    simonkeys assigned #172
  • Aug 07 00:18
    simonkeys opened #172
  • Aug 05 05:50
    halirutan closed #171
Szabolcs Horvát
@szhorvat
image.png
Strangely, Normalized does not show a context, even though it should be System context.
This is true for anything that's not treated as a function $RecursionLimit also does not show a context.
It's pretty bright here today so I can't see well with Darcula. I'll switch back after sunset. I really wish for an automatic theme switcher :)
Patrick Scheibe
@halirutan
@szhorvat The reason is that I use a "heuristic" to decide if it's a function or not and strangely enough:
In[303]:= Options[DirectedEdges]

Out[303]= {"ArrowheadsSize" -> Automatic}
Szabolcs Horvát
@szhorvat
???
That must be a bug!
I'll ask Kyle
Patrick Scheibe
@halirutan
And I can check back home why Normalized doesn't show the context. We need to wrap up anyway for the 12.1 release.
Then I need to re-check all the symbols, usage messages, contexts, etc..
eduardoofthehour
@eduardoofthehour
@halirutan Hi, thanks for taking the time to answer, I guess I will make an exception and subscribe in spite of how much I hate subcription monetisation models, partly because I wanna say thanks for all the unpaid work so far.
But I really realy don't want them, if, in the future, it becomes unaffordable to me, I might be locked out of a significant investment in terms of learning how to learn the plugin
Szabolcs Horvát
@szhorvat
@halirutan Could you give me a link to the Mathematica code that extracts this information? Perhaps I can submit an improvement and work around these individual issues.
The Gitter desktop app is not working at all for me today. Generally, Gitter has been unrealiable recently and it stopped sending me emails a long time ago. Anyone else having problems?
Patrick Scheibe
@halirutan
@szhorvat I also don't get emails. I just have to check every once in a while. This is the reason I'm sometimes slow to respond. I'd like to switch to Slack, but I'm not sure since people need to get invited.
In any case, you can always write me in our Mathematica Slack in the plugin channel. I just invited you.
Yearly/monthly subscription with a fallback license
That basically means that each version you used for a whole year (speak, you paid for it a whole year) will be used as a fallback. However, I don't if this is already available for plugins.
eduardoofthehour
@eduardoofthehour
@halirutan Hi, I wasn't aware of this, this sounds much better, in terms of locking yourself into a product.
oscu0
@oscu0
What's the timeline on 2020.1 support?
Patrick Scheibe
@halirutan
@oscu0 Is already supported as a beta version. You just need to turn on the beta-repository in IDEA
@oscu0 Here is how it's done in a few seconds: https://wlplugin.halirutan.de/docs/installation/#using-eap-beta-releases
Patrick Scheibe
@halirutan
For the official release, I need another 2 weeks, maybe shorter depending on my work-load. I'd like to recheck the support for Mathematica 12.1, which will also be part of the release.
Adam Hill
@adamhill
For the record, Slack is much worse for communities. It kills searchable history after 10000 or so messages. If Gitter is not acceptable, Discord is much better alternative.
Patrick Scheibe
@halirutan
@adamhill One major point for going to Slack is not that Gitter is bad. It's that I'll go crazy otherwise with all the different chats :)
Just to give you an impression: (1) The Wolfram chat and my workchat is RocketChat, (2) Jetbrains developers; our own Mathematica chat; Kotlin; and a few more are on Slack, (3) JabRef, Rubi, and currently this is on Gitter, (4) all StackExchange things are on the StackExchange chat..
Patrick Scheibe
@halirutan
So to be clear: I'm not abandoning this Gitter channel completely, but I don't check it daily. Since @szhorvat, my main tester and fellow sufferer of Wolfram bugs, is also on Slack we moved the discussions for the upcoming 2020 release there since my Slack client is running anyway.
Patrick Scheibe
@halirutan
We use Slack really as a chat and everything that needs to be preserved is properly documented. The nice thing with our Wolfram Language Slack is that it's a general chat and the IntelliJ plugin is only one part of it. You'll find a lot of experts there like Anton Antonov (recent WRI streams about statistic), Axel (developer of Symja), Cory Walker (developer of Expreduce), Robert Jacobson (expert on Wolfram Language syntax, who works on the Wolfram Language Spec), and Szabolcs Horvat (developer of LTemplate and IGraphM). Just to name a few.
Syd Geraghty
@sydgeraghty
@szhorvat Hi Szabolcs ... Thanks for the message on LinkedIn .. I do not have your email address so please contact me on sydgeraghty@mac.com Cheers ... Syd Geraghty