I want to change the default layout of Window's Powershell so that it can expand to entire screen.
I tried from properties option.
But when I click the ok button, I am getting below error in Windows 8.1
Unable to modify the shortcut:
Check to make sure it has not been deleted or renamed
Settings get reflected even getting the above error, but it reset to its original settings after reopening of Powershell.
Edit the "Defaults" which is in the menu above "Properties". This will persist your changes even after closing and re-opening the window.
You should be looking at setting up your Powershell profile. The profile file is usually kept in your user location and contains, amongst other things, the settings for your Powershell session.
This should get you started: http://www.howtogeek.com/50236/customizing-your-powershell-profile/
And there's plenty of reading here on SO if you search for 'Powershell Profile'.
Related
I edited the settings file and there must have been a typo and now the app crashes on startup.
Online the documentation says the settings lives in $env:LocalAppData\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
I can't figure out what that path means since it doesn't exist on the computer.
I re-installed the app to fix the problem then made sure to see what the actual path is.
It's located in : C:\Users\{USERNAME}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState
In the current version (1.7.1033.0), the application can open the JSON settings file for you via a button. Open the Settings tab, and the bottom left corner will have a button named "Open JSON file". Clicking that button will open a prompt asking with what application to open the file. That text editor can then tell you where the file is located.
If you open the terminal settings, it will open a text editor with the settings.json file. If your default editor is VS Code it will show you the path below the tabs on the top of the screen.
I'm unsure what other editors show you the path, but if it is crucial you can change your default text editor to Code.
There is still the option to open the JSON file through settings. In version 1.15.2875.0 you can still find the "Open JSON file" at the bottom left corner
Screenshot with highlights
This hint was given by a comment by user1340531:
Mine is at C:\Users\{username}\AppData\Local\Microsoft\Windows Terminal\settings.json
(or more generically: %userprofile%\AppData\Local\Microsoft\Windows Terminal\settings.json)
If it's not there, you should consider OP's answer or vyps comment which lets you find out one of these generic paths (they are equivalent):
%userprofile%\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState
%LocalAppData%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState
$env:LocalAppData\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState
If you don't know what these paths mean, I'd recommend playing around with "Windows Run" (Win+R) and the explorer address bar.
I have reinstalled Visual Studio Code and for some reason, when I do the Ctrl+Shift+` shortcut, instead of opening a terminal window inside VS Code, it's opening an external command window, which is very annoying.
Anyone knows what setting it is to get it back internally?
I tried File->Preferences->Settings->Terminal and then set the first option "Customizes what kind of terminal to launch." to integrated.
Is there any other setting I need to set?
Happened the same with me. It was because I was using Legacy Console. To disable that, open any of your terminal (cmd or powershell) and right click to go to properties.
Properties -> Options -> Use Legacy console (tick it off).
Turn off ConPTY integration in the
File->Preferences->Settings->conPTY->Uncheck it
This is worked for me as mentioned here: https://stackoverflow.com/a/56267064/2462531
Found this:
https://github.com/microsoft/vscode/issues/72033
Which is listed as a duplicate but someone was also kind enough to link to this:
How do I get around the verified bug in Windows 1903 and launch the VSCode integrated terminal?
Which has a workaround as an answer, yay!
Here's some things you can check:
Make sure you've set integrated on both the User and the Workspace settings, because the Workspace settings can override the User settings.
Make sure you are using the correct keyboard shortcut. VS Code actually has a shortcut for opening the system's native console, which will open an external window:
Make sure that your Ctrl+Shift+` is actually the shortcut for Create New Integrated Terminal:
I'm trying to change the default path of the integrated terminal in Visual Studio Code, but I'm not sure how to. I do know how to change it in the windows command prompt, but not in Visual Studio Code. I looked in user settings, but I can't find anything there to change.
The current default path is C:\Users\User_Name.
I'd like to change it to C:\Project.
How do I do this in Visual Studio Code?
Short answer
Edit the user preference "terminal.integrated.cwd": "" to the path that you want the integrated terminal to open to.
Long answer
The same answer, but the long step-by-step version,
In Visual Studio Code go to:
Menu File → Preferences → Settings
Now that you are in the "User Settings", using the "Search Settings" bar across the top of the window paste or type this:
terminal.integrated.cwd
It will list the following as a result:
// An explicit start path where the terminal will be launched, this is used
as the current working directory (cwd) for the shell process. This may be
particularly useful in workspace settings if the root directory is not a
convenient cwd.
"terminal.integrated.cwd": "",
You will notice that it will not let you type here to change this setting. That is because you can't change the default setting. You instead need to change your personal settings. Here's how...
Click the pencil icon to the left of the this option and then the "Copy to Settings" option that pops-up.
You should have a split screen in which the right side of the screen has the heading Place your settings here to overwrite the Default Settings. This is the correct place for you to make changes. You might already have a few personalized settings listed here.
When you clicked "Copy to Settings" it automatically added this line for you:
"terminal.integrated.cwd": ""
Notice that whichever item is last in this list will not have a trailing comma but any items before it in the list will require one.
FYI: you could have simply typed or copy/pasted this into the personalized settings yourself, but following these steps is the process to learn for changing other preferences as needed.
Now you are able to type to set the path you want to use. Make sure to use \\ in place of \ and you do not need the trailing \. For example including this line would always start your terminal in the baz directory:
{
"terminal.integrated.cwd": "C:\\Users\\foo\\bar\\baz"
}
To apply the change, simply Save and restart Visual Studio Code.
As others have already explained, you can add a setting to change the default folder for your integrated terminal to start in. This setting also accepts Visual Studio Code variables, so to make a relative path from the root folder of your workspace you can use ${workspaceFolder}.
For example, for your terminal to always start in the subfolder mystart, your setting would be:
"terminal.integrated.cwd": "${workspaceFolder}/mystart"
Thanks for the original answer from Peter. Definitely helped !
It has now slightly changed in more recent versions of VS Code.
Navigate to File -> Preferences -> Settings
Type cwd in search
Choose Terminal > Integrated: Cwd settings
Type the default path you want to set in the text block below (simply, no need for double hashes to escape)
No need for saving, It's automatic
Restart VS Code
terminal cwd screen
Try this option in the "Intergrated Terminal" section of Settings.
"terminal.integrated.cwd": "",
You can also set it to a relative path to the open folder with
"terminal.integrated.cwd": "./example"
So if you do menu File → Open Folder... → project, and open the terminal with your keyboard shortcut, it will open to ~/project/example automatically.
It can be a general folder like src you would always use, or a specific one (but then it would be best to save it in file .vscode/settings.json).
The below option will help you do this.
Menu File → Preferences → Settings.
Add or edit the below setting.
terminal.integrated.shell.windows": ""
From the next terminal it will be reflected.
And add file .profile to your default shell, and add the default path to it.
More information can be found
at Integrated Terminal.
I have a development tool that's crashing on launch, and I don't get to see any error messages it throws, or get a chance to debug it, because it shows the Windows 7 dialog for crashed programs, where it says "Windows is checking for a solution..."
I want to have my old school big ass assert dialog box back, with a big "DEBUG" button. I have JIT completely enabled in Visual Studio's options and settings, so I'm not sure why I'm not getting the option.
Use Regedit, navigate to the below path:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\DontShowUI]
Create a DWORD and set the value to 1.
This blog post on raymond.cc contains an expanded version of the steps suggested in Krzysztof John's answer.
Quote:
Turn Off The Error Dialog Via The Registry
Although editing the registry manually is not recommended for average users, sometimes there isn’t a choice because something like the Group policy Editor might not be available in your version of Windows or the group policy method itself doesn’t work. This works on Windows Vista and above.
Open the Registry Editor by typing regedit into the Start search box or the Win+R Run dialog.
Navigate to the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting
Double click the DontShowUI entry on the right and change its value to 1, then close the registry editor.
. . .
The above registry fix will turn off the popup dialog for the current user, if you want the setting to affect all users on the computer then a similar registry key needs to be created in the registry at HKEY_LOCAL_MACHINE. This key isn’t present by default so needs to be created.
Read More: https://www.raymond.cc/blog/disable-program-has-stopped-working-error-dialog-in-windows-server-2008/
control panel -> troubleshooting -> change settings
In my case this solved same problem:
Control Panel\All Control Panel Items\Action Center\Problem Reporting Settings
set to "never check for solutions"
On my old Windows Vista Home Basic install, the option is hidden in a completely different place beneath the control panel:
Control Panel → Classic View → Problem Reports and Solutions → Change Settings → Advanced Settings → “For my programs, problem reporting is: [×] Off”
On Eclipse, whenever I double click a tab, it fills the workspace (by hiding all other views like project tree, console, etc).
Is there any way to do this on Visual Studio?
Note: i'm not looking for full screen, just want a way to declutter the workspace but still have access to menus.
Are you after this?
Set shortcuts for the Window.AutoHideAll function and for the Window.ResetWindowLayout function. In order for the ResetWindowLayout to work, you have to export your settings (make sure you select "All Settings") with all windows expanded and then import them again.
ResetWindowLayout will restore all windows to the way they were the last time you imported your settings.
Not with double click on tab, but you can do the same with Shift+Alt+Enter key combination.
This keyboard shorcut was changed to F11 from 1.9.1 vscode version.
All keyboard Shortcuts: https://code.visualstudio.com/shortcuts/keyboard-shortcuts-windows.pdf
I was looking for that, as well, and I now just got used to using full screen (Shift+Alt+Enter), which hides a little too much, which you seem to think, as well, but does in fact still show the menus.
Looks like drby got it on this one. Just FYI. I pinged the VS team to ask about this and here is the response:
"There is no way to reverse the command automatically. For it to work as a toggle we would need to save which toolwindows were auto hidden and which ones were not when the command was run, which we don’t do (it would cause lots of interesting persistence questions, across profiles and VS sessions)."
The idea of a "Unhide All" command is what I suggested. So if you hide all then you can unhide all as well. There might be some windows you don't want to unhide but the 1 or 2 extra windows is better than not having an unhide IMHO.