-
Notifications
You must be signed in to change notification settings - Fork 293
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
Jupyter Notebook Behavior Differences in VS Code vs VS Code Insiders #6045
Comments
@amitktripathi Currently VSCode-insiders contains our new UI that we will be slowly rolling out into stable over the next releases. Thanks for providing the feedback on it. I believe that we already have an issue covering the markdown not executing, but not on the other issues. We can look into these changes. |
Just for a clarification or two. For Rendered fonts you mean fonts in the notebook output, correct? Font family (and all other editor setting should still control the input code cells). |
@IanMatthewHuff That is correct. The font used in the markdown cell during editing is the one specified by Also, thank you for looking into other issues. |
I found some other issues using Jupytor notebook with VS Code Insiders: https://github.com/microsoft/vscode-jupyter/issues/6094 |
M & Y shortcut is covered by #4438 |
The rendered font size is too small for me as well. To increase the font size, I used the Customize UI tool. I hope it will be possible to increase the font size within the VC code setting soon. The font size is almost the same between the stop editing vs editing: |
I just filed an issue upstream on VS Code for the markdown text size rendering. I don't believe that there is a current setting for this. |
Something else I noticed: the rendering of error messages when running code cells is also noticeably harder to read than it used to be. Note that I am using VSCode default Light Theme (Light+). Is there currently a way to make this a bit easier on the eyes? (the green is not great in either the interactive view or the notebook, but in the notebook the green is unreadable) |
@mtsitzer That's a good suggestion, would you mind filing that as a new issue? The feedback here is great, but when multiple issues get into one thread it can be a bit hard to track the resolution on our side. |
Reading through, it appears that all of the issues noted have been addressed or reference another open issue. So, closing this one. If there was something missed, please open a new issue. Thank you! |
I recently gave VS Code Insiders a try and its impressive. The main reason I was trying Insider edition because I could not use Python extensions in Jupyter Notebook in VS Code. Interestingly I can do those in Jupyter Notebook in VS Code Insiders edition. However, I am finding the Markdown cells in VS Code insiders behaving strangely.
Few issues in VS Code Insiders while using Jupyter Notebook:
Using VS Code 1.56.2
Using VS Code Insiders 1.57
VS Code - 1.56.2
VS Code Insiders - 1.57
Windows 10
(If this report has incorrect format, I apologize. First time posting issue/feedback on git)
The text was updated successfully, but these errors were encountered: