Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should startup.msl really be required? #5

Open
jfschaefer opened this issue Feb 27, 2019 · 0 comments
Open

Should startup.msl really be required? #5

jfschaefer opened this issue Feb 27, 2019 · 0 comments

Comments

@jfschaefer
Copy link

I tried to set up the kernel. During the configuration, I had the problem that I don't have a startup.msl file, which appears to be necessary.

Without the file, I get the following error, which prevents the kernel from launching:

[I 15:06:12.044 NotebookApp] Creating new notebook in 
[I 15:06:12.911 NotebookApp] Kernel started: 62334c33-e208-4584-aa20-8a10e8c2fcef
Argument /home/jfs/MMT/deploy/startup.msl cannot be used: /home/jfs/MMT/deploy/startup.msl is not a file.

Creating an empty file there solves the problem.

Since the meaning of the startup.msl file is not clear to every user and it doesn't seem to be generated for everyone by default, I suggest to make it optional (and make that clear in configure).

@jfschaefer jfschaefer changed the title Should startup.mls really be required? Should startup.msl really be required? Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant