I clicked something which I have absolutely no clue of and now every-time I click on 'New Terminal', I am being presented with an external PowerShell window rather than the integrated terminal. Any clue how to set it correctly (or should I say more aesthetically)?
Current Situation:
Expected:
I have uninstalled and reinstalled the program, no change.
The issue is resolved by unchecking Use Legacy console in PowerShell
Current State:
Related
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:
UPDATE 16-02-29:
I managed to fix this error by trying to build from the sources hosted on github. Building this way worked but I suspect the fix had something to do with either me downloading powershell 4.0 or Microsoft Build Tools 2015, because I was prompted to update after starting cmder and the bug was still gone even after update. The fix might have also been from editing the init.bat file to point to my manual install of the latest conemu before building. I'm not sure.
ORIGINAL POST:
I'm following a tutorial to setup vim on my Windows machine. I have a weird bug though where when I scroll down on a file in Vim, every other line gets highlighting and will go away if I move the cursor up to those lines.
Like this:
This seems like a screen refresh issue of some kind. There's a similar problem, not sure if related, where sometimes when I got back to cmder after quitting vim the prompt will be placed in the middle of the previous outputs and will start to overwrite these previous lines as commands are executed. This is fixed either by a cls or restarting cmder.
Tutorial: https://www.youtube.com/watch?v=NPtJ4TquQZY
I used to get to the bottom of a webpage by pressing CMD+Keydown. Did they remove this shortcut or is it just me?
I know this used to work not too long ago and it's not working since one of the newer versions... (currently Version 31.0.1650.57)
CMD+Keyup still works just fine.
So I finally got around the problem:
An extension I was using got some automatic update, in this it used CMD+Keydown as a shortcut for the extension, which overwrote the default behavior.
The problem hereby was, that the programmer was not done, so he "seized" the shortcut, but was not using it for anything.
Now after more than 2 months, after an other automatic update, the shortcut triggered something in this extension, so I could find out what was causing the shortcut not to work.
Then I just disabled that shortcut for said extension. All working now :D
This is just plain weird.
For some reason, the accelerator Cmd-Opt-L (reformat code) no longer works inside IntelliJ 10. This started with one of my projects and seems to have "spread".
Other accelerators work normally. Reformat works if I use the menu to select it, or Cmd-Shift-A and choose it from the "Find action ..." popup dialog.
I've tried to see if some conflicting application is the cause. I'm using 1Password and it defines an accelerator for Cmd-Option-L, but I disabled that, restarted IntelliJ and still no dice.
A quit-and-restart doesn't help.
More oddness. I pulled down the Code menu and typed Cmd-Opt-/ ... I can see the menu item flash and then my editor updates. If I pull down the Code menu and type Cmd-Opt-L, there's no reaction (the menu line for Reformat Code does not flash, the menu stays up). So ... one theory is that something elsewhere on my Mac is consuming the Cmd-Opt-L before it gets to IntelliJ? If that's so, how would I track it down?
Your theory is correct. As a workaround you can remap reformat code action to different shortcut in Settings | Keymap.
As for tracing the offending application, I'd try killing one by one and see when it starts working again.
I've just had a strange problem show up with my XCode project. The project is one that I've been working on for 4+ years. Just today, when try to start debugging, the debugging view opens and the console says "[Session started at 2010-10-03 14:04:35 -0600.]" but nothing else happens.
It seems that the executable is screwed up. If I open up the executable's (I've only got one in the project) settings window, in the General tab, the drop down for "Use whatever for standard input/output" says "No Value" and there are no other options in the menu. On the debugging tab I see "When using whatever" but the drop down menu for that is completely empty, and again the drop down for "Use whatever for standard input/output" says "No Value" with no other options. Also interestingly, the "Start executable after starting debugger" option is unchecked. However, checking it doesn't stick. If you close the Executable Info window, then reopen it, the setting has reverted to off.
I've tried creating a new executable, but the same thing happens. Closing the project/reopening it and restarting Xcode also have no effect.
I noticed that someone with the same problem posted on the Xcode mailing list, but they got no real answer: http://www.cocoabuilder.com/archive/xcode/263804-debug-run-executable-does-nothing.html?q=%22no+value%22+standard+input#263804 .
Any ideas?
Have you installed anything lately? Do newly-created projects misbehave in the same way? Do you have backups (or version control) and, if so, does restoring the project to a former state also behave the same way? If yes to any, you might try reinstalling Xcode Tools.