wolfram-language-notebook icon indicating copy to clipboard operation
wolfram-language-notebook copied to clipboard

**Can't open new Wolfram Notebooks**

Open fkhorad opened this issue 2 years ago • 6 comments

Describe the bug After an apparently successful installation, opening new Wolfram Notebooks fails with an error "command wolframLanguageNotebook.newNotebook not found" (screenshot attached). The same happens with the Manage Kernel command.

Expected behavior A new notebook should open.

Screenshots image

Environment (please complete the following information):

  • Operating system: Ubuntu 20.04.4 LTS
  • Mathematica/Engine: 13.0.0
  • VS Code: 1.64.2
  • Version: 0.0.9

Additional context I've checked that the wolframscript command does work as expected from the CLI, and that there are no running Wolfram processes when trying to open a notebook. I was able to make the extension work on another machine (which, however, runs Windows).

fkhorad avatar Mar 03 '22 17:03 fkhorad

It might be an issue related to snap (#6).

njpipeorgan avatar Mar 05 '22 07:03 njpipeorgan

Exact same issue here, latest OSX, vscode (M1 processor). Anything we can do to debug the issue?

stepelu avatar Mar 27 '22 06:03 stepelu

Exact same issue here, latest OSX, vscode (M1 processor). Anything we can do to debug the issue?

The extension does not work on m1 macbook natively (#4) due to the dependency on zeromq. But running vscode with rosetta 2 seems to be working.

njpipeorgan avatar Mar 27 '22 22:03 njpipeorgan

@njpipeorgan zeromq is now supporting macOS arm64 as described https://github.com/zeromq/zeromq.js/pull/522 here.

Will this issue be fixed by updating the zeromq dependency?

SaltyChiang avatar Feb 19 '23 15:02 SaltyChiang

I am also facing the same issue on M1 Mac.

gaurav-src avatar May 23 '23 13:05 gaurav-src

I am on a mac too, but with Intel processor. Same issue here. MacOS Ventura 13.5.1 and Wolfram Engine 13.3. It worked a while ago for me, so it might be the upgrade to Wolfram Engine 13.3 or some problem with a newer version of VSCode or the Plugin itself. I cannot tell.

The3DWizard avatar Nov 26 '23 10:11 The3DWizard