8 ms·
Terminal is already in there and mentioned in the root link. Just press Ctrl+` and it will show up.
by pingec 10y ago
Terminal is already in there and mentioned in the root link. Just press Ctrl+` and it will show up.
- rcarmo 10y agoNeed to change that key binding... thanks to the US-centric take we've had on keyboards since the TTY days, that key combination doesn't make sense on a Portuguese keyboard.
- deleted 10y ago[deleted]
- noir_lord 10y ago// Place your key bindings in this file to overwrite the defaults [ { "key": "ctrl+shift+t", "command": "workbench.action.terminal.toggleTerminal" } ] Change to whatever works for you, I use ctrl+shift+t since I have that mapped in intellij and muscle memory is a terrible beautiful thing.
- rcarmo 10y agoAye, thanks. That's what I'll do, since I also use that in OpenBox when running Linux and it's much more intuitive.
- hrvbr 10y agoIt's Ctrl+ù on French keyboards. Maybe they customized it for Portuguese keyboards too.
- rcarmo 10y agoThey did, they're using Ctrl+ç, which is a nice way to use an otherwise useless key for programming, but hardly memorable or ergonomic for me - I'll go and use Ctrl-Shift-T as well, which is what I use in Openbox ;)
- monsieurbanana 10y agoI wouldn't recommend. What if you use VScode in openbox?
- lloeki 10y agoCMD+< here, found via CMD+SHIFT+P interm which I use anyway.
- deleted 10y ago[deleted]
- tekism 10y agoWow this is amazing! Do you know if you can run powershell in terminal? I just tried to run my usual powershell build cmd ".\build.ps1 Prod" for example but it launches notepad with the code for the powershell script.
- sgreenlay 10y agoYeah, you just need to change your terminal in settings: "terminal.integrated.shell.windows": "\\Windows\\system32\\WindowsPowerShell\\v1.0\\powershell.exe"
- code_chimp 10y agoOn my Windows 7 work laptop I just added the following to my settings.json: "terminal.external.windowsExec": "Powershell.exe", "terminal.integrated.shell.windows": "C:\\windows\\system32\\WindowsPowerShell\\v1.0\\powershell.exe"
- Tyriar 10y agoHi, I wrote the integrated terminal. The advice mentioned will open 32-bit version of Powershell, for 64-bit you need to use a different path: "terminal.integrated.shell.windows": "C:\\WINDOWS\\sysnative\\WindowsPowerShell\\v1.0\\powershell.exe" C:\WINDOWS\sysnative should be a symlink to C:\Windows\SysWOW64, see https://github.com/Microsoft/vscode/issues/7095#issue-157913681 https://github.com/Microsoft/vscode/issues/7095#issue-157913... for more info
- riskable 10y agoI just tried it out (finally, a terminal!) but I have a strange problem with it: I can't copy & paste text in the terminal. Ctrl-C sends the usual terminal escape sequence (which is good) but there's no right-click menu or alternate shortcut (that I can find) to copy from or paste into the terminal. Traditionally terminals auto-copy text to the clipboard or use a keyboard shortcut like `ctrl-shift-c`. To paste you typically use `shift-insert` or `ctrl-shift-v`. Am I missing something?
- taude 10y agoThey have in the release notes that Copy/Paste doesn't work yet, and that the terminal integration is pretty early.... "Please note, this is an early version of what we want to deliver. Currently VS Code only supports a single terminal and there still are missing features like copying and pasting with the keyboard. Windows 10 users may experience problems getting cmd.exe to work. If so, please try enabling the legacy terminal as described in #143"
- alexc05 10y ago> Just press Ctrl+` and it will show up. WOW! this is awesome!
- vonklaus 10y agohavent used straight up terminal yet, but I have done bower and yeoman inits presumably with the same interface. Works well. I like that they add features slow and seemingly balance performance. Atom was a great idea but throwing the kitchen sink in also seemed to creat crazy petf issues