WEBVTT

1
00:00:00.080 --> 00:00:03.439
<v Speaker 1>Okay, let's unpack this. Have you ever felt like your

2
00:00:03.480 --> 00:00:07.559
<v Speaker 1>command line experience on Windows was well, a little behind

3
00:00:07.559 --> 00:00:10.599
<v Speaker 1>the times, definitely like you were jumping through hoops just

4
00:00:10.720 --> 00:00:13.519
<v Speaker 1>to copy text or you know, manage multiple tasks.

5
00:00:13.599 --> 00:00:15.679
<v Speaker 2>Uh huh, the old ways were limiting.

6
00:00:16.199 --> 00:00:19.559
<v Speaker 1>Today we're delving deep into something that changes all of that,

7
00:00:20.280 --> 00:00:24.480
<v Speaker 1>the new Windows Terminal. Our mission for you, our listener,

8
00:00:24.760 --> 00:00:28.600
<v Speaker 1>is to unlock a supercharged command line experience, making you

9
00:00:28.719 --> 00:00:30.000
<v Speaker 1>a true power user.

10
00:00:30.239 --> 00:00:30.440
<v Speaker 2>Yeah.

11
00:00:30.879 --> 00:00:34.960
<v Speaker 1>We're drawing our insights from Wilfuqua's excellent book Windows Terminal Tips,

12
00:00:35.000 --> 00:00:38.920
<v Speaker 1>Tricks and Productivity Hacks, and we've distilled some powerful insights

13
00:00:38.960 --> 00:00:41.960
<v Speaker 1>that we think will genuinely transform your command line workflow.

14
00:00:42.079 --> 00:00:45.840
<v Speaker 2>What's truly fascinating here is how Microsoft has completely rethought

15
00:00:45.840 --> 00:00:47.439
<v Speaker 2>this integral tool from the ground up.

16
00:00:47.560 --> 00:00:48.880
<v Speaker 1>Right, it feels totally different.

17
00:00:49.079 --> 00:00:51.280
<v Speaker 2>For years, the Windows command line experience felt like it

18
00:00:51.359 --> 00:00:54.920
<v Speaker 2>lagged behind what was available on say Unix based system.

19
00:00:55.000 --> 00:00:58.359
<v Speaker 1>Yeah, malcos Linux they always seem to head exactly.

20
00:00:58.759 --> 00:01:01.759
<v Speaker 2>This exploration will not only reveal the incredible advancements, but

21
00:01:01.799 --> 00:01:04.959
<v Speaker 2>also show you how to tailor them precisely to your workflow.

22
00:01:05.200 --> 00:01:09.040
<v Speaker 2>It's about more than just a new window it's about efficiency, clarity,

23
00:01:09.439 --> 00:01:11.599
<v Speaker 2>and truly making your command line work for you.

24
00:01:12.239 --> 00:01:15.040
<v Speaker 1>So let's start at the beginning. Then, before Windows Terminal,

25
00:01:15.040 --> 00:01:17.439
<v Speaker 1>we had con host dot exe. Why did we even

26
00:01:17.480 --> 00:01:20.560
<v Speaker 1>need a new terminal? What was so I guess limiting

27
00:01:20.879 --> 00:01:21.840
<v Speaker 1>about the old way?

28
00:01:22.120 --> 00:01:25.239
<v Speaker 2>Well, the core issue with con host dot ex was

29
00:01:25.280 --> 00:01:28.200
<v Speaker 2>its primary mission backward compatibility.

30
00:01:28.319 --> 00:01:28.920
<v Speaker 1>Oh okay.

31
00:01:29.079 --> 00:01:32.000
<v Speaker 2>It was designed to run basically every old command line

32
00:01:32.000 --> 00:01:33.439
<v Speaker 2>application Windows had ever.

33
00:01:33.319 --> 00:01:35.599
<v Speaker 1>Seen, which sounds good in theory, right.

34
00:01:35.640 --> 00:01:40.120
<v Speaker 2>But it became a massive roadblock for innovation. Simple everyday

35
00:01:40.200 --> 00:01:44.000
<v Speaker 2>tasks that users expected, like easily selecting and copying text

36
00:01:44.200 --> 00:01:45.560
<v Speaker 2>were surprisingly difficult.

37
00:01:45.760 --> 00:01:48.640
<v Speaker 1>Oh I remember that pain multiple clicks exactly.

38
00:01:48.680 --> 00:01:51.599
<v Speaker 2>It felt clunky, and that commitment to never breaking older

39
00:01:51.599 --> 00:01:53.959
<v Speaker 2>apps meant the user experience was kind of stuck in

40
00:01:54.000 --> 00:01:57.599
<v Speaker 2>the past compared to modern terminals on mac os or Linux.

41
00:01:57.840 --> 00:02:00.640
<v Speaker 2>And this is where a key distinction clarifies everything. Understanding

42
00:02:00.640 --> 00:02:02.359
<v Speaker 2>the difference between a terminal and a shell.

43
00:02:02.439 --> 00:02:03.599
<v Speaker 1>Okay, yeah, break that down.

44
00:02:03.920 --> 00:02:06.640
<v Speaker 2>A terminal like Windows terminal is what you see. It's

45
00:02:06.680 --> 00:02:10.319
<v Speaker 2>the display engine responsible for rendering text, drawing the interface,

46
00:02:10.639 --> 00:02:12.039
<v Speaker 2>accepting your keyboard.

47
00:02:11.759 --> 00:02:15.240
<v Speaker 1>And mouse input, got it the window itself pretty much.

48
00:02:15.280 --> 00:02:18.000
<v Speaker 2>It then passes that input to the shell. The shell,

49
00:02:18.039 --> 00:02:21.039
<v Speaker 2>on the other hand, is the actual command line program

50
00:02:21.199 --> 00:02:26.800
<v Speaker 2>like PowerShell, CMD or Bash that interprets and executes your commands.

51
00:02:26.840 --> 00:02:29.039
<v Speaker 1>So PowerShell isn't the terminal, correct.

52
00:02:29.280 --> 00:02:32.439
<v Speaker 2>Windows Terminal is a brand new, modern terminal that hosts

53
00:02:32.479 --> 00:02:35.599
<v Speaker 2>all your existing shells. So all your PowerShell knowledge, your

54
00:02:35.599 --> 00:02:39.400
<v Speaker 2>get knowledge still completely valid and now honestly much more

55
00:02:39.439 --> 00:02:40.919
<v Speaker 2>powerful within this new host.

56
00:02:41.639 --> 00:02:45.400
<v Speaker 1>That distinction makes perfect sense. So con host was trapped

57
00:02:45.400 --> 00:02:49.960
<v Speaker 1>by its past, sacrificing user experience for backward compatibility. But

58
00:02:50.080 --> 00:02:53.280
<v Speaker 1>when Microsoft finally decided to build a new what was

59
00:02:53.319 --> 00:02:56.479
<v Speaker 1>the absolute first thing they prioritize in terms of user experience?

60
00:02:56.520 --> 00:02:58.800
<v Speaker 1>What makes this new Windows terminal so much better? Right

61
00:02:58.840 --> 00:02:59.439
<v Speaker 1>out of the box.

62
00:02:59.560 --> 00:03:03.840
<v Speaker 2>They really prioritized a modern, fast, and flexible foundation. It's

63
00:03:03.879 --> 00:03:08.240
<v Speaker 2>built on modern Windows technologies, things like UWP, EXML islands.

64
00:03:08.240 --> 00:03:09.439
<v Speaker 1>Okay, techy stuff.

65
00:03:09.199 --> 00:03:11.159
<v Speaker 2>Yeah, but what it means for you is it leverages

66
00:03:11.199 --> 00:03:14.639
<v Speaker 2>your system's full power, including GPU acceleration.

67
00:03:14.360 --> 00:03:16.039
<v Speaker 1>AH, using the graphics card.

68
00:03:15.919 --> 00:03:19.240
<v Speaker 2>Exactly for rendering text and effects. It results in a

69
00:03:19.319 --> 00:03:23.919
<v Speaker 2>remarkably smooth, fast, and visually rich experience that was simply

70
00:03:23.960 --> 00:03:27.759
<v Speaker 2>impossible with the old command prompts. But the immediate aha

71
00:03:28.039 --> 00:03:31.479
<v Speaker 2>moment for many users I think comes from its organizational power.

72
00:03:31.840 --> 00:03:35.479
<v Speaker 2>How so it brings built in tab support. Finally, Yes,

73
00:03:35.599 --> 00:03:40.039
<v Speaker 2>you can finally manage multiple shells PowerShell, WSL, CMDSS, eighth

74
00:03:40.039 --> 00:03:42.919
<v Speaker 2>sessions all within a single window. No more dozens of

75
00:03:42.919 --> 00:03:44.599
<v Speaker 2>separate windows clutter in your taskbar.

76
00:03:44.719 --> 00:03:47.039
<v Speaker 1>Oh that alone is worth the price of admission, which is.

77
00:03:47.039 --> 00:03:51.280
<v Speaker 2>Freehu Exactly, a quick trol plus shift plus T opens

78
00:03:51.319 --> 00:03:54.719
<v Speaker 2>a new tab, trol plus shift plus W closes one simple.

79
00:03:54.840 --> 00:03:58.159
<v Speaker 1>The tab support is a huge game changer for reducing clutter.

80
00:03:58.280 --> 00:04:00.120
<v Speaker 1>I can't tell you how many times I've hunted for

81
00:04:00.120 --> 00:04:04.199
<v Speaker 1>a specific command window. But you mentioned something even more powerful, pains.

82
00:04:04.560 --> 00:04:07.319
<v Speaker 2>Exactly beyond tabs, you also get terminal pains.

83
00:04:07.439 --> 00:04:08.520
<v Speaker 1>Okay, what does that mean?

84
00:04:08.759 --> 00:04:13.120
<v Speaker 2>Imagine a single tab becoming your entile development cockpit. You

85
00:04:13.120 --> 00:04:15.479
<v Speaker 2>could be running a live build process in one pain,

86
00:04:15.840 --> 00:04:18.920
<v Speaker 2>debugging in another, and maybe interacting with get in a third,

87
00:04:19.240 --> 00:04:22.800
<v Speaker 2>all visible at once, all simultaneously visible and interactive. It's

88
00:04:22.839 --> 00:04:26.839
<v Speaker 2>about eliminating that constant context switching, you know, freeing up

89
00:04:26.879 --> 00:04:29.800
<v Speaker 2>mental band with creating a truly focused workspace. How do

90
00:04:29.839 --> 00:04:32.519
<v Speaker 2>you make those pains Duplicating your current shell into a

91
00:04:32.560 --> 00:04:35.720
<v Speaker 2>new pain is as simple as alt plus shift plus D.

92
00:04:36.439 --> 00:04:39.079
<v Speaker 2>And you could split horizontally or vertically too.

93
00:04:39.240 --> 00:04:39.720
<v Speaker 1>Oh nice.

94
00:04:39.800 --> 00:04:42.959
<v Speaker 2>Yeah, the shortcuts are alt plus shift plus minus for horizontal,

95
00:04:43.279 --> 00:04:45.639
<v Speaker 2>alt plus shift plus equals for vertical. We can put

96
00:04:45.680 --> 00:04:47.079
<v Speaker 2>those exact commands in the show notes.

97
00:04:47.160 --> 00:04:50.839
<v Speaker 1>Good idea, Okay, tabs pains what else? Visually?

98
00:04:51.319 --> 00:04:54.879
<v Speaker 2>Visually, there's also a significant upgrade. It introduced Cascadia code

99
00:04:54.959 --> 00:04:58.279
<v Speaker 2>the font YEP, a programming font designed specifically for this.

100
00:04:58.519 --> 00:05:02.600
<v Speaker 2>It supports optional programming, so characters like render as a

101
00:05:02.639 --> 00:05:04.759
<v Speaker 2>cleaner single E glyph.

102
00:05:05.000 --> 00:05:07.439
<v Speaker 1>Oh that's pretty neat makes code look cleaner.

103
00:05:07.439 --> 00:05:11.079
<v Speaker 2>It does. And it supports power line glyphs, which are

104
00:05:11.160 --> 00:05:14.800
<v Speaker 2>special characters that enhance the visual style of custom command

105
00:05:14.879 --> 00:05:15.839
<v Speaker 2>line comps.

106
00:05:16.000 --> 00:05:18.519
<v Speaker 1>Like those fancy status bars I see people have.

107
00:05:18.680 --> 00:05:21.639
<v Speaker 2>Exactly turning a drab text line into an informative and

108
00:05:22.040 --> 00:05:25.839
<v Speaker 2>frankly esthetically pleasing status bar with things like get status

109
00:05:26.319 --> 00:05:27.879
<v Speaker 2>current directory stuff like that.

110
00:05:28.240 --> 00:05:34.759
<v Speaker 1>Okay, I'm sold on the features, But what about control customization? Ah?

111
00:05:34.800 --> 00:05:38.120
<v Speaker 2>For those who love control, The customization is incredibly flexible,

112
00:05:38.560 --> 00:05:40.399
<v Speaker 2>uses the settings dot json file.

113
00:05:40.600 --> 00:05:41.879
<v Speaker 1>Jason, Okay, yeah.

114
00:05:41.720 --> 00:05:44.519
<v Speaker 2>With a documented structure This isn't just some random text file.

115
00:05:44.759 --> 00:05:47.600
<v Speaker 2>It means editors like visual Studio Code give you first

116
00:05:47.639 --> 00:05:50.959
<v Speaker 2>class editing with autocomplete and documentation built right in.

117
00:05:51.160 --> 00:05:54.000
<v Speaker 1>That makes editing way easier than guessing totally.

118
00:05:54.279 --> 00:05:56.720
<v Speaker 2>And the key insight here is that your configurations are

119
00:05:56.720 --> 00:06:00.399
<v Speaker 2>easily version controlled. Put it in get and share across

120
00:06:00.399 --> 00:06:04.519
<v Speaker 2>different machines, so you get a truly consistent personal environment everywhere.

121
00:06:04.560 --> 00:06:06.680
<v Speaker 1>And it's open source, right and critically, yes.

122
00:06:06.560 --> 00:06:08.879
<v Speaker 2>It's completely open source. You can see all the development

123
00:06:08.879 --> 00:06:11.519
<v Speaker 2>happening on Microsoft's GitHub repository.

124
00:06:10.959 --> 00:06:13.240
<v Speaker 1>So you can see where it's going, maybe even contribute.

125
00:06:13.319 --> 00:06:18.560
<v Speaker 2>Absolutely, the team is incredibly active encouraging community contributions and

126
00:06:18.720 --> 00:06:23.199
<v Speaker 2>maintaining transparent development, which fuels rapid innovation. It's a really

127
00:06:23.399 --> 00:06:24.680
<v Speaker 2>vibrant project.

128
00:06:24.399 --> 00:06:28.240
<v Speaker 1>That transparency and community involvement are huge. So with all

129
00:06:28.279 --> 00:06:31.959
<v Speaker 1>these fantastic capabilities, how do you actually get this powerhouse

130
00:06:32.079 --> 00:06:33.360
<v Speaker 1>up and running efficiently?

131
00:06:33.560 --> 00:06:37.279
<v Speaker 2>The easiest and most recommended way directly from the Microsoft Store.

132
00:06:37.399 --> 00:06:40.800
<v Speaker 2>Just search for it, YEP, search Windows terminal click get.

133
00:06:41.120 --> 00:06:44.439
<v Speaker 2>That's it. This also ensures that stays automatically.

134
00:06:43.959 --> 00:06:45.839
<v Speaker 1>Updated, which is nice, okay, easy enough.

135
00:06:45.920 --> 00:06:48.079
<v Speaker 2>Once installed, you launch it like any other app. From

136
00:06:48.120 --> 00:06:50.920
<v Speaker 2>the start menu, but for more efficiency, it ships with

137
00:06:50.959 --> 00:06:53.120
<v Speaker 2>the command WT dot.

138
00:06:52.959 --> 00:06:55.079
<v Speaker 1>Ex ah WT.

139
00:06:55.360 --> 00:06:57.800
<v Speaker 2>Right, you can simply type wt in the run dialogue

140
00:06:57.920 --> 00:07:00.959
<v Speaker 2>or even the Windows Explorer address bar, hit enter and

141
00:07:00.959 --> 00:07:01.879
<v Speaker 2>boom it launches.

142
00:07:02.000 --> 00:07:02.360
<v Speaker 1>Andy.

143
00:07:02.480 --> 00:07:05.439
<v Speaker 2>You can even add command line flags like wtdshf to

144
00:07:05.480 --> 00:07:07.079
<v Speaker 2>launch directly into full screen mode.

145
00:07:07.160 --> 00:07:08.680
<v Speaker 1>Okay, full screen Terminal, I like it.

146
00:07:08.759 --> 00:07:10.079
<v Speaker 2>Yeah, lots of little tricks like that.

147
00:07:10.319 --> 00:07:13.839
<v Speaker 1>Here's where it gets really interesting for customizing your digital workspace.

148
00:07:13.879 --> 00:07:16.759
<v Speaker 1>I think, with all these powerful features, how do we

149
00:07:16.800 --> 00:07:20.040
<v Speaker 1>make Windows Terminal truly ours? It all starts with that

150
00:07:20.160 --> 00:07:21.399
<v Speaker 1>settings dot json file.

151
00:07:21.480 --> 00:07:25.959
<v Speaker 2>Right, Absolutely, that settings adjacent file is truly the cornerstone

152
00:07:26.000 --> 00:07:27.040
<v Speaker 2>of configurability.

153
00:07:27.079 --> 00:07:28.240
<v Speaker 1>Cornerstone Okay.

154
00:07:28.439 --> 00:07:31.519
<v Speaker 2>As we discussed, it offers incredible power for deep customization,

155
00:07:32.079 --> 00:07:34.480
<v Speaker 2>makes it easy to version control your settings with git

156
00:07:34.759 --> 00:07:36.920
<v Speaker 2>or something, and allows for seamless sharing.

157
00:07:37.000 --> 00:07:38.040
<v Speaker 1>How do you open it quickly?

158
00:07:38.160 --> 00:07:40.680
<v Speaker 2>You can quickly open it by pressing tree, troll plus

159
00:07:40.680 --> 00:07:45.600
<v Speaker 2>shift plus aid directly from within Windows Terminal.

160
00:07:45.279 --> 00:07:48.120
<v Speaker 1>Creed, roll plus shift plus comma, got it?

161
00:07:48.279 --> 00:07:51.040
<v Speaker 2>And Yeah. Using Visual Studio code for editing provides a

162
00:07:51.079 --> 00:07:55.319
<v Speaker 2>superior experience, whether it's built in autocomplete and documentation really

163
00:07:55.360 --> 00:07:58.480
<v Speaker 2>helps avoid typos. The file itself is logically structured, which

164
00:07:58.519 --> 00:08:00.879
<v Speaker 2>is helpful. You'll find global settings that apply to the

165
00:08:01.040 --> 00:08:06.199
<v Speaker 2>entire terminal overall behavior exactly. Then profile settings for individual shells,

166
00:08:06.480 --> 00:08:09.800
<v Speaker 2>so PowerShell can look different from your Wslobuntu shell for.

167
00:08:09.720 --> 00:08:13.000
<v Speaker 1>Instance, ah Per shell settings nice YEP.

168
00:08:13.319 --> 00:08:16.480
<v Speaker 2>Also color scheme settings for its appearance, and keyboard shortcut

169
00:08:16.560 --> 00:08:18.319
<v Speaker 2>settings for all your custom hot keys.

170
00:08:18.480 --> 00:08:21.839
<v Speaker 1>So for someone just diving into settings dot json, what

171
00:08:21.959 --> 00:08:25.319
<v Speaker 1>are some global settings that can immediately enhance their workflow?

172
00:08:26.240 --> 00:08:27.360
<v Speaker 1>Any quick wins?

173
00:08:27.399 --> 00:08:29.959
<v Speaker 2>Definitely a few make a big difference right away.

174
00:08:30.399 --> 00:08:33.320
<v Speaker 1>Copy on select, copy on select What's that?

175
00:08:33.480 --> 00:08:36.320
<v Speaker 2>When set to true, it automatically copies any text you

176
00:08:36.399 --> 00:08:39.399
<v Speaker 2>highlight with your mouse straight to the clipboard, no need

177
00:08:39.440 --> 00:08:42.279
<v Speaker 2>to write, click or press quockol plus.

178
00:08:42.080 --> 00:08:45.279
<v Speaker 1>C oh copy on select. Yes, I can't tell you

179
00:08:45.279 --> 00:08:47.679
<v Speaker 1>how many times I've fumbled with compleplus c in the

180
00:08:47.679 --> 00:08:50.360
<v Speaker 1>old con host only to find I'd selected the wrong

181
00:08:50.399 --> 00:08:52.600
<v Speaker 1>thing or missed it. It's a small thing, but yeah,

182
00:08:52.679 --> 00:08:56.519
<v Speaker 1>it's a huge quality of life upgrade. Seriously, it absolutely is.

183
00:08:56.919 --> 00:08:59.399
<v Speaker 2>Then there's start on user login din'd it start up YEP,

184
00:08:59.440 --> 00:09:02.039
<v Speaker 2>which can lunch the terminal automatically when you log into

185
00:09:02.039 --> 00:09:03.840
<v Speaker 2>Windows great if it's your daily driver.

186
00:09:04.159 --> 00:09:04.679
<v Speaker 1>Makes sense.

187
00:09:04.720 --> 00:09:07.679
<v Speaker 2>Default profile lets you choose which shell opens by default

188
00:09:07.720 --> 00:09:10.240
<v Speaker 2>when you hit the new tab button, or just launch

189
00:09:10.279 --> 00:09:10.960
<v Speaker 2>the terminal so.

190
00:09:10.960 --> 00:09:14.320
<v Speaker 1>I can make it powersholl Core instead of old cmd exactly.

191
00:09:14.480 --> 00:09:16.799
<v Speaker 2>You can also set tab visibility to hide the tab

192
00:09:16.840 --> 00:09:19.399
<v Speaker 2>strip if you only have one tab open. Gives you

193
00:09:19.440 --> 00:09:20.759
<v Speaker 2>a bit more screen real estate.

194
00:09:20.879 --> 00:09:22.919
<v Speaker 1>Oh I like that minimal.

195
00:09:22.720 --> 00:09:26.559
<v Speaker 2>And theme of course to switch between light dark, or

196
00:09:27.480 --> 00:09:29.320
<v Speaker 2>just follow your systems theme automatically.

197
00:09:29.440 --> 00:09:32.799
<v Speaker 1>Okay, those are great practical tweaks. Beyond behavior, how can

198
00:09:32.840 --> 00:09:35.879
<v Speaker 1>we make it visually stunning and you know, truly reflective

199
00:09:35.879 --> 00:09:36.960
<v Speaker 1>of our personal style?

200
00:09:37.159 --> 00:09:40.440
<v Speaker 2>Yeah, esthetics matter. That's where color schemes come in. Windows

201
00:09:40.519 --> 00:09:44.159
<v Speaker 2>Terminal includes popular built in schemes like Solarized and Tango.

202
00:09:44.759 --> 00:09:45.840
<v Speaker 2>Pretty good starting.

203
00:09:45.519 --> 00:09:46.799
<v Speaker 1>Points, so you can add more.

204
00:09:47.039 --> 00:09:49.919
<v Speaker 2>Oh yeah, the community has created a wealth of options.

205
00:09:50.039 --> 00:09:53.440
<v Speaker 2>You can explore websites like Windows Terminal Themes dot dev.

206
00:09:53.559 --> 00:09:54.480
<v Speaker 2>Just copy paste the.

207
00:09:54.519 --> 00:09:56.720
<v Speaker 1>Jason ah easy to find new ones.

208
00:09:56.919 --> 00:09:59.559
<v Speaker 2>Or for full control, you can define your own color

209
00:09:59.600 --> 00:10:02.559
<v Speaker 2>schemes right in the JSON, mapping standard A and SI

210
00:10:02.679 --> 00:10:07.559
<v Speaker 2>color names like bright black or cyan to specific rgb

211
00:10:07.879 --> 00:10:08.320
<v Speaker 2>X values.

212
00:10:08.360 --> 00:10:09.600
<v Speaker 1>Total control. Nice.

213
00:10:09.639 --> 00:10:12.200
<v Speaker 2>You can also personalize it deeply with background images. Put

214
00:10:12.200 --> 00:10:14.320
<v Speaker 2>your logo, your cat, whatever you want behind the.

215
00:10:14.279 --> 00:10:17.320
<v Speaker 1>Text background images in a terminal okay.

216
00:10:17.240 --> 00:10:20.879
<v Speaker 2>And adjust the translucency of the window using usacrylic and

217
00:10:20.879 --> 00:10:25.279
<v Speaker 2>acrylic capacity. Is it that slightly see through modern.

218
00:10:24.960 --> 00:10:27.399
<v Speaker 1>Look acrylic like the Windows fluent design thing?

219
00:10:27.559 --> 00:10:30.320
<v Speaker 2>Exactly? Yeah, and a neat visual trick here. Once a

220
00:10:30.360 --> 00:10:33.679
<v Speaker 2>crylic is enabled, you can temporarily adjust the translucency on

221
00:10:33.720 --> 00:10:37.360
<v Speaker 2>the fly. Hold crill it plus alt plus shift and

222
00:10:37.399 --> 00:10:38.480
<v Speaker 2>scroll your mouse wheel.

223
00:10:38.600 --> 00:10:41.639
<v Speaker 1>Oh, temporary adjustment, that's cool, Yeah.

224
00:10:41.320 --> 00:10:43.960
<v Speaker 2>Just for that session. For more experimental visual effect, you

225
00:10:44.000 --> 00:10:46.600
<v Speaker 2>can even play around with pixel shaders, but that's getting

226
00:10:46.639 --> 00:10:47.360
<v Speaker 2>pretty advanced.

227
00:10:47.399 --> 00:10:50.240
<v Speaker 1>Okay, maybe I'll stick with background images for now. And

228
00:10:50.440 --> 00:10:52.799
<v Speaker 1>for the keyboard wizards among us, the folks who live

229
00:10:52.840 --> 00:10:56.120
<v Speaker 1>by shortcuts, what kind of raw power can we unlock

230
00:10:56.159 --> 00:10:57.360
<v Speaker 1>with custom shortcuts?

231
00:10:57.559 --> 00:11:00.480
<v Speaker 2>Right the action section in Settings dot Jason. This used

232
00:11:00.480 --> 00:11:02.960
<v Speaker 2>to be called key bindings, now it's actions. This is

233
00:11:02.960 --> 00:11:04.720
<v Speaker 2>where you define custom keyboard.

234
00:11:04.360 --> 00:11:07.120
<v Speaker 1>Shortcuts, so mapping keys to actions.

235
00:11:07.159 --> 00:11:10.320
<v Speaker 2>Pretty much, each shortcut maps a command which can be

236
00:11:10.320 --> 00:11:12.879
<v Speaker 2>a simple string for built in actions or a more

237
00:11:13.000 --> 00:11:16.279
<v Speaker 2>complex object for actions with parameters, to a keys property

238
00:11:16.360 --> 00:11:19.399
<v Speaker 2>so critical plus shift plus something does this action well.

239
00:11:19.480 --> 00:11:20.639
<v Speaker 1>Kind of actions all.

240
00:11:20.440 --> 00:11:25.320
<v Speaker 2>Sorts, closing tabs, splitting pains, changing font size. But one

241
00:11:25.360 --> 00:11:27.000
<v Speaker 2>of the most powerful is send input.

242
00:11:27.279 --> 00:11:29.679
<v Speaker 1>Send input like typing for me exactly.

243
00:11:29.919 --> 00:11:33.480
<v Speaker 2>This allows you to send arbitrary keyboard input directly to

244
00:11:33.559 --> 00:11:36.279
<v Speaker 2>the active terminal shell, essentially automating typing.

245
00:11:36.440 --> 00:11:38.159
<v Speaker 1>Give me an example. How's that useful?

246
00:11:38.320 --> 00:11:41.840
<v Speaker 2>Okay, say you constantly navigate to your main project's directory.

247
00:11:42.320 --> 00:11:45.519
<v Speaker 2>You could bind maybe c trel plus al plus P

248
00:11:46.080 --> 00:11:49.600
<v Speaker 2>to instantly type CD projects followed by an enter key.

249
00:11:49.679 --> 00:11:53.120
<v Speaker 1>Whoa so one key combo jumps me to my fold well.

250
00:11:53.200 --> 00:11:57.639
<v Speaker 2>Warp speed directory navigation. It's about automating those repetitive finger movements.

251
00:11:58.159 --> 00:12:01.200
<v Speaker 2>You can even send ANSI escape sequences for things like

252
00:12:01.360 --> 00:12:01.960
<v Speaker 2>arrow keys.

253
00:12:02.200 --> 00:12:05.240
<v Speaker 1>Okay, send input sounds incredibly powerful for automation.

254
00:12:05.399 --> 00:12:07.879
<v Speaker 2>What else, There's the WT eight action. This is fantastic

255
00:12:07.919 --> 00:12:10.000
<v Speaker 2>for launching pre configured tab and pain.

256
00:12:09.879 --> 00:12:11.919
<v Speaker 1>Layouts, wait launching layouts of the shortcut.

257
00:12:12.000 --> 00:12:15.120
<v Speaker 2>Yeah. Imagine launching an entire project workspace, maybe your code

258
00:12:15.200 --> 00:12:17.960
<v Speaker 2>editor like vim in one pain, a live build process

259
00:12:18.039 --> 00:12:20.600
<v Speaker 2>like dot netwatch run, and another, all with a single

260
00:12:20.639 --> 00:12:23.360
<v Speaker 2>custom command you've defined in your setting start Jason.

261
00:12:23.080 --> 00:12:26.639
<v Speaker 1>That's huge. One shortcut sets up my whole dev environment

262
00:12:26.639 --> 00:12:28.000
<v Speaker 1>in terminal exactly.

263
00:12:28.039 --> 00:12:31.320
<v Speaker 2>And this wtgidxc blindary we mentioned earlier. You can use

264
00:12:31.360 --> 00:12:34.200
<v Speaker 2>it from outside the terminal too, crease start menu shortcuts

265
00:12:34.279 --> 00:12:38.840
<v Speaker 2>or batch files that launch these highly customized complex layouts instantly.

266
00:12:39.000 --> 00:12:40.879
<v Speaker 2>We can put some example syntax in the show notes

267
00:12:40.879 --> 00:12:42.360
<v Speaker 2>because it gets a bit involved.

268
00:12:42.399 --> 00:12:45.399
<v Speaker 1>Please do that sounds amazing. So okay, we've seen how

269
00:12:45.399 --> 00:12:48.000
<v Speaker 1>to make Windows Terminal look and behave exactly how we want.

270
00:12:48.080 --> 00:12:50.799
<v Speaker 1>It's truly ours, right But for many of us, the

271
00:12:50.919 --> 00:12:53.399
<v Speaker 1>command line isn't just a Windows thing anymore. We live

272
00:12:53.440 --> 00:12:57.519
<v Speaker 1>in a multious world, rightly, What about those Linux command

273
00:12:57.600 --> 00:13:00.519
<v Speaker 1>line tools we love right here on Windows. Many people

274
00:13:00.519 --> 00:13:03.440
<v Speaker 1>have heard of WSL two, the Windows subsystem for Linux. Uh,

275
00:13:03.600 --> 00:13:05.679
<v Speaker 1>But for those of us integrating it into our daily

276
00:13:05.720 --> 00:13:10.600
<v Speaker 1>Windows flow, what truly makes WSL two such a significant evolution?

277
00:13:10.799 --> 00:13:12.000
<v Speaker 1>Why is it such a big deal?

278
00:13:12.639 --> 00:13:16.480
<v Speaker 2>WSL two is a genuine game changer, largely because it

279
00:13:16.519 --> 00:13:20.600
<v Speaker 2>finally provides a fast, fully compatible Linux environment directly.

280
00:13:20.279 --> 00:13:22.679
<v Speaker 1>On Windows, faster than WSL one, much.

281
00:13:22.480 --> 00:13:25.919
<v Speaker 2>Faster for filesystem operations, yeah yeah, and more compatible. It

282
00:13:26.000 --> 00:13:29.480
<v Speaker 2>solves so many dependency headaches, especially for developers using popular

283
00:13:29.480 --> 00:13:31.320
<v Speaker 2>web frameworks or tools designed for Linux.

284
00:13:31.559 --> 00:13:34.440
<v Speaker 1>How does it work? Is it like a VM sort of?

285
00:13:34.919 --> 00:13:38.440
<v Speaker 2>Unlike its predecessor, WSL two runs a real Linux kernel

286
00:13:38.639 --> 00:13:41.159
<v Speaker 2>on a lightweight hyper V virtualization.

287
00:13:40.679 --> 00:13:42.799
<v Speaker 1>Layer a real kernel, which.

288
00:13:42.600 --> 00:13:46.279
<v Speaker 2>Results in vastly improved performance and compatibility. It truly feels

289
00:13:46.279 --> 00:13:50.519
<v Speaker 2>like Rhyando Lenox natively just inside Windows. And what's truly revolutionary,

290
00:13:50.559 --> 00:13:53.919
<v Speaker 2>I think, is the seamless bidirectional access between Windows and Linux.

291
00:13:54.000 --> 00:13:57.879
<v Speaker 2>Bidirectional meaning you can easily access your Linux distributions files

292
00:13:57.879 --> 00:14:00.879
<v Speaker 2>from Windows. Just navigate to a UNC path like inf

293
00:14:00.919 --> 00:14:04.519
<v Speaker 2>open two in File Explorer. Your Linux home directory is right.

294
00:14:04.399 --> 00:14:07.879
<v Speaker 1>There, oh, directly in file Explore. No special tools, nope.

295
00:14:08.200 --> 00:14:11.159
<v Speaker 2>And conversely, your Windows drives like your c drive are

296
00:14:11.200 --> 00:14:15.080
<v Speaker 2>automatically mounted directly under m NTC within your Linux environment,

297
00:14:15.799 --> 00:14:18.200
<v Speaker 2>so you can c D m n TC users your name,

298
00:14:18.639 --> 00:14:20.600
<v Speaker 2>and access Windows files from your Linux shell.

299
00:14:20.679 --> 00:14:23.360
<v Speaker 1>Okay, that's seamless, files are easy. What about running things

300
00:14:23.440 --> 00:14:24.000
<v Speaker 1>even better?

301
00:14:24.200 --> 00:14:26.879
<v Speaker 2>You can run Linux programs directly from Windows PowerShell or

302
00:14:26.879 --> 00:14:31.679
<v Speaker 2>CMD using WSL dot ex Linux command like wsls ls

303
00:14:31.799 --> 00:14:34.679
<v Speaker 2>L runs the Linux ls command. Okay, and maybe even

304
00:14:34.720 --> 00:14:37.480
<v Speaker 2>more surprisingly you can run Windows programs from your Linux shell.

305
00:14:37.679 --> 00:14:41.519
<v Speaker 1>Wait, run dot ex files from Bash or z sh yep.

306
00:14:41.559 --> 00:14:45.440
<v Speaker 2>Imagine you're in your WSL terminal. You type notepad dot

307
00:14:45.440 --> 00:14:49.879
<v Speaker 2>exc my linux canfig dot txt, It opens that Linux

308
00:14:49.879 --> 00:14:53.200
<v Speaker 2>file and Windows notepad no way. Or type explorer dot

309
00:14:53.240 --> 00:14:57.600
<v Speaker 2>ex that's explore dot xe space dot and it launches

310
00:14:57.639 --> 00:15:00.639
<v Speaker 2>Windows file Explorer right in your current Linux directory.

311
00:15:00.799 --> 00:15:04.919
<v Speaker 1>Mind blown. That level of integration is incredible. Okay, but

312
00:15:05.000 --> 00:15:07.919
<v Speaker 1>it's not just about running Linux. It's about making those shells,

313
00:15:07.919 --> 00:15:12.000
<v Speaker 1>both Linux and powershells sing with customization and power tools exactly.

314
00:15:12.120 --> 00:15:15.279
<v Speaker 2>Let's start with PowerShell. For PowerShell users. Oh my posh

315
00:15:15.399 --> 00:15:18.440
<v Speaker 2>is a fantastic tool. You've probably seen screenshots.

316
00:15:17.879 --> 00:15:19.360
<v Speaker 1>Those really cool looking prompts.

317
00:15:19.360 --> 00:15:22.679
<v Speaker 2>That's the one. It transforms basic prompts into informative, stylish ones.

318
00:15:22.799 --> 00:15:25.679
<v Speaker 2>It can show critical details like your current Git branch status,

319
00:15:25.840 --> 00:15:28.799
<v Speaker 2>shortened paths so they don't wrap air indicators if the

320
00:15:28.840 --> 00:15:31.600
<v Speaker 2>last command failed. All enhanced by using a font like

321
00:15:31.639 --> 00:15:34.679
<v Speaker 2>Cascade codepl that has the necessary gliss.

322
00:15:34.519 --> 00:15:36.159
<v Speaker 1>So it makes your prompt work harder for you.

323
00:15:36.240 --> 00:15:39.480
<v Speaker 2>Basically, precisely, and beyond external tools like that, you can

324
00:15:39.519 --> 00:15:42.559
<v Speaker 2>actually define your own custom prompt functions right in your

325
00:15:42.559 --> 00:15:43.879
<v Speaker 2>PowerShell profile.

326
00:15:43.519 --> 00:15:45.200
<v Speaker 1>Script writing your own prompt.

327
00:15:45.440 --> 00:15:49.639
<v Speaker 2>Yeah. This lets you inject things like ANSI, escape sequences

328
00:15:49.679 --> 00:15:53.159
<v Speaker 2>for custom colors, or maybe even add emojis directly into

329
00:15:53.159 --> 00:15:55.120
<v Speaker 2>your prout for a unique Flare.

330
00:15:55.080 --> 00:15:57.639
<v Speaker 1>Rocket ship emoji when in my project's folder.

331
00:15:57.879 --> 00:16:01.679
<v Speaker 2>Why not if that works for you. Psrid line is

332
00:16:01.720 --> 00:16:05.600
<v Speaker 2>another essential PowerShell module. It's usually included now, but it

333
00:16:05.639 --> 00:16:07.600
<v Speaker 2>greatly enhances command line editing.

334
00:16:07.759 --> 00:16:09.600
<v Speaker 1>How does it enhance it?

335
00:16:09.600 --> 00:16:12.799
<v Speaker 2>Its history search is incredibly powerful. Just type part of

336
00:16:12.799 --> 00:16:15.399
<v Speaker 2>a command you ran before, say G, then press the

337
00:16:15.480 --> 00:16:19.000
<v Speaker 2>up arrow and it intelligently filters your command history. Makes

338
00:16:19.039 --> 00:16:21.639
<v Speaker 2>finding that get status command from yesterday way faster.

339
00:16:21.919 --> 00:16:23.679
<v Speaker 1>That's better than just scrolling up endlessly.

340
00:16:23.840 --> 00:16:27.000
<v Speaker 2>Way better. Oh. It also offers command predictions, which appear

341
00:16:27.039 --> 00:16:29.639
<v Speaker 2>as feint tech suggestions in your prompt. Guessing what you

342
00:16:29.720 --> 00:16:31.799
<v Speaker 2>might type next base on your history. Just hit the

343
00:16:31.840 --> 00:16:34.399
<v Speaker 2>right arrow to accept really speeds up your input.

344
00:16:34.679 --> 00:16:36.480
<v Speaker 1>Predictive text for the command line.

345
00:16:36.600 --> 00:16:39.000
<v Speaker 2>Kind of yeah. And for those who love the classic

346
00:16:39.080 --> 00:16:42.480
<v Speaker 2>Unix tools, you can bring genu cordals like ales grabs,

347
00:16:42.519 --> 00:16:45.399
<v Speaker 2>food oc to PowerShell. They often get installed as part

348
00:16:45.399 --> 00:16:46.720
<v Speaker 2>of GIT for Windows.

349
00:16:46.360 --> 00:16:48.399
<v Speaker 1>So I can use l's in PowerShell.

350
00:16:48.320 --> 00:16:51.039
<v Speaker 2>You can't. There's also the z utility, which is amazing.

351
00:16:51.399 --> 00:16:54.919
<v Speaker 2>It provides warp speed directory navigation met It learns which

352
00:16:54.960 --> 00:16:58.159
<v Speaker 2>directories you a visit frequently or a freesency frequency plus recency.

353
00:16:58.720 --> 00:17:01.679
<v Speaker 2>Then you can just type Z and it might jump

354
00:17:01.679 --> 00:17:04.559
<v Speaker 2>you straight to see users, your documents, projects if that's

355
00:17:04.559 --> 00:17:07.359
<v Speaker 2>where you go. Often jump to common directories with just

356
00:17:07.400 --> 00:17:08.400
<v Speaker 2>a few key strokes.

357
00:17:08.480 --> 00:17:11.440
<v Speaker 1>Okay, z sounds essential. Now moving over to WSL two.

358
00:17:11.519 --> 00:17:13.599
<v Speaker 1>Maybe using zsh instead of Bash.

359
00:17:13.680 --> 00:17:18.400
<v Speaker 2>Yeah. Zsh is a fantastic, highly configurable alternative to Bash.

360
00:17:18.720 --> 00:17:22.279
<v Speaker 2>It's actually the default shell on macOS now and oh

361
00:17:22.319 --> 00:17:25.480
<v Speaker 2>my zish builds on this with a massive community ecosystem

362
00:17:25.880 --> 00:17:27.160
<v Speaker 2>of themes and plugins.

363
00:17:27.640 --> 00:17:29.799
<v Speaker 1>Z plus oh my zish is the combo.

364
00:17:29.920 --> 00:17:33.119
<v Speaker 2>It's a very popular and powerful combo. Yeah for rerunning commands,

365
00:17:33.119 --> 00:17:36.319
<v Speaker 2>and zsh HL plus r provides an interactive history search

366
00:17:36.640 --> 00:17:40.960
<v Speaker 2>that's incredibly efficient, similar to PS redlines. Zsh also offers

367
00:17:41.000 --> 00:17:44.640
<v Speaker 2>powerful history substitutions, which are brilliant shortcuts. Look what things

368
00:17:44.680 --> 00:17:46.559
<v Speaker 2>like zeer, which treat is the last argument of the

369
00:17:46.599 --> 00:17:49.359
<v Speaker 2>previous command repeats your entire previous command.

370
00:17:49.440 --> 00:17:51.839
<v Speaker 1>Ah, I've heard of that useful.

371
00:17:51.519 --> 00:17:54.559
<v Speaker 2>For incredibly useful. When you forget to type pseudo first

372
00:17:55.319 --> 00:17:57.640
<v Speaker 2>run a command, it fails with permission denied. You just

373
00:17:57.680 --> 00:17:59.880
<v Speaker 2>type pseudo and hit enter. Done.

374
00:18:00.079 --> 00:18:02.200
<v Speaker 1>Okay, Pseudo is going in my muscle memory.

375
00:18:02.279 --> 00:18:04.160
<v Speaker 2>It's a life saver. Yeah. You can also set up

376
00:18:04.200 --> 00:18:07.559
<v Speaker 2>custom aliases and functions in zsh, just like in PowerShell,

377
00:18:07.920 --> 00:18:09.559
<v Speaker 2>to automate repetitive.

378
00:18:09.039 --> 00:18:11.839
<v Speaker 1>Tasks like shortcuts for long commands.

379
00:18:11.440 --> 00:18:16.400
<v Speaker 2>Exactly or recreating powershells I alias invoke item to open

380
00:18:16.480 --> 00:18:20.319
<v Speaker 2>files with their default Windows application using PowerShell dot ex,

381
00:18:21.559 --> 00:18:25.000
<v Speaker 2>or to find a complex work function that maybe changes directory,

382
00:18:25.119 --> 00:18:27.920
<v Speaker 2>opens vs code and fetches GIT updates, all with a

383
00:18:27.960 --> 00:18:28.799
<v Speaker 2>single work command.

384
00:18:28.920 --> 00:18:30.720
<v Speaker 1>Automating workflows nice for.

385
00:18:30.720 --> 00:18:33.440
<v Speaker 2>Quick directory navigation, and z auto seeds is an option

386
00:18:33.480 --> 00:18:35.200
<v Speaker 2>where you can just type the directory name to CD

387
00:18:35.319 --> 00:18:38.519
<v Speaker 2>into it if it exists. Using hyphen instantly toggles you

388
00:18:38.559 --> 00:18:39.759
<v Speaker 2>between your last two directories.

389
00:18:39.839 --> 00:18:42.119
<v Speaker 1>Oh jump back and forth, handy.

390
00:18:42.119 --> 00:18:45.519
<v Speaker 2>Very and finally oh my. Switech plugins add even more power.

391
00:18:45.720 --> 00:18:48.680
<v Speaker 2>There's zz plug in, bringing that freqency based directory jumping

392
00:18:48.720 --> 00:18:49.440
<v Speaker 2>we talked about to.

393
00:18:49.440 --> 00:18:51.079
<v Speaker 1>Z okay z everywhere.

394
00:18:51.240 --> 00:18:54.839
<v Speaker 2>There's zush Auto Suggestions, which gives you those faint text

395
00:18:54.880 --> 00:18:59.440
<v Speaker 2>suggestions as you type, like PS redline and syntax highlighting

396
00:18:59.480 --> 00:19:03.079
<v Speaker 2>gives you vision feedback coloring commands green if they look valid,

397
00:19:03.400 --> 00:19:05.000
<v Speaker 2>red if not before you hit enter.

398
00:19:05.160 --> 00:19:07.559
<v Speaker 1>Wow, that prevents typos too, exactly.

399
00:19:07.640 --> 00:19:11.119
<v Speaker 2>These collectively make your Linux terminal experience within Windows Terminal

400
00:19:11.480 --> 00:19:12.920
<v Speaker 2>much smarter and faster.

401
00:19:13.359 --> 00:19:16.279
<v Speaker 1>Now, let's talk about taking all this customizability and power

402
00:19:16.319 --> 00:19:20.839
<v Speaker 1>and integrating it with the tools developers use every single day. Get, GitHub,

403
00:19:21.039 --> 00:19:24.200
<v Speaker 1>remote systems, even the cloud, all from Windows Terminal. This

404
00:19:24.240 --> 00:19:27.279
<v Speaker 1>feels like where you become a true command line powerhouse.

405
00:19:27.440 --> 00:19:30.200
<v Speaker 2>Absolutely, this is where it all comes together for Get

406
00:19:30.200 --> 00:19:34.839
<v Speaker 2>and GitHub. A modern setup often involves using SSH authentication.

407
00:19:34.480 --> 00:19:36.960
<v Speaker 1>Instead of HTTPS passwords or tokens.

408
00:19:37.039 --> 00:19:40.480
<v Speaker 2>Yeah, because sshkeys provide a more streamlined workflow that's consistent

409
00:19:40.519 --> 00:19:44.240
<v Speaker 2>across Windows, WSL two and even macOS. If you use

410
00:19:44.279 --> 00:19:46.119
<v Speaker 2>that too, no more password prompts.

411
00:19:46.279 --> 00:19:47.960
<v Speaker 1>Okay, how do you set that up on Windows?

412
00:19:48.160 --> 00:19:51.119
<v Speaker 2>It means installing the built in open ssh client on

413
00:19:51.200 --> 00:19:54.000
<v Speaker 2>Windows ten eleven. It's usually there or easy to add

414
00:19:54.079 --> 00:19:56.960
<v Speaker 2>via optional features. Then you can figure the slish agent

415
00:19:57.000 --> 00:20:00.200
<v Speaker 2>service to run automatically. The agent handles the keys, hold

416
00:20:00.240 --> 00:20:03.279
<v Speaker 2>your decrypted private key in memory securely, so you don't

417
00:20:03.279 --> 00:20:06.559
<v Speaker 2>have to re enter your passphrase constantly. You'll generate modern

418
00:20:06.680 --> 00:20:09.960
<v Speaker 2>public private key pairs EED two five nine time is recommended.

419
00:20:10.000 --> 00:20:12.839
<v Speaker 1>Now share the public key, keep the private key secret.

420
00:20:12.559 --> 00:20:15.400
<v Speaker 2>Exactly, upload the public key to services like get up,

421
00:20:15.440 --> 00:20:18.640
<v Speaker 2>get lab, et cetera. Keep the private key safe. Test

422
00:20:18.720 --> 00:20:24.160
<v Speaker 2>with keysst get at getub dot com. Forget on Linux

423
00:20:24.359 --> 00:20:28.240
<v Speaker 2>WSL two, managing SSH keys gets interesting. You have options

424
00:20:28.759 --> 00:20:31.400
<v Speaker 2>copy your Windows keys into WSL, or maybe share them

425
00:20:31.480 --> 00:20:35.000
<v Speaker 2>via a symbolic link from MNPC and set permissions correctly.

426
00:20:35.440 --> 00:20:37.720
<v Speaker 2>Then use a tool like keychain to manage your lucheche

427
00:20:37.799 --> 00:20:41.000
<v Speaker 2>agent sessions within WSL to itself a.

428
00:20:40.960 --> 00:20:44.079
<v Speaker 1>Bit fiddly, but doable for seamless SSH everywhere.

429
00:20:43.759 --> 00:20:46.440
<v Speaker 2>It is and some seemingly small Get usage tips can

430
00:20:46.480 --> 00:20:49.400
<v Speaker 2>actually dramatically reduce friction and cognitive load day to.

431
00:20:49.440 --> 00:20:52.480
<v Speaker 1>Day, Like what Little Things Matter, Get check.

432
00:20:52.279 --> 00:20:54.480
<v Speaker 2>Out dash switches you to the previous branch.

433
00:20:54.279 --> 00:20:56.720
<v Speaker 1>You're on, oh instead of remembering the name exactly.

434
00:20:56.759 --> 00:20:58.680
<v Speaker 2>It's a mental release, keeps you in the flow. Get

435
00:20:58.720 --> 00:21:02.480
<v Speaker 2>config globalhelp dot Com. Autocorrect twenty tells get to wait

436
00:21:02.519 --> 00:21:05.519
<v Speaker 2>two seconds twenty tens of a second, and automatically fix

437
00:21:05.559 --> 00:21:09.359
<v Speaker 2>simple command typos like get stats because get status as.

438
00:21:09.240 --> 00:21:10.319
<v Speaker 1>Time correcting mistakes.

439
00:21:10.680 --> 00:21:14.000
<v Speaker 2>Love it and get push origin head lets you push

440
00:21:14.039 --> 00:21:17.119
<v Speaker 2>your current branch to its remote counterpart without typing the

441
00:21:17.119 --> 00:21:18.200
<v Speaker 2>branch name again.

442
00:21:18.160 --> 00:21:19.920
<v Speaker 1>Hand you when working on feature branches.

443
00:21:20.400 --> 00:21:24.359
<v Speaker 2>Together, these little things create a much more frictionless Git experience.

444
00:21:24.839 --> 00:21:28.319
<v Speaker 2>You can also define powerful get aliases in your dot

445
00:21:28.400 --> 00:21:30.559
<v Speaker 2>Git canfig like get s, for get.

446
00:21:30.400 --> 00:21:32.240
<v Speaker 1>Status, short and common commands, or.

447
00:21:32.240 --> 00:21:35.480
<v Speaker 2>Even create command aliases that run shell commands, like a

448
00:21:35.559 --> 00:21:38.599
<v Speaker 2>quick get checkpoint alias that stages all changes and commits

449
00:21:38.599 --> 00:21:40.119
<v Speaker 2>them with a generic message.

450
00:21:39.799 --> 00:21:42.279
<v Speaker 1>Quick save point yep, and don't forget.

451
00:21:42.319 --> 00:21:45.759
<v Speaker 2>Tools like tig. It's a fantastic text mode curses based

452
00:21:45.759 --> 00:21:49.599
<v Speaker 2>Git browser for inspecting commits, branches, blame statues right in

453
00:21:49.640 --> 00:21:51.319
<v Speaker 2>your terminal. Very powerful.

454
00:21:51.400 --> 00:21:53.680
<v Speaker 1>Okay, TIG, I'll check that out. What about interacting with

455
00:21:53.759 --> 00:21:54.680
<v Speaker 1>GitHub itself.

456
00:21:54.759 --> 00:21:56.799
<v Speaker 2>That's where the get hub cligh comes in.

457
00:21:57.039 --> 00:22:00.759
<v Speaker 1>Brilliant The disk command yeah, or g off log in.

458
00:22:00.799 --> 00:22:03.079
<v Speaker 2>You can do things like GA repo create, which creates

459
00:22:03.079 --> 00:22:05.680
<v Speaker 2>the repo locally and on GitHub dot com in one step.

460
00:22:05.799 --> 00:22:06.319
<v Speaker 1>Oh nice.

461
00:22:06.400 --> 00:22:10.440
<v Speaker 2>You can ghpr list to see poll requests, ghpr checkout

462
00:22:10.480 --> 00:22:13.759
<v Speaker 2>pr id to instantly check out the code for a

463
00:22:13.839 --> 00:22:18.039
<v Speaker 2>specific pull request. It really simplifies those common GitHub interactions.

464
00:22:18.559 --> 00:22:23.200
<v Speaker 2>Now connecting to remote systems beyond get hosts, maybe actual servers.

465
00:22:22.960 --> 00:22:25.240
<v Speaker 1>Yeah, ssshing into servers, you'll.

466
00:22:25.039 --> 00:22:27.599
<v Speaker 2>Typically choose between win RM, which is more common in

467
00:22:27.640 --> 00:22:31.359
<v Speaker 2>corporate Windows environments, or SSH, which is much more flexible

468
00:22:31.640 --> 00:22:34.000
<v Speaker 2>and works for both Windows servers and Linux servers.

469
00:22:34.160 --> 00:22:36.400
<v Speaker 1>Ssh seems more universal generally.

470
00:22:36.480 --> 00:22:39.279
<v Speaker 2>Yeah. To set up an SSH server on Windows itself,

471
00:22:39.319 --> 00:22:42.240
<v Speaker 2>you install it via optional features. You can even change

472
00:22:42.240 --> 00:22:45.039
<v Speaker 2>the default shell. Users get from CMD to PowerShell core

473
00:22:45.119 --> 00:22:46.319
<v Speaker 2>via a registry.

474
00:22:45.920 --> 00:22:48.240
<v Speaker 1>Key, so I can SSH into Windows and get.

475
00:22:48.039 --> 00:22:51.680
<v Speaker 2>PowerShell you can, and public key authentication is key here too,

476
00:22:51.960 --> 00:22:54.599
<v Speaker 2>using an authorized keys file, just like on Linux. For

477
00:22:54.720 --> 00:22:56.400
<v Speaker 2>secure passwordless access.

478
00:22:56.200 --> 00:22:58.559
<v Speaker 1>Okay, Standard SSH practice.

479
00:22:58.240 --> 00:23:02.079
<v Speaker 2>SEP Secure copy part call which comes with SSH is

480
00:23:02.119 --> 00:23:04.720
<v Speaker 2>your friend for copying files between your local machine and

481
00:23:04.799 --> 00:23:09.519
<v Speaker 2>remote servers or vice versa at cplocalfile dot txt, user

482
00:23:09.799 --> 00:23:13.359
<v Speaker 2>at server dot remote path CLASSICCP. And to make managing

483
00:23:13.400 --> 00:23:16.279
<v Speaker 2>lots of connections easier, use your touch canfig file.

484
00:23:16.200 --> 00:23:17.880
<v Speaker 1>The SSH canfig file.

485
00:23:17.960 --> 00:23:20.960
<v Speaker 2>Yeah, centralize all your connection details there. To find a

486
00:23:21.000 --> 00:23:23.599
<v Speaker 2>host nickname like host home, it's that the host name,

487
00:23:23.680 --> 00:23:26.799
<v Speaker 2>the user, maybe even a remote command to run automatically

488
00:23:26.799 --> 00:23:29.240
<v Speaker 2>on connection. Then you just type spoosh home.

489
00:23:29.200 --> 00:23:31.759
<v Speaker 1>Much easier than remembering ips and usernames.

490
00:23:31.799 --> 00:23:35.400
<v Speaker 2>Definitely. Finally, you can integrate these SSH connections directly into

491
00:23:35.400 --> 00:23:38.720
<v Speaker 2>Windows Terminal, add custom profiles to your settings dot Jason

492
00:23:38.759 --> 00:23:42.039
<v Speaker 2>file that just runs swish home or swoosh work server.

493
00:23:42.279 --> 00:23:43.880
<v Speaker 2>Then that connection is just a click away in the

494
00:23:43.920 --> 00:23:46.000
<v Speaker 2>new tab dropdown menu, or bind it to.

495
00:23:45.960 --> 00:23:50.200
<v Speaker 1>A shortcut seamless SSH access from the terminal menu. Love it, okay? Last,

496
00:23:50.240 --> 00:23:54.960
<v Speaker 1>Big Area cloud Management Azure AWSGCP. Can we manage those

497
00:23:55.000 --> 00:23:56.039
<v Speaker 1>from Windows Terminal too?

498
00:23:56.119 --> 00:23:58.920
<v Speaker 2>Absolutely, It's a huge use case for Microsoft Azure. The

499
00:23:58.920 --> 00:24:02.240
<v Speaker 2>integration is obviously fair tight. Azure cloud Shell often shows

500
00:24:02.279 --> 00:24:04.720
<v Speaker 2>up as an autocreative profile right and Windows Terminals.

501
00:24:04.519 --> 00:24:07.039
<v Speaker 1>Drop down cloudsll profile. What is that?

502
00:24:07.119 --> 00:24:09.839
<v Speaker 2>It connects you to a terminal environment, essentially a Linux

503
00:24:09.880 --> 00:24:12.599
<v Speaker 2>container running an Azure It comes preloaded with all the

504
00:24:12.640 --> 00:24:16.880
<v Speaker 2>Azure Cli tools as age, terraform, quebec, dole, lots of

505
00:24:16.920 --> 00:24:20.519
<v Speaker 2>def tools. Your files can persist in linked Azure storage, so.

506
00:24:20.480 --> 00:24:22.440
<v Speaker 1>Are ready to go Azure environments.

507
00:24:22.200 --> 00:24:25.079
<v Speaker 2>Exactly and inside that or even locally. If you install

508
00:24:25.160 --> 00:24:28.720
<v Speaker 2>the Azure Cli. The as interactive command is amazing. It

509
00:24:28.799 --> 00:24:31.680
<v Speaker 2>drops you to a special shell with smart autocompletion for

510
00:24:31.720 --> 00:24:35.119
<v Speaker 2>commands and parameters, inline documentation, and even.

511
00:24:34.920 --> 00:24:37.519
<v Speaker 1>Examples interactive mode for as.

512
00:24:37.160 --> 00:24:40.079
<v Speaker 2>Plus it helps you learn Jan's path. That's a powerful

513
00:24:40.119 --> 00:24:43.160
<v Speaker 2>query language for filtering and reshaping the Jason output you

514
00:24:43.240 --> 00:24:46.759
<v Speaker 2>get back from cloud APIs. As interactive lets you easily

515
00:24:46.799 --> 00:24:48.599
<v Speaker 2>test james path queries.

516
00:24:48.240 --> 00:24:51.079
<v Speaker 1>Filter that huge JSON blob down to what I need. Okay,

517
00:24:51.200 --> 00:24:52.319
<v Speaker 1>what about Google Cloud?

518
00:24:52.640 --> 00:24:55.559
<v Speaker 2>For Google Cloud, you'll typically use WSL two to run

519
00:24:55.599 --> 00:24:58.599
<v Speaker 2>the g Cloud STK. It works best in a Linux environment.

520
00:24:58.720 --> 00:24:59.839
<v Speaker 2>You run g Cloud in it.

521
00:24:59.799 --> 00:25:01.559
<v Speaker 1>To link your accounts standard setup.

522
00:25:01.640 --> 00:25:04.880
<v Speaker 2>Then you can use g cloud Beta cloudshell shosh authorized

523
00:25:04.880 --> 00:25:07.839
<v Speaker 2>session to launch a connection to your Google cloudshell VM

524
00:25:07.960 --> 00:25:11.880
<v Speaker 2>similar concept to azures and g Cloud Beta Interactive gives

525
00:25:11.920 --> 00:25:15.880
<v Speaker 2>you a similar interactive shell with autocompletion and docks for

526
00:25:16.039 --> 00:25:17.079
<v Speaker 2>g Cloud commands.

527
00:25:17.119 --> 00:25:19.319
<v Speaker 1>So interactive shells are common AWS.

528
00:25:19.359 --> 00:25:23.519
<v Speaker 2>For Amazon Web Services AWS, again, WSL two is often

529
00:25:23.559 --> 00:25:27.119
<v Speaker 2>your best bet. For the standard AWSCLI, there's a tool

530
00:25:27.160 --> 00:25:30.359
<v Speaker 2>called osshell ohshell Yeah. It's a Python based command line

531
00:25:30.359 --> 00:25:35.319
<v Speaker 2>shell specifically for AWS. It provides autocompletion, command history, and

532
00:25:35.400 --> 00:25:38.839
<v Speaker 2>also supports jme's path filtering via the core flag. It

533
00:25:38.880 --> 00:25:41.400
<v Speaker 2>even lets you run local Shell commands using dot cmd.

534
00:25:41.720 --> 00:25:44.519
<v Speaker 1>Nice any PowerShell options for AWS?

535
00:25:44.640 --> 00:25:48.480
<v Speaker 2>Yes, alternatively, there are the AWS tools for PowerShell. These

536
00:25:48.480 --> 00:25:51.799
<v Speaker 2>are native PowerShell modules that provide cmdal that's mapping directly

537
00:25:51.839 --> 00:25:55.000
<v Speaker 2>to the AWSAPI. So if you prefer a PowerShell centric

538
00:25:55.039 --> 00:25:57.640
<v Speaker 2>workflow from editing AWS, that's a great option too.

539
00:25:57.759 --> 00:26:00.160
<v Speaker 1>Okay, tons of power there for cloud management right from

540
00:26:00.160 --> 00:26:01.920
<v Speaker 1>the terminal. So what does this all mean for you,

541
00:26:01.960 --> 00:26:05.799
<v Speaker 1>our listener? From transforming a basic, clunky command prompt into

542
00:26:05.839 --> 00:26:08.279
<v Speaker 1>this multi tab, pain filled powerhouse.

543
00:26:08.359 --> 00:26:09.839
<v Speaker 2>Yeah, it's a huge leap.

544
00:26:09.759 --> 00:26:13.680
<v Speaker 1>To seamlessly running Linux apps side by side with Windows tools,

545
00:26:13.720 --> 00:26:18.640
<v Speaker 1>automating get workflows, managing complex cloud infrastructure. We've seen how

546
00:26:18.640 --> 00:26:21.599
<v Speaker 1>Windows Terminal isn't just a window anymore. It's really your

547
00:26:21.640 --> 00:26:26.279
<v Speaker 1>central hub for productivity. It's about being informed, being efficient,

548
00:26:26.559 --> 00:26:31.240
<v Speaker 1>and truly mastering your digital workspace, all from the command line.

549
00:26:31.559 --> 00:26:33.720
<v Speaker 2>And this raises an important question. I think, now that

550
00:26:33.759 --> 00:26:36.400
<v Speaker 2>you've seen the sheer breadth of what's possible that tabs,

551
00:26:36.440 --> 00:26:40.559
<v Speaker 2>the pains, the shells, the customization, the integrations, what other

552
00:26:40.640 --> 00:26:44.480
<v Speaker 2>tools or workflows could you imagine integrating into your customized

553
00:26:44.519 --> 00:26:47.640
<v Speaker 2>Windows Terminal experience? How could you make your daily work

554
00:26:47.680 --> 00:26:49.079
<v Speaker 2>even more fluid with.

555
00:26:49.039 --> 00:26:53.279
<v Speaker 1>This good question to ponder, Keep exploring, keep customizing, and

556
00:26:53.359 --> 00:26:56.400
<v Speaker 1>keep uncovering those deep insights. We hope this journey has

557
00:26:56.440 --> 00:26:59.480
<v Speaker 1>given you a solid headstart on becoming a Windows terminal pro.

558
00:27:00.160 --> 00:27:00.519
<v Speaker 1>Next time,