From ef547b7be18871a345c1d7e44ecad664cd277d71 Mon Sep 17 00:00:00 2001 From: Valerie Wolfe Date: Mon, 19 Aug 2024 15:09:46 -0400 Subject: [PATCH] man: updated mkwin and wt manuals --- README.md | 4 ++-- man/mkwin.1 | 6 +++--- man/wt.1 | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 8f02df5..7591715 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@ # Winure: WSL inurement tools -These are tools I use to use Windows primarily through WSL. A lot of them -assume you have PowerShell somewhere in your `PATH` as "`pwsh`". +These are tools I use to use Windows primarily through WSL. Many are +cross-dependent. ## `dos-var` diff --git a/man/mkwin.1 b/man/mkwin.1 index e32fc1e..24624a0 100644 --- a/man/mkwin.1 +++ b/man/mkwin.1 @@ -56,11 +56,11 @@ Windows Explorer does not accept paths with spaces when executed from WSL. To ge .Pp Windows Terminal's executable moves when updated. To generate a script to launch Windows Terminal: .Pp -.Dl $ mkwin --empty --find='/mnt/c/Program Files/WindowsApps/Microsoft.WindowsTerminal*' WindowsTerminal.exe > terminal.sh +.Dl $ mkwin --empty --find='/mnt/c/Program Files/WindowsApps/Microsoft.WindowsTerminal*' WindowsTerminal.exe > wt.sh .Pp -PowerShell doesn't inherit environment variables from WSL. To generate a script to call PowerShell with shared variables: +PowerShell has two versions (Core is user-installed) and doesn't inherit environment variables from WSL. To generate a script to call PowerShell Core with a fallback to Windows PowerShell and shared environment variables: .Pp -.Dl $ mkwin -E '/mnt/c/Program Files/PowerShell/7/pwsh.exe' +.Dl $ mkwin -E '/mnt/c/Program Files/PowerShell/7/pwsh.exe' --or '/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe' .Pp .Sh SEE ALSO .Xr env-share 1 , diff --git a/man/wt.1 b/man/wt.1 index 048f812..1c3cca1 100644 --- a/man/wt.1 +++ b/man/wt.1 @@ -3,7 +3,7 @@ .Os MICROSOFT WINDOWS .Sh NAME .Nm wt -launch Windows Terminal from WSL. +.Nd Windows Terminal .Sh SYNOPSIS .Nm .Op Fl hv