 | Mike Verhagen on geerlingguy/my-backup-plan: Ho… |
 | Attila Kovacs on docs.embarcadero.com unreachab… |
 | David Blue on MacOS: converting a man page t… |
 | jpluimers on How do I pretty-print JSON in… |
| jpluimers on Delphi 10.2 Tokyo Godzilla ISO… |
Posted by jpluimers on 2023/03/28
While writing On my reading list: Windows Console and PTY, I found out that OpenSSH had become available as an optional Windows feature.
It was in [Wayback/Archive.is] Windows Command-Line: Introducing the Windows Pseudo Console (ConPTY) | Windows Command Line:
Thankfully, OpenSSH was recently ported to Windows and added as a Windows 10 optional feature. PowerShell Core has also adopted ssh as one of its supported PowerShell Core Remoting protocols.
Here are a few links:
Posted in *nix, *nix-tools, Communications Development, ConPTY, Console (command prompt window), Development, Internet protocol suite, OpenSSH, Power User, SSH, ssh/sshd, TCP, Windows, Windows 10, Windows 11 | 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 »
Posted by jpluimers on 2022/06/16
Adapted from [Archive.is] How can you export the Visual Studio Code extension list? – Stack Overflow, presuming that code is on the PATH:
git installed:code --list-extensions | xargs -L 1 echo code --install-extension
git installed:code --list-extensions | % { "code --install-extension $_" }
or, as I think, more clearly (see also [WayBack] syntax – What does “%” (percent) do in PowerShell? – Stack Overflow):
code --list-extensions | foreach { "code --install-extension $_" }
or even more explanatory:
code --list-extensions | ForEach-Object { "code --install-extension $_" }
cmd.exe command:@for /f %l in ('code --list-extensions') do @echo code --install-extension %l
cmd.exe batch file (in a .bat/.cmd script):@for /f %%l in ('code --list-extensions') do @echo code --install-extension %%l
PowerShell -Command "code --list-extensions | % { """""code --install-extension $_""""" }"
Note that here too, the % can be expanded into foreach or ForEach-Object for clarity.
All of the above prepend “code --install-extension ” (note the trailing space) before each installed Visual Studio Code extension.
They all give you a list like this which you can execute on any machine having Visual Studio Code installed and its code on the PATH, and a working internet connection:
code --install-extension DavidAnson.vscode-markdownlint code --install-extension ms-vscode.powershell code --install-extension yzhang.markdown-all-in-onex
(This is about the minimum install for me to edit markdown documents and do useful things with PowerShell).
Of course you can pipe these to a text-file script to execute them later on.
The double-quote escaping is based on [Wayback/Archive.is] How to escape PowerShell double quotes from a .bat file – Stack Overflow:
you need to escape the
"on the command line, inside a double quoted string. From my testing, the only thing that seems to work is quadruple double quotes""""inside the quoted parameter:powershell.exe -command "echo '""""X""""'"
Via: [Archive.is] how to save your visual studio code extension list – Google Search
–jeroen
Posted in *nix, *nix-tools, .NET, bash, Batch-Files, CommandLine, Console (command prompt window), Development, Mac OS X / OS X / MacOS, Power User, PowerShell, PowerShell, Software Development, Visual Studio and tools, vscode Visual Studio Code, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Development, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, WSL Windows Subsystem for Linux, xargs | Leave a Comment »
The Wiert Corner - irregular stream of stuff 