Mathematica IntelliJ Plugin/Lobby

Patrick Scheibe

@halirutan

There you are using IGCommunitiesEdgeBetweenness::invopt which doesn't seem to have a definition anywhere.

Szabolcs Horvát

@szhorvat

@halirutan Oh, I’ve forgotten about this situation … I should have mentioned it in the feature request. It picks up General::invopt. Try Message[foofoo::invopt, 1, 2, 3] in a new session and it will work, without defining foofoo::invopt

Patrick Scheibe

@halirutan

@szhorvat OK, didn't know that.

Kuba Podkalicki

@kubaPod

@halirutan sorry for asking something that can probably be found somewhere but it is quicker to ask and go on as this is not what I critically need asap :)

How to find declaration without caret around the symbol? I tried Shift+Shift but it only lists symbols with usages, right?

(I also tried looking online but apparently people are expected to look for names they directly see as I can only find Ctrl+B references.)

Patrick Scheibe

@halirutan

@kubaPod Check item 3. in my latest comment on the goto message issue.

"Goto Symbol" will only list things were a symbol gets a value.

(The shift-shift search everywhere is new and I'm not sure I have to do something to incorporate things in this search)

Kuba Podkalicki

@kubaPod

Ah, sorry, only about now I received an e-mail about your answer.

p.s. structure view works for single files

Patrick Scheibe

@halirutan

Yes, the structure view only gives you the information about a single file.

Kuba Podkalicki

@kubaPod

Hmm, I just updated the plugin to 2019.2.1, restarted and intellij says there are no plugins with .m support

Patrick Scheibe

@halirutan

@kubaPod Which exact IDEA version are you using?

Patrick Scheibe

@halirutan

@kubaPod I'm guessing you don't use IDEA 2019.2. This was a mistake of mine. I updated to a newer API only available in 2019.2 but did not restrict the plugin to be installable only in this version.

Kuba Podkalicki

@kubaPod

Right, I heard about it so I should've known.

Updating now

Kuba Podkalicki

@kubaPod

@halirutan I have IntelliJ 2019.2 and plugin 2019.2.1.1 and still can't search for symbols that don't have usage messages via Navigate > Symbol

Basically I want to jump between package private functions that I don't write usages for

Patrick Scheibe

@halirutan

@kubaPod Yes, I know. The current limitation is that symbols you want to use project-wide need a message. I need to find a betters solution to index all definitions without bringing the plugin to a halt on projects such as IGraphM.

I have currently no good idea for this

Kuba Podkalicki

@kubaPod

That makes sense and for private function structure view is enough. Thanks.

Szabolcs Horvát

@szhorvat

Just installed the beta and will be using it today/tomorrow.

The “go to message” is great!

Kuba Podkalicki

@kubaPod

@halirutan just a thought, how difficult would it be to add "Export symbol" that would put it between BeginPackage and Begin? Sounds like something I'd use a lot but I don't desperately need it.

Szabolcs Horvát

@szhorvat

It's hard to do it in a general way ...

Kuba Podkalicki

@kubaPod

I know, though I suspect 80% of use cases would be to use it for a simple old style package so it may not need to be general.

Otoh would creators of such packages use that feature?

Kuba Podkalicki

@kubaPod

I just tried an IntelliJ MacOs shortkey combination on Windows machine with MMA FE... Thanks @halirutan ! :p

Patrick Scheibe

@halirutan

@kubaPod Hehe..

Kuba Podkalicki

@kubaPod

I was so surprised it does not work that I checked IntelliJ docs...

Patrick Scheibe

@halirutan

@kubaPod @szhorvat The "Export symbol" feature is not particularly hard, but it is very cumbersome to get it right with all the different file and package layouts we have. I guess I just need to sit down and write it up.

Szabolcs Horvát

@szhorvat

Otoh would creators of such packages use that feature?

@kubaPod

I would not use this much when working on packages that I release publicly.

I would use it a lot for packages I put together quickly for myself, as I tend to develop things quickly in a notebook, then copy and paste into a package as needed.

@kubaPod @szhorvat The "Export symbol" feature is not particularly hard, but it is very cumbersome to get it right with all the different file and package layouts we have. I guess I just need to sit down and write it up.

Looking at my own use cases, I would recommend to give this lower priority. There are other features/issues which would bring a bigger benefit if fixed.

Patrick Scheibe

@halirutan

@szhorvat

There are other features/issues which would bring a bigger benefit if fixed.

Yes, I agree. One project of immense work is to the free WL kernel integrated properly and most of all, see if we can support Jupyter notebooks.

Szabolcs Horvát

@szhorvat

Recently I tried the official Wolfram Jupyter kernel again because we are having a summer school here at the moment and I was thinking about whether the students could have used the free Wolfram Engine.

Unfortunately, more than one, the system just hung for no apparent reason. Evaluations would not return. It was random, and seemed to happen when a call to the front end was necessary (e.g. graphics rendering).

Kuba Podkalicki

@kubaPod

:heart:

Patrick Scheibe

@halirutan

@/all All of the things I worked on and that are fixed can be seen by watching the milestone for the next release.

One things that is not mentioned in the issues is that I have worked on the Parenthesizer which lets you display the order of evaluation

Patrick Scheibe

@halirutan

I have polished this feature enough so that it is now available in the Wolfram Language menu or via the shortcut Ctrl+Alt+Shift+9 (so basically Ctrl+Alt+( on most keyboards).

It will put parentheses into your current file (the cursor must be blinking in the file to use this feature). It puts your file into read-only and once you verified that the evaluation order is OK, you can press Esc to remove all parens and continue working.

All closed issues are available in the latest beta build. If we don't have major issues, I would push this as official next minor update later this week.

Kuba Podkalicki

@kubaPod

:+1:

@halirutan tangentially related question, should I close an issue which I labeled as "wontfix"? I am experimenting with project management via github.

Patrick Scheibe

@halirutan

@kubaPod No, leave them for me when I'm emotionally ready to close them :)

Kuba Podkalicki

@kubaPod

@halirutan I mean in general :)

Not for Plugin repo

Patrick Scheibe

@halirutan

Oh.. well, that's up to you. Usually, I would say yes but the tag wontfix isn't the best one anyway. A better tag would be wontfixnow and then, you could leave them open when you consider implementing them.

Kuba Podkalicki

@kubaPod

@halirutan right, I realized that there should be wontfixever+closed and wontfix-unless-runoutofissues.

Where communities thrive

People

Repo info

Activity