I already read answer to this question on stack overflow which did seem to work....UNTIL... until I closed VS code. when I opened it again, I had to go to settings.json file, make some change and do ctrl+s for it to work it again. So the question is, what do I do so that it won't need me to go to settings.json file every time I open my VS Code for the mouse scroll sensitivity change to work.
Related
Whenever I use autocomplete, VSCode automatically puts whatever I type in a selection, it didn't happen before and it only started happening recently.
Here's what happens:
I type something like this and suggestion comes up:
Then I press enter to auto complete:
All of this is fine, but when I start typing in the quotes:
VSCode automatically puts my text in a selection. This causes multiple problems. Suggestions get disabled in selection and I have to press Esc everytime I want the selection disabled.
Is there any way to fix this?
The question was already answered by #Anton Solomin and #devanil. The issue is VS code auto-suggestion is not working when text is highlighted, because some of your code snippet is preventing quick suggestion by VS code.
So just tell VS code that don't disable quick suggestion if some snippets askes you to do it.
Go to VScode settings page, in settings search bar type editor.suggest.snippetsPreventQuickSuggestions
Uncheck Controls whether an active snippet prevents quick suggestion
If I am editing a file in VS Code, then alt-tab (or click) another program to view something else, then go back to VS Code, the focus has shifted over to the side panel, which prevents me from immediately typing in the editing panel. I find it really annoying to have to change the focus back to the editing panel every time (by either clicking or using keyboard shortcuts). Is there a way to have VS Code keep the focus where it is until I change it, even if VS Code is in the background for a bit?
This does not happen when my workspace is a local folder, but it does happen when my workspace is a remote folder connected via SSH (using the "Remote - SSH" extension).
When I attempt to save my file on Visual Studio Code with the cmd+s keyboard shortcut, it does not save the code. I have to manually click File, the Save, just to be able to save my progress. I'm using macOS Catalina version 10.15.7 and VC Code version 1.55.2.
How do I fix this?
Attempts:
-Checked if ⌘ Cmd + S keyboard shortcut is tied to the Save functionality
If you do it right this solution will fix your issue.
I have never had a problem saving with VS-Code personally, but I have had issues with keybindings. IDK if you write your own keybindings, but if you do, you might want to check the keybindings that you have wrote to make sure they do not conflict with [CTRL + S]. The keybindings.json file that you create custom keybindings in, overrides the default keybindings.json file that defines the keybindings that VS-Code ships with.
To check your keybindings.json file...
Hit the F1-Key
A menu will drop open type in "Keyboard Shortcuts"
There will be two Preferences: Keyboard Shortcuts
Make sure to select Preferences: Keyboard Shortcuts and not Preferences: Default Keyboard Shortcuts
If the file is empty you are good. If you have keybindings written in the file, you need to iterate through them by hand, checking each one. Make sure that none use [CTRL + S] together. Even if the keybinding uses [CTRL + S] and other keys, you will need to disable it, so you can test if it is causing an issue.
Debugging [CTRL + S]
If your keybindings.json file is all good, then great, that's one thing to scratch off the list. The only thing left to do now is debug the Bound Key ("Key Binding"). To debug keybindings, you will use a built in tool, that VS-Code offers. To start do the following:
Hit the F1-Key
When the quick input drops open type the following into the text input:
"Toggle Keyboard Shortcuts Troubleshooting"
Select the option: Developer: Toggle Keyboard Shortcuts Troubleshooting
It should automatically open the OUTPUT panel, which is located in the same panel that your terminal is. Make sure that the OUTPUT is set to LOG(Window) in the drop down. (I took a picture and posted it below if you can't find the Keyboard Shortcut Troubleshooter).
The image might have funny declensions because I am on a dual monitor setup with 1 1080x1920 curved screen and one 1080x720 screen.... I cropped it to a STD HD 1920 width.
I Got My Trouble-shooter working, and Output open, now What Jay?
Okay... Well your at the right spot. Now every-time you press some keys, you should see your OUTPUT WINDOW working like crazy. It should be logging all sorts of stuff, which is good, very good.
This Part Is Important! READ CAREFULLY
What you want to do is use your keybinding that you feel isn't working appropriately. Use it when focus is set on an editor, use it when focus is set on a different editor, use it when focus is set on the sidebar. Where you are focused at in the editor at any given time can greatly affect a keybinding. The output is gonna write lines every-time you use your keybinding. Try not to hit any other keys while doing this, so you have a column in you output that includes logging from the keybinding you are testing only. Read the output see what it says. See if it looks right, or wrong. If it looks wrong, you can visit this link, to the VSCode site that covers this topic, and see if you can fix it your self. If you can't fix it your self, come back here, and edit your question. When you edit your question make sure that it includes the Troubleshooter's Logging Output.
VSCode Troubleshooting Keybindings (Keyboard Shortcuts) # https://code.visualstudio.com/docs/getstarted/keybindings#_troubleshooting-keybindings
Image that shows how to open the Keyboard Debugger
Also shows how to set the OUTPUT to Log(Window)
StackOverflow-2021-JUNE-26018:34-PST
Another thing to check for is, for lack of a better term, combination key bindings. For example, I was having an issue with ⌘+s. VSCode gave a message that it was waiting for the second key binding. After looking at the keybindings.json, I noticed I had a key binding for opening up user snippets as
{
"key": "cmd+s cmd+n",
"command": "workbench.action.openSnippets"
}
The ⌘+s portion of this key binding conflicted with the default ⌘+s
The MATLAB GUI normally (for me) has 4 tabs in the upper left - Home, Plots, Apps and (I think) Editor. However the editor tab has disappeared and I cannot find documentation how to turn it back on. I tried the Layout->Default but that just arranges all the visible windows and doesn't re-enable to missing editor.
Does anyone know how to turn this back on?
Type edit in the command window.
Unfortunately you are right, there is no 'Editor' option in the Layout panel of Matlab's interface, and for obscure reasons it's not present in the default layout.
OK, I've checked Ratbert's answer as he got here before me but Mathworks tells me it disappears any time you're not actually editing any code. If that happens their answer was to just click on the New Script button. Doing that worked for me. Typing edit in the command window is (I think) doing the same thing.
Thanks!
For anyone that finds this thread at a later date I eventually debugged the root cause of this problem as a mouse that was failing. When attempting to close the open variables part of the GUI, when clicking the X in the upper left, the mouse was generating two clicks instead of one. The first closed the variables GUI, the second closed the editing GUI. Purchasing a new mouse resulted in no longer seeing the problem at all.
in matlab command window, go on top right triagle and click, a drop down list will appear, select undock editor
This question already has answers here:
How do I stop VSCode from the Side Bar moving to the folder that the current file is in?
(3 answers)
Closed 2 years ago.
Is there a way to prevent VSCode from jumping all over the place when closing a tab? It jumps to the location of the selected tab, but this is very disorienting when opening various files to inspect within a lib.
This behaviour is controlled by the following setting:
"explorer.autoReveal": false
There is currently no setting for keeping the selected file in the explorer, but this one at least keeps the scroll position fixed and prevents the "jumping".
Update
In current versions, the same setting now keeps the selected file.
After you apply "explorer.autoReveal": false, as mentioned above, you can also set up
a shortcut to force show the current file in Explorer:
{ "key": "cmd+e", "command": "workbench.files.action.showActiveFileInExplorer" }
As commented in issue 23902 (Option to keep file selected in sidebar without forcing a scroll)
If set autoReveal to true, the jumping inside file explorer is confusing;
If set autoReveal to false, I have to use showActiveFileInExplorer keybinding or right click menu every time when switch between tabs
But with VSCode 1.46 (May 2020) you now have:
Explorer auto reveal focus without forcing a scroll
There is a new option focusNoScroll for the explorer.autoReveal setting.
When using this option, the Explorer will automatically select files when opening them but will not scroll to reveal them in the Explorer view.