 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2025/03/12
Boy, I always to the Ctrl+Shift+Space on Microsoft Windows (or on MacOS Command+Shift+Space) detour to switch to the Terminal tab in Visual Studio Code
So I was amazed to find the shortcut inside the first bullet in the Google Search quote of the first result at [Wayback/Archive] vscode terminal open new terminal – Recherche Google:
Posted in .NET, Apple, Development, Keyboards and Keyboard Shortcuts, KVM keyboard/video/mouse, Mac OS X / OS X / MacOS, Power User, Software Development, Terminal, vscode Visual Studio Code, Windows, Windows Terminal | Tagged: 143 | Leave a Comment »
Posted by jpluimers on 2023/05/26
In the continuing series of Chocolatey/Scoop/winget related posts, this one is about Windows Terminal.
There are basically two ultimate sources you can install it from:
winget install --id 9N0DX20HK701 --source msstore --accept-source-agreements --accept-package-agreements --silentwinget install --id=Microsoft.WindowsTerminal -echoco upgrade microsoft-windows-terminalYou can configure the Microsoft Store to automatically install updates as per [Wayback/Archive] Turn on automatic app updates (on my system this was the default):
Microsoft Store – Auto-Updates is turned on by default
As a backgrounder, here some articles on Windows Terminal, ConPTY and the Windows Console from the [Wayback/Archive] DevBlogs – Microsoft Developer Blogs:
More on (pseudo)terminals in general containing [Wayback/Archive] “ConPTY” – Search results – Wikipedia:
More on using the Windows Terminal:
My related blog posts:
–jeroen
Posted in Chocolatey, ConPTY, Microsoft Store, Power User, Scoop, Windows, Windows Terminal, winget | Leave a Comment »
Posted by jpluimers on 2022/12/08
For my link archive: some links related to the Visual Studio Code built-in terminal and its’ known issues.
This document is about reporting issues for the integrated terminal (ctrl+`). Learn more about how to use the terminal in the [W/Archive] documentation.
in that wiki page, this is also important:
If your issue is a question then please ask the question on [Wayback/Archive] Stack Overflow using the tag
vscode.
To open the terminal:
- Use the Ctrl+` keyboard shortcut with the backtick character.
- Use the View > Terminal menu command.
- From the Command Palette (Ctrl+Shift+P), use the View: Toggle Integrated Terminal command.
All of the above links started when I looked for [Wayback/Archive] vscode terminal wikipedia – Google Search.
–jeroen
Posted in Console (command prompt window), Development, Power User, Software Development, vscode Visual Studio Code, Windows, Windows Terminal | Leave a Comment »
Posted by jpluimers on 2022/11/09
Having missed quite a lot of Visual Studio Code releases during my metastasised rectum cancer treatment and recovery, it had become both very mature, but also very reliant of having the right extensions installed.
In that period, the extension marketplace grew remarkably, so I really wanted an easy way to install them from within the inside vscode integrated Windows Terminal.
A while ago I wrote How can you export the Visual Studio Code extension list? (via: Stack Overflow), which generated a small script with code --install-extension <extension-name> lines so I could executed those from the command-line for Visual Studio installations on new machines.
Boy was I surprised that you can just as well execute them from the [Wayback/Archive] Integrated Terminal in Visual Studio Code as well (:
When doing so, the Visual Studio Code instance around that Integrated Terminal will automatically pick up the new extension.
I found that with a [Wayback/Archive] vscode install extension from within visual studio code console – Google Search and bumping in the video also embedded below the signature: [Archive] VS Code tips — Installing extensions from the command line using –install-extension – YouTube.
The video also showed that the installation syntax can also include the version number like this:
Posted in Console (command prompt window), Development, Power User, Software Development, vscode Visual Studio Code, Windows, Windows 10, Windows Terminal | Leave a Comment »
Posted by jpluimers on 2022/10/25
With the rise of *nix tools and infrastructure on Windows (including, but certainly not limited to Visual Studio Code and Windows Subsystem for Linux), I need to get acquainted to the new ways these interface to the Windows Console.
Since Windows Console is from the (now obsolete) UCS-2 days, so it is not even fully Unicode aware, and has trouble with UTF-8, UTF-16.
So here are some links for my reading list:
conhost.exe and condrv.sys, and the core everything is a file/object difference in the unix and Windows world)
- Keep the default value of ‘termwintype’ as “”.
- If ‘termwintype’ is “” and if ConPTY is considered stable (Win10 1903? or later), use ConPTY.
- If ‘termwintype’ is “” and if ConPTY is considered unstable (1809), use winpty.
- If ‘termwintype’ is “” and if ConPTY is not available (before 1809), use winpty.
- If ‘termwintype’ is “conpty”, use ConPTY even if it is unstable (1809).
- If ‘termwintype’ is “winpty”, use winpty.
conhost.exe)–jeroen
Posted in *nix, *nix-tools, CommandLine, ConPTY, Console (command prompt window), Development, Linux, Power User, Software Development, Windows, Windows 10, Windows 11, Windows Development, Windows Terminal, WSL Windows Subsystem for Linux | Leave a Comment »
The Wiert Corner - irregular stream of stuff 