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

Command Palette won't open #3074

Closed
Paul-Yuchao-Dong opened this issue Nov 23, 2017 · 12 comments · Fixed by #3122
Closed

Command Palette won't open #3074

Paul-Yuchao-Dong opened this issue Nov 23, 2017 · 12 comments · Fixed by #3122

Comments

@Paul-Yuchao-Dong
Copy link

I am working in with current version of Jupyter notebook. And I encountered a weird problem - the command palette won't open, even if I click on the icon just below the menu bar.

Server Information:

You are using Jupyter notebook.

The version of the notebook server is: 5.2.1
The server is running on this version of Python:
Python 3.5.4 |Anaconda custom (64-bit)| (default, Oct 27 2017, 11:35:13) [MSC v.1900 64 bit (AMD64)]

Current Kernel Information:

Python 3.5.4 |Anaconda custom (64-bit)| (default, Oct 27 2017, 11:35:13) [MSC v.1900 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 6.1.0 -- An enhanced Interactive Python. Type '?' for help.

The chrome console gave below error message:
capture

it seems new commandpalette.CommandPalette(this) called Jed.gettext which throw the error.

I've re-installed jupyter, but the problem persists.

Appreciate any help!

@takluyver
Copy link
Member

takluyver commented Nov 23, 2017 via email

@Paul-Yuchao-Dong
Copy link
Author

Many thanks for your time on this issue. For additional information, I am using Chrome Version 62.0.3202.94 (Official Build) (64-bit).

I have set the language to English and restarted chrome as below, yet the prolem persists.

image

@JCEmmons
Copy link
Contributor

JCEmmons commented Nov 27, 2017 via email

@takluyver
Copy link
Member

Any ideas why it might be failing? Or how to debug it? The error shown is definitely coming from Jed.

@uduse
Copy link

uduse commented Dec 8, 2017

Having the same problem here, on both Chrome and Safari. I work remotely on a notebook that runs on a server. Most other keys are fine, but no matter what I try I can't get the command palette show up. Not even a sign.

I tried remapping jupyter-notebook:show-command-palette to another shortcut and the same problem persists.

Any help will be appreciated.

@takluyver
Copy link
Member

Do you see the same error in the Javascript console?

@uduse
Copy link

uduse commented Dec 8, 2017

@takluyver yep, exact the same.

@takluyver
Copy link
Member

@JCEmmons do you have time to investigate this further? It's definitely coming from the translation machinery, and you're most familiar with that.

@uduse
Copy link

uduse commented Dec 8, 2017

Just to provide more information: my Jupyter runs on a Ubuntu server and I remotly access it on my mac. I am wondering if it is an operating system discrepancy problem.

@takluyver
Copy link
Member

There may be some discrepancies in the UI: parts of the translations are loaded depending on the environment variables on the server, and parts depending on the language you set in the browser preferences. But they shouldn't cause an issue like this.

@JCEmmons
Copy link
Contributor

JCEmmons commented Dec 8, 2017 via email

takluyver added a commit to takluyver/notebook that referenced this issue Dec 11, 2017
takluyver added a commit to takluyver/notebook that referenced this issue Dec 11, 2017
takluyver added a commit to takluyver/notebook that referenced this issue Dec 11, 2017
@takluyver
Copy link
Member

I think I've worked it out - hopefully #3122 will fix it.

@takluyver takluyver added the bug label Dec 11, 2017
@takluyver takluyver added this to the 5.3 milestone Dec 11, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants