Ancestors

Written by Jamie Teh on 2024-11-20 at 12:15

Continuing on my journey to switch to Windows Terminal, I want my various terminals to have separate pinned icons on the taskbar so I can get to each one quickly with Windows+number. Nothing I do seems to allow me to do this. There are command line arguments to focus a specific tab in a specific window, but that doesn't help with the initial launch where you need to specify a command line. This all worked just fine with conhost and various shortcuts. 😩

=> More informations about this toot | More toots from jcsteh@aus.social

Toot

Written by Jamie Teh on 2024-11-20 at 12:48

I found a very ugly, not at all intuitive way to do it:

  1. Create a shortcut which starts the terminal with the desired command line, specifying a unique window name with the -w option; e.g.:

wt -w wsl wsl.exe ~

  1. Create another shortcut which focuses the first tab in the same window name; e.g.:

wt -w wsl ft -t 0

  1. Pin the second shortcut to the taskbar, but not the first. You can then delete the second shortcut from wherever you created it if you like.

  1. When you want to launch it, you'll have to use the first shortcut. However, once launched, you can use the pinned taskbar shortcut to switch to it.

=> More informations about this toot | More toots from jcsteh@aus.social

Descendants

Written by Philip Kiff on 2024-11-20 at 13:54

@jcsteh It took me a while just to figure out how to create a simple shortcut to open a specific Windows Terminal - mainly so that I could open a WSL Terminal at a specific folder without navigating to it.

I tested pinning one of those just now, but as you note, my shortcut doesn't manage new vs multiple tab instances.

Windows Terminal keeps improving and sometimes surprises me as I continue to learn more neat things about it, but it definitely still has some awkward quirks!

=> More informations about this toot | More toots from pkiff@mastodon.social

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113515359970530863
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
306.803985 milliseconds
Gemini-to-HTML Time
0.980182 milliseconds

This content has been proxied by September (3851b).