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

shift/ctrl + enter adds new non-interactive cells with no cursor #16136

Open
1 of 2 tasks
AusafMo opened this issue Oct 22, 2024 · 1 comment
Open
1 of 2 tasks

shift/ctrl + enter adds new non-interactive cells with no cursor #16136

AusafMo opened this issue Oct 22, 2024 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@AusafMo
Copy link

AusafMo commented Oct 22, 2024

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

Image

Running the shell adds new cell but without the cursor, The new cells (happens multiple times in a row) completely non-interactive.
After restarting kernel or spamming shift+enter for a couple times, the cursor appears again.

VS Code Version

1.94.2 (Universal)

Jupyter Extension Version

v2024.9.1

Jupyter logs

No response

Coding Language and Runtime Version

python 3.12.7

Language Extension Version (if applicable)

v2024.16.1

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Local

@AusafMo AusafMo added the bug Issue identified by VS Code Team member as probable bug label Oct 22, 2024
@amunger
Copy link
Contributor

amunger commented Oct 22, 2024

Is this happening consistently? Is there specific code in the cell that causes this to happen?
Are other cells behaving normally while this is happening?

@amunger amunger added the info-needed Issue requires more information from poster label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants