Command mode in Jupyterlab - jupyter

Does jupyterlab ditch the Jupyter notebook editing and execution norms? I can not do the simplest action- that is to toggle into/out of the command mode using escape. Instead the notebook remains in edit mode on the current cell.
Generally I am also at a loss on how to navigate among the various tabs and to/from the Editor pane using keyboard only. An IDE must have strong support for keyboarding or it is the wrong one for me. Hopefully these shortcuts exist but I was unable to find them yet.

Related

Visual Studio Code Jupyter Notebooks: Keyboard shortcuts not working

I am trying to get the integrated Jupyter environment up and running for my VSCode installation. I have the Jupyter extension enabled and can edit and run Python and Markdown cells without issue. However, none of the default keyboard shortcuts work when I am in edit mode. For example, in the below screenshot, I am trying to advance to the next cell using 'Ctrl+Alt+]' but nothing happens when I am in the editor. I believe the criteria for using the shortcut in the "when" column are met which is why I am confused. Am I not in the right context for the shortcut, or am I missing something?
https://imgur.com/a/HjIxAoX
I tried all the stated keyboard shortcuts, making my own keyboard shortcut, reinstalling the extension, looking for similar issues online. This issue does not appear to exist in the same form here.

How to disable Ctrl+Enter full screen toggle in AWS Amazon Workspace function?

I recently learned that pressing Ctrl+Alt+Enter while in an AWS workspace will toggle full screen mode. I tried that and it worked. But now when I press Ctrl+Enter it too toggles full screen mode which I do not want. Ctrl+Enter is a very common and unique function for my job that it's hard for me to remember not to use it and even if I do the alternative involves additional steps/time. Is there any way I can disable the Ctrl+Enter key binding for AWS workspace?
The workspace restarted itself later in the week. I suspect for a Windows update. The restart or the update fixed the issue.

In VS Code, how do I bring the terminal up to the code editor section (without resizing the terminal)? "Terminal editors"

After getting more comfortable with awslogs, I am wondering if there's a way to actually open up or bring a terminal to the code editor view. For example, here's what I see in my iTerm2 app:
I don't really use iterm2 too much if I have to do some editing of files, but having this inside of VS Code in a tab would be really nice. Just would allow me to make changes to the Dockerfile and monitor the progress of the build from AWS.
Here's where I would like it to go:
I understand that this isn't really a "terminal" spot per se since it's typically at the bottom, but I was just curious to see if there was a way to do it without affecting the terminal on the bottom. In some rare cases it would be nice to attach to a tmux session from the code editor window so I can flip between that and code.
In the Insiders build now, and so presumably will be in v1.58, is the ability to put a terminal into an editor like you ask. You can also drag a terminal into the editor area to crop it there!
There are these commands:
Terminal: MoveTerminal into Editor Group
Terminal: Create Terminal Editor
workbench.action.terminal.moveToEditorInstance

How to expand VSCode's Interactive Terminal's text font

I've been working on a bunch of different projects in VSCode and just to clear up some space on my desktop I decided to quit all VSCode applications. Upon reopening it, the Interactive Terminal's text too small to read. I know you can just launch terminal and execute the same command but out of convince's sake I want to be able to increase the size of it again. Example of my issue
You can change the terminal display settings with this configuration in your settings.json.
I saw your photo, and it looks like there is some minor problem. Just reload your window - Command + R on macOS, or select Developer: Reload Window after opening the command palette. That should work.

New to VSCode, can't disable sidebar

I am new to VSCode, long been a holdout with Powershell ISE. I am in a situation where I am doing more with PS7, so have no choice but to use it. The one thing that I cannot seem to find is a way to permanently disable the sidebar. Every time I run a script the stupid thing pops up, and I have to hit CTRL+B to close it. I have tried going into Powershell language specific settings, but the only option I see is sidebar.location.
Is there any way to permanently stop this from popping up?
Here is the solution:
go to settings
search for Debug: Open Debug
choose never open
Allow me just say this. I too use VSCode, Sapien's PS Studio, and the ISE more than the previous two, but also use PowerShell v7.
So, FYI... You do have a choice, You can use PowerShell v7 from the ISE. I do this every day. Well, it's a workaround to do so, but it works just fine.
Here is one of the ways to use PowerShell v7 in the ISE.
Using PowerShell Core 6 and 7 in the Windows PowerShell ISE
The other way I use it is just shelling/branching out to it as needed.
Yet, your question is really a duplicate of this Q&A.
Is there a shortcut to hide the sidebar in Visual Studio Code?
And these potential answers...
you can hide the activity bar by setting up your own keybinding
(code.visualstudio.com/docs/customization/keybindings) for
workbench.action.toggleActivityBarVisibility
and or
In the VS code version 1.43, you can hide or show the side menu or
activity bar by going under the 'VIEW' tab in the nav bar in the top
margin of VS CODE(called the 'Menu Bar'). Go to View => Appearance,
there you can check or uncheck different nav bars to show/hide each
one.
If you have the top bar (Menu Bar) currently hidden press 'alt' key to
bring it back then follow above instructions to check it to keep it
there permanently if desired.
The thing to remember though is, that sidebar is your file/project explorer and as such critical for normal development. It's how you get to all your files. Sure, you can still get to them using F1 and type a name, but that's kind of painful, vs scrolling to find what you need or opening multiple files in a project at once.