WEBVTT

00:00:00.000 --> 00:00:02.759
If you're listening to this as a podcast, remember

00:00:02.759 --> 00:00:06.259
that it was originally recorded as a video. If

00:00:06.259 --> 00:00:08.199
you're not following along, you can go to my

00:00:08.199 --> 00:00:11.720
YouTube channel. My username is Linkarzu. And

00:00:11.720 --> 00:00:14.019
if you want to support me to keep this podcast

00:00:14.019 --> 00:00:17.820
going, you can donate in Ko -fi. I'm going to

00:00:17.820 --> 00:00:20.719
leave a link in the description. All right, so

00:00:20.719 --> 00:00:23.280
let's get started with this chapter then. Hey

00:00:23.280 --> 00:00:26.320
everyone, I have a special guest today, Josh

00:00:26.320 --> 00:00:30.339
Medesky. A lot of you probably know him already.

00:00:30.760 --> 00:00:35.000
Hi, Josh. How's it going? Hey, it's going well.

00:00:35.079 --> 00:00:38.640
Thanks for having me. I watched your videos,

00:00:38.799 --> 00:00:41.340
you know, you got me started with Yabai some

00:00:41.340 --> 00:00:45.539
time ago. So I just wanted to have you over because

00:00:45.539 --> 00:00:49.340
I've been wanting to try your CLI tool. I think

00:00:49.340 --> 00:00:52.259
it is called Sesh, right? It's like a team session

00:00:52.259 --> 00:00:54.619
manager, something like that, right? That's right.

00:00:54.759 --> 00:00:57.740
Yep. A lot of people in the comments have told

00:00:57.740 --> 00:01:02.420
me, have you tried Sesh? And I haven't. So that's

00:01:02.420 --> 00:01:05.219
one of the reasons why you're here. And for everyone

00:01:05.219 --> 00:01:08.260
else watching, just want to get to know Josh

00:01:08.260 --> 00:01:11.140
a little bit more. So I have a series of questions

00:01:11.140 --> 00:01:14.620
here that we'll be going over. I don't know.

00:01:14.620 --> 00:01:16.739
Do you want to say something before we get started

00:01:16.739 --> 00:01:20.260
with the questions, Josh? Sure. I guess general

00:01:20.260 --> 00:01:23.620
background, I'm a full stack developer. Have

00:01:23.620 --> 00:01:27.560
been for about a decade and mostly in the TypeScript

00:01:27.560 --> 00:01:29.599
land by day, but do a lot of other languages

00:01:29.599 --> 00:01:33.900
on the side. And I'm in Texas here in the U .S.

00:01:33.959 --> 00:01:36.959
And yeah, that's a little bit about me outside

00:01:36.959 --> 00:01:40.620
of YouTube. All right. Wonderful. Wonderful.

00:01:42.099 --> 00:01:46.219
I'm in Guatemala, by the way. Nice. I'm more

00:01:46.219 --> 00:01:49.549
like a site reliability engineer. unemployed

00:01:49.549 --> 00:01:51.769
at the moment. I'm looking for a job. I don't

00:01:51.769 --> 00:01:53.030
know what's going to happen. I don't know if

00:01:53.030 --> 00:01:55.370
YouTube is going to work out or not, but we'll

00:01:55.370 --> 00:01:58.069
see. We'll see. Yeah. Good luck either way. Yeah.

00:01:58.349 --> 00:02:02.430
Yeah. So first I have here, well, let me just

00:02:02.430 --> 00:02:07.870
start a timer. Um, we don't have to take 30 minutes

00:02:07.870 --> 00:02:10.710
exactly. It's just so that we can keep track

00:02:10.710 --> 00:02:13.650
of, um, of time. Just going to do this thing

00:02:13.650 --> 00:02:18.370
here. Yeah. And, um, why did you start YouTube?

00:02:18.939 --> 00:02:22.900
And when did you start? It's a question I have.

00:02:24.439 --> 00:02:28.120
Yeah, good question. I think one of my first

00:02:28.120 --> 00:02:31.919
videos was around maybe 2020. I'm trying to think

00:02:31.919 --> 00:02:35.599
about three. I'd say about three years ago, I

00:02:35.599 --> 00:02:38.960
really started making videos mostly on .files

00:02:38.960 --> 00:02:42.280
and macOS and all similar to what you talk about

00:02:42.280 --> 00:02:46.840
here and started doing interviews over that time.

00:02:47.599 --> 00:02:49.560
Because I just wanted to talk to my friends about

00:02:49.560 --> 00:02:51.620
this stuff. And I thought it was interesting

00:02:51.620 --> 00:02:53.659
to record it and share it with others. And that

00:02:53.659 --> 00:02:58.400
seems to be well received so far. And then, yeah,

00:02:58.460 --> 00:03:00.699
like the TMUX stuff and some of the macOS stuff,

00:03:00.819 --> 00:03:03.580
I just found that I was being extremely productive

00:03:03.580 --> 00:03:07.560
after many years of iterating on setups and workflows

00:03:07.560 --> 00:03:10.520
and ideas. And so I thought that it would be

00:03:10.520 --> 00:03:14.090
useful to share that knowledge. Interesting.

00:03:14.169 --> 00:03:16.849
And when you share this with your friends or

00:03:16.849 --> 00:03:19.629
other people, you know, do they understand? Do

00:03:19.629 --> 00:03:23.150
they feel the same way, excited like you or they

00:03:23.150 --> 00:03:25.550
don't care? That's a great question. I think

00:03:25.550 --> 00:03:29.169
the main reason maybe I tried the YouTube thing

00:03:29.169 --> 00:03:33.189
is. Because most of the people I know don't really

00:03:33.189 --> 00:03:35.009
care about this kind of stuff. It's a little

00:03:35.009 --> 00:03:38.050
bit more nerdy than even some of my developer

00:03:38.050 --> 00:03:40.610
friends. So I went out to look for a community

00:03:40.610 --> 00:03:43.689
of like -minded people. And so far, it's going

00:03:43.689 --> 00:03:46.530
well. I'm making lots of new friends that actually

00:03:46.530 --> 00:03:49.830
care about Tmux session management strategies

00:03:49.830 --> 00:03:54.069
and NeoVim plugin configurations and all the

00:03:54.069 --> 00:03:56.569
kind of super, super nerdy stuff that I'm into.

00:03:57.289 --> 00:04:01.469
Yeah, same thing happens here. I talk about this,

00:04:01.469 --> 00:04:05.289
you know, to everyone. No one cares. Not my friends,

00:04:05.449 --> 00:04:09.030
ex -co -workers. Everyone's like, okay, I don't

00:04:09.030 --> 00:04:13.389
care. Yeah, so good. That's when you started

00:04:13.389 --> 00:04:16.589
then. And let's move on to the next one that

00:04:16.589 --> 00:04:20.050
I have here is your operating system of choice.

00:04:20.230 --> 00:04:24.529
Which one is it? And why do you choose that operating

00:04:24.529 --> 00:04:27.160
system? Yeah. So if you can tell from the little

00:04:27.160 --> 00:04:29.579
traffic cones, well, you can't see my screen

00:04:29.579 --> 00:04:33.560
yet, but I'm a Mac OS guy. And I think around

00:04:33.560 --> 00:04:37.120
college, I switched to my, I bought my first

00:04:37.120 --> 00:04:40.000
Mac, which I won't age myself, but it was quite

00:04:40.000 --> 00:04:44.220
a while ago. So I've been here quite some time.

00:04:44.300 --> 00:04:46.699
You're going to see my browser, which I think

00:04:46.699 --> 00:04:48.600
we're going to talk about later. But yeah, so

00:04:48.600 --> 00:04:51.079
Mac OS, it's been great, great to me. I have

00:04:51.079 --> 00:04:55.069
an iPhone, an iPad, an Apple Watch. I tried the

00:04:55.069 --> 00:04:57.370
Vision Pro for a couple of weeks before returning

00:04:57.370 --> 00:05:00.170
it. So I'm a big Apple guy in general. I like

00:05:00.170 --> 00:05:04.189
the ecosystem. And so far it works for me. Okay.

00:05:04.810 --> 00:05:08.129
And what are your thoughts on the other two operating

00:05:08.129 --> 00:05:10.730
systems? We're just going to talk about the most

00:05:10.730 --> 00:05:14.149
known ones, which is Windows, of course, and

00:05:14.149 --> 00:05:17.069
Linux. What are your thoughts? Why didn't you

00:05:17.069 --> 00:05:20.329
switch to one of those? Or why haven't you switched

00:05:20.329 --> 00:05:22.470
to one of those? Why are you still on macOS?

00:05:23.230 --> 00:05:25.430
and um have you used them and what do you think

00:05:25.430 --> 00:05:28.670
about them totally fair question so i have a

00:05:28.670 --> 00:05:32.889
gaming pc on windows and i like to do stable

00:05:32.889 --> 00:05:36.430
diffusion and a lot of those toolings tend to

00:05:36.430 --> 00:05:38.350
really only work well on windows at least some

00:05:38.350 --> 00:05:42.569
of the more specific open source projects and

00:05:42.569 --> 00:05:45.610
so i dabble with windows to be honest though

00:05:45.610 --> 00:05:50.240
i just use the mac os windows desktop you know,

00:05:50.259 --> 00:05:52.939
streaming app. So usually I'm just using Windows

00:05:52.939 --> 00:05:58.420
on my Mac as a virtual machine. Overall, I've

00:05:58.420 --> 00:06:00.300
never been impressed by Windows productivity

00:06:00.300 --> 00:06:03.779
apps. I think that they're really limiting. As

00:06:03.779 --> 00:06:06.420
a good example, things like Raycast, the whole

00:06:06.420 --> 00:06:08.779
concept of Raycast is like a productivity launcher

00:06:08.779 --> 00:06:12.240
and tooling and things like that. I know that

00:06:12.240 --> 00:06:14.959
the Raycast team recently mentioned they're importing

00:06:14.959 --> 00:06:18.199
to Windows, but the idea of that doesn't translate

00:06:18.199 --> 00:06:21.980
well. And I am a computer programmer, so being

00:06:21.980 --> 00:06:25.160
a Unix -based system is just really great. It

00:06:25.160 --> 00:06:27.800
makes everything a lot easier to grasp and to

00:06:27.800 --> 00:06:30.920
understand when it comes to tooling and command

00:06:30.920 --> 00:06:35.660
line stuff and all of that. And for Linux, I've

00:06:35.660 --> 00:06:39.500
used Pop! OS for a while. I liked that one the

00:06:39.500 --> 00:06:43.259
most, which is a branch off of Ubuntu from a

00:06:43.259 --> 00:06:47.639
US -based computer company. What is their name?

00:06:48.040 --> 00:06:50.459
System 76 are the ones that maintain that one.

00:06:50.540 --> 00:06:53.360
And it's good. It's good. It's really good. I

00:06:53.360 --> 00:06:56.379
personally am really, really married to the command

00:06:56.379 --> 00:07:00.319
key. And so between Windows or Linux, everything's

00:07:00.319 --> 00:07:03.199
kind of driven by the control key, which may

00:07:03.199 --> 00:07:05.240
seem like a small thing, but at least for me,

00:07:05.319 --> 00:07:09.800
it was enough to not be enticing enough to switch

00:07:09.800 --> 00:07:14.139
full time. And I... can customize things and

00:07:14.139 --> 00:07:16.540
again there's even a lot of good mac os apps

00:07:16.540 --> 00:07:18.680
i've used over the years that there were never

00:07:18.680 --> 00:07:22.199
any alternative options that were even close

00:07:22.199 --> 00:07:26.720
to me regarding quality or features or whatever

00:07:26.720 --> 00:07:30.879
and so i just keep keep sticking to mac os okay

00:07:30.879 --> 00:07:34.220
but you're open to the other two operating systems

00:07:34.220 --> 00:07:36.699
you mentioned that you use windows for gaming

00:07:36.699 --> 00:07:41.519
right so it's not like you're windows No, I'm

00:07:41.519 --> 00:07:43.699
not anti -Windows. I just don't find myself to

00:07:43.699 --> 00:07:46.279
be very productive there. Yeah, makes sense.

00:07:46.720 --> 00:07:50.720
Especially in the terminal. Like you said, I'm

00:07:50.720 --> 00:07:53.160
used to Unix, you know, and when I switch to

00:07:53.160 --> 00:07:56.420
a Windows machine and I open the terminal, man,

00:07:56.519 --> 00:08:00.199
I just can't do anything. Just to list the contents

00:08:00.199 --> 00:08:03.060
of a directory, typing the dir command. That's

00:08:03.060 --> 00:08:07.600
right. I'm not used to it. All right. Yeah. Good.

00:08:08.279 --> 00:08:14.750
Good, good. And which ID do you use? I think

00:08:14.750 --> 00:08:16.949
we all know the answer to that. Yeah, so I'm

00:08:16.949 --> 00:08:19.350
a NeoVim guy. I wouldn't consider it an IDE.

00:08:19.550 --> 00:08:23.189
I'd call it a text editor with some fancy features

00:08:23.189 --> 00:08:29.329
plugged into it. I've been a Vim user for, I

00:08:29.329 --> 00:08:33.570
would say, maybe eight or nine years. First,

00:08:34.230 --> 00:08:37.730
I started in VS Code. Well, if we go back really,

00:08:37.850 --> 00:08:41.679
really far, you know things like dream weaver

00:08:41.679 --> 00:08:44.299
from adobe was probably my first editor and then

00:08:44.299 --> 00:08:47.159
adam was a really popular one a few years back

00:08:47.159 --> 00:08:49.860
and brackets made an appearance for a little

00:08:49.860 --> 00:08:54.279
while and then you know vs code became a standard

00:08:54.279 --> 00:08:59.259
for most people i actually had a stint for i

00:08:59.259 --> 00:09:01.620
would say almost two years i was in space max

00:09:01.620 --> 00:09:04.200
which is an interesting emacs distro that is

00:09:04.200 --> 00:09:09.340
vim heavy very vim minded And that was a cool

00:09:09.340 --> 00:09:13.759
experience. I like SpaceMax still. And then I'd

00:09:13.759 --> 00:09:16.399
say about five years ago or so, I was like, I

00:09:16.399 --> 00:09:19.519
quit all of those. And I just went into the terminal

00:09:19.519 --> 00:09:21.740
full time. And I went into NeoVim full time.

00:09:22.059 --> 00:09:24.980
And I haven't looked back ever since. And do

00:09:24.980 --> 00:09:27.299
you remember how you felt the first time that

00:09:27.299 --> 00:09:29.620
you opened Vim? Well, not only the first time,

00:09:29.639 --> 00:09:32.519
the first few times that you opened Vim. And

00:09:32.519 --> 00:09:34.580
you needed to do something like edit a file.

00:09:34.700 --> 00:09:36.960
Remember? How was the experience? Can I think

00:09:36.960 --> 00:09:41.379
back that far? I remember being very curious

00:09:41.379 --> 00:09:43.840
where I was like, ooh, this is interesting. What

00:09:43.840 --> 00:09:47.159
is this thing called modals, right? I think all

00:09:47.159 --> 00:09:49.440
of us, the very first time we get into Vim is

00:09:49.440 --> 00:09:52.120
by accident. And so at that point, it's like,

00:09:52.220 --> 00:09:54.620
I don't even know what editor I'm in. What is

00:09:54.620 --> 00:09:56.659
this? You know, it's like, I don't even know

00:09:56.659 --> 00:09:58.960
what is Vim. So that was probably my first experience,

00:09:59.159 --> 00:10:02.950
which we all joke that. exiting vim is like one

00:10:02.950 --> 00:10:05.269
of the hardest things on earth to do if you don't

00:10:05.269 --> 00:10:07.210
know how to do it so there's definitely frustration

00:10:07.210 --> 00:10:10.669
if you kind of blindly end up inside it but at

00:10:10.669 --> 00:10:12.350
the beginning it was interesting it was very

00:10:12.350 --> 00:10:14.929
slow very strange to wrap my head around but

00:10:14.929 --> 00:10:18.710
pretty quickly you can grasp the basic concepts

00:10:18.710 --> 00:10:21.590
and you get used to hitting the escape key a

00:10:21.590 --> 00:10:25.389
lot right yeah and did you stick to vim first

00:10:25.389 --> 00:10:29.080
time or You stopped, you said, because I remember

00:10:29.080 --> 00:10:31.059
what happened to me. I tried it the first time

00:10:31.059 --> 00:10:33.940
and it was like, I don't know what this is. I

00:10:33.940 --> 00:10:36.700
just, I was following a tutorial, I think, and

00:10:36.700 --> 00:10:40.440
a Linux tutorial. And the guy just made me open

00:10:40.440 --> 00:10:44.220
Vim and edit. I think it was like, I don't remember

00:10:44.220 --> 00:10:46.940
what file. Some .file or something, yeah. Yeah,

00:10:46.960 --> 00:10:49.700
some network file, some config file related to

00:10:49.700 --> 00:10:52.039
that. To set up a static IP, I think it was,

00:10:52.100 --> 00:10:54.889
right? I was like, what the hell is this? Why

00:10:54.889 --> 00:10:57.789
do people use this? Yeah, like it doesn't make

00:10:57.789 --> 00:11:00.090
any sense, right? That's what I thought, you

00:11:00.090 --> 00:11:04.450
know, so did you? Yeah, I feel your pain. I think

00:11:04.450 --> 00:11:06.850
it may be on accident. I had opened it a few

00:11:06.850 --> 00:11:09.350
times, but because I've been so curious about

00:11:09.350 --> 00:11:13.889
it for most of my development career, I found

00:11:13.889 --> 00:11:15.730
it really lackluster at the beginning because

00:11:15.730 --> 00:11:18.789
the Vim editor itself, you had older tools like,

00:11:18.889 --> 00:11:21.950
boy, am I going to remember these. There were

00:11:21.950 --> 00:11:24.470
tools for formatting and for code completion

00:11:24.470 --> 00:11:27.370
and things like that. And they were okay. But

00:11:27.370 --> 00:11:29.389
I ultimately found for the longest time that

00:11:29.389 --> 00:11:33.389
using Vim bindings in other editors, like I even

00:11:33.389 --> 00:11:36.029
used WebStorm for a little while. So WebStorm

00:11:36.029 --> 00:11:39.789
and VS Code and Atom and Brackets and all of

00:11:39.789 --> 00:11:41.610
the editors I've used over the years all had

00:11:41.610 --> 00:11:44.809
Vim motions. So that was where I started. And

00:11:44.809 --> 00:11:48.200
that's where I recommend most beginners. that

00:11:48.200 --> 00:11:50.320
want to know about vim i tell them go install

00:11:50.320 --> 00:11:53.460
the vim emulator on your editor get used to the

00:11:53.460 --> 00:11:57.779
modes and the bindings and then if you feel comfortable

00:11:57.779 --> 00:11:59.940
and you have the time and energy to commit to

00:11:59.940 --> 00:12:03.120
understanding and grasping all the terminal related

00:12:03.120 --> 00:12:07.360
stuff you know then switch over is my sort of

00:12:07.360 --> 00:12:11.039
philosophy to most people yeah Great. Thank you

00:12:11.039 --> 00:12:14.299
for sharing that. And what about your window

00:12:14.299 --> 00:12:16.820
manager? What are you using these days? I got

00:12:16.820 --> 00:12:18.840
started in Dubai because of one of your videos.

00:12:19.059 --> 00:12:22.519
So what are you up to? People are asking me that

00:12:22.519 --> 00:12:24.440
a lot lately, and I haven't been able to land

00:12:24.440 --> 00:12:29.480
on a solid answer. So there's a new tool called

00:12:29.480 --> 00:12:32.779
Aerospace that's become really popular, and it's

00:12:32.779 --> 00:12:38.269
an i3 -like tiling manager. It is in beta, and

00:12:38.269 --> 00:12:40.850
I found that it has some memory leaks. And so

00:12:40.850 --> 00:12:45.230
it's kind of like Yubai without having to assign,

00:12:45.529 --> 00:12:48.690
you know, disable system integrity, which is

00:12:48.690 --> 00:12:51.129
one reason that I recently thought, you know

00:12:51.129 --> 00:12:53.029
what, maybe I don't need Yubai. Maybe there's

00:12:53.029 --> 00:12:55.789
a better solution. So I use this for a little

00:12:55.789 --> 00:12:59.009
while. I ultimately am not using it. And so my

00:12:59.009 --> 00:13:01.870
current approach is something built into macOS

00:13:01.870 --> 00:13:05.720
called Stage Manager. And so stage manager just

00:13:05.720 --> 00:13:09.960
puts windows in this little tray on the side.

00:13:10.279 --> 00:13:15.179
And similar to my blazing fast window manager

00:13:15.179 --> 00:13:17.620
video, there was a tool called space launcher

00:13:17.620 --> 00:13:20.620
that I talked about. I now do something slightly

00:13:20.620 --> 00:13:24.299
different, which is I have the option key bound

00:13:24.299 --> 00:13:27.820
to somewhat semantic letters. So like option

00:13:27.820 --> 00:13:32.529
W is for web. So I can go to web, option A for

00:13:32.529 --> 00:13:35.750
my editor. It used to be Alacrity, but the binding

00:13:35.750 --> 00:13:39.409
has stuck. And so I have WASD, right? S would

00:13:39.409 --> 00:13:42.529
be second brain. And you'll notice that they

00:13:42.529 --> 00:13:46.610
sort of just fill in the space available. And

00:13:46.610 --> 00:13:49.269
so the way that Stage Manager works is it takes

00:13:49.269 --> 00:13:52.629
this window and it will basically swap it out

00:13:52.629 --> 00:13:56.799
for another. And so you'll see that. And so I

00:13:56.799 --> 00:13:59.279
just hit that button and it binds it. And if

00:13:59.279 --> 00:14:02.820
I was to say, hey, I want my note taker here,

00:14:02.960 --> 00:14:06.980
I can use a couple bindings and I can have two

00:14:06.980 --> 00:14:09.919
screens at once. I don't do this very much, so

00:14:09.919 --> 00:14:11.759
I haven't even gone through the trouble of making

00:14:11.759 --> 00:14:16.059
it. And you can just sort of drag this guy back

00:14:16.059 --> 00:14:19.799
over to get it back. So unfortunately, all the

00:14:19.799 --> 00:14:22.440
mouse people are going to freak out, right? The

00:14:22.440 --> 00:14:25.139
no mouse people. Um, but I find that because

00:14:25.139 --> 00:14:27.639
the majority of my day is all full screen windows,

00:14:27.940 --> 00:14:32.039
um, that it's fine if I have to grab the mouse

00:14:32.039 --> 00:14:34.720
and drag a window over for, let's say a meeting

00:14:34.720 --> 00:14:36.940
and I need zoom and my note taking app on the

00:14:36.940 --> 00:14:40.580
same screen. I see. Um, but I found aerospace

00:14:40.580 --> 00:14:42.820
to be a little bit too much cause I didn't like,

00:14:42.919 --> 00:14:45.899
I don't really like the auto tiling anymore.

00:14:46.000 --> 00:14:49.539
Yeah. I just prefer, give me full screen width.

00:14:50.539 --> 00:14:52.600
yeah keep it simple and you'll notice my menu

00:14:52.600 --> 00:14:58.440
bar is hidden my dock is hidden um you know where's

00:14:58.440 --> 00:14:59.919
the dock i think the dock usually lives over

00:14:59.919 --> 00:15:02.679
here interesting oh it's not even here because

00:15:02.679 --> 00:15:05.259
this is a secondary screen but yeah so i don't

00:15:05.259 --> 00:15:08.179
use the dock i don't use the menu bar i just

00:15:08.179 --> 00:15:11.980
like a minimalist full screen app on the screen

00:15:11.980 --> 00:15:14.220
yeah that's what i do as well i just keep an

00:15:14.220 --> 00:15:17.120
application on the screen at the at a time well

00:15:17.759 --> 00:15:20.379
One application and the skitty notes thingy that

00:15:20.379 --> 00:15:22.700
you see on the right, which is my notes. Yeah.

00:15:23.340 --> 00:15:26.519
But I just got used to it and I feel that I get

00:15:26.519 --> 00:15:31.799
distracted way less. Yeah. Yeah. And let's see.

00:15:33.220 --> 00:15:36.559
What else do we have here? Oh, your terminal.

00:15:36.919 --> 00:15:39.120
What were you using? I didn't notice what terminal

00:15:39.120 --> 00:15:41.000
you were using and why did you choose that one?

00:15:41.100 --> 00:15:46.370
Yeah. So I'm using Westerm. I know you've spoken

00:15:46.370 --> 00:15:51.289
a lot about Wes' term. And, you know, I really

00:15:51.289 --> 00:15:54.669
like the background image. This background image

00:15:54.669 --> 00:16:00.029
that we see on my terminal right now is something

00:16:00.029 --> 00:16:03.029
that I can change. So if I hit Command -R, this

00:16:03.029 --> 00:16:06.509
is a mid -journey photo I generated. This is

00:16:06.509 --> 00:16:10.929
Severance, any Severance fans. And Outer Wilds,

00:16:10.929 --> 00:16:13.129
a video game I played. So I like personally to

00:16:13.129 --> 00:16:17.940
collect. And because I do the full screen thing,

00:16:18.100 --> 00:16:21.039
right, it's like when I'm full screen on these

00:16:21.039 --> 00:16:24.700
windows, you can't see the wallpaper. And so

00:16:24.700 --> 00:16:27.379
for me, I'm in the terminal so much that I prefer

00:16:27.379 --> 00:16:30.519
this style. Here's a nice one I found from online.

00:16:31.460 --> 00:16:34.419
And so it's just a collection. Here's a new game

00:16:34.419 --> 00:16:37.000
coming up. So I have things that I anticipate.

00:16:37.200 --> 00:16:40.539
And Minecraft, you know, is always fun. And so

00:16:40.539 --> 00:16:44.700
it's just a really simple way to. control that.

00:16:45.080 --> 00:16:47.639
And I like the Lua programming language. And

00:16:47.639 --> 00:16:50.580
so all of this is driven by Lua. And I have high

00:16:50.580 --> 00:16:54.960
performance setup and max FPS. And so it's very

00:16:54.960 --> 00:17:00.240
buttery smooth. Yeah, I even have the ability

00:17:00.240 --> 00:17:03.820
to like switch between fonts. So if I wanted

00:17:03.820 --> 00:17:07.319
to do that, I could. And then this get wallpaper

00:17:07.319 --> 00:17:12.319
is just, you know, wallpaper. It's just a quick

00:17:12.319 --> 00:17:15.000
little Lua thing combined with Westerm. So I

00:17:15.000 --> 00:17:17.759
get to do cool programmatic stuff. I've talked

00:17:17.759 --> 00:17:20.460
about it in depth in my channel as well. I like

00:17:20.460 --> 00:17:24.720
to use keyboard bindings that are Mac OS style

00:17:24.720 --> 00:17:28.059
for my editor. So if I hit Command T, it creates

00:17:28.059 --> 00:17:31.019
a new TMUX window. If I hit Command W, it closes

00:17:31.019 --> 00:17:35.059
a TMUX pane. If I hit Command K, I get my sesh

00:17:35.059 --> 00:17:37.220
switcher so I can switch between projects with

00:17:37.220 --> 00:17:40.269
Command K. If there's more than one thing open,

00:17:40.450 --> 00:17:42.829
I can do command shift bracket. For those that

00:17:42.829 --> 00:17:45.750
don't know, you can move between tabs. So I have

00:17:45.750 --> 00:17:50.529
all that bound using a couple of combined functions.

00:17:50.730 --> 00:17:54.109
And even command S works. Command S can save.

00:17:55.569 --> 00:17:59.670
So yeah. That seems pretty useful. And how do

00:17:59.670 --> 00:18:02.250
you feel when using a terminal without a desktop

00:18:02.250 --> 00:18:04.890
background? A lot of people tell me that, like,

00:18:04.950 --> 00:18:08.549
how can you use a terminal? and see that picture

00:18:08.549 --> 00:18:11.349
in the background a lot of people in the comments

00:18:11.349 --> 00:18:14.049
and reddit and basically everywhere sure tell

00:18:14.049 --> 00:18:16.190
me the same thing how do you feel when using

00:18:16.190 --> 00:18:19.509
a terminal without a desktop background how do

00:18:19.509 --> 00:18:22.690
i feel i mean because i've ingrained it in west

00:18:22.690 --> 00:18:26.069
term i like just it's just visually pleasing

00:18:26.069 --> 00:18:30.369
but having just a blank screen to me is just

00:18:30.369 --> 00:18:33.819
boring i'm just a visually oriented person And

00:18:33.819 --> 00:18:36.359
I'm sure we could just disable this, right? And

00:18:36.359 --> 00:18:39.559
it would just go away. So, okay, it's black.

00:18:39.880 --> 00:18:43.460
Like, whatever. But so it's not, it's just to

00:18:43.460 --> 00:18:46.900
my own benefit that I can see something pleasant.

00:18:47.500 --> 00:18:51.140
Yeah, I got used to it as well. And in my work

00:18:51.140 --> 00:18:55.200
computer, I couldn't disable zip. So I was using

00:18:55.200 --> 00:19:00.079
Yabai, but I couldn't set the transparency. So

00:19:00.079 --> 00:19:02.180
I had to use the terminal, you know, with the

00:19:02.180 --> 00:19:06.000
solid. color i just didn't like it i felt something

00:19:06.000 --> 00:19:08.900
was missing i cannot explain it i got used to

00:19:08.900 --> 00:19:11.720
it i think yeah i mean it's the same i mean i

00:19:11.720 --> 00:19:14.240
don't what i've learned recently is i really

00:19:14.240 --> 00:19:18.680
don't like having a desktop wallpaper so if you

00:19:18.680 --> 00:19:21.059
have a macbook pro or a similar kind of computer

00:19:21.059 --> 00:19:23.740
you'll notice there's a black notch sitting at

00:19:23.740 --> 00:19:26.779
the top of your screen right it's like this like

00:19:26.779 --> 00:19:30.400
thing that sticks out and if you set your desktop

00:19:30.400 --> 00:19:32.910
to black it just goes away yeah and if you're

00:19:32.910 --> 00:19:34.930
on a if i'm on a studio display so when there's

00:19:34.930 --> 00:19:38.109
a little bit of spacing between my windows it's

00:19:38.109 --> 00:19:40.450
just invisible you can't even notice that that

00:19:40.450 --> 00:19:42.890
space is there so everything just sort of floats

00:19:42.890 --> 00:19:46.849
and then when i'm editing you know when i'm editing

00:19:46.849 --> 00:19:51.230
that the wallpapers are used on the terminal

00:19:51.230 --> 00:19:54.869
emulator itself yeah interesting great idea okay

00:19:54.869 --> 00:19:58.109
and um to navigate between your projects how

00:19:58.109 --> 00:20:01.849
do you how do you do it you use tmux if you Don't

00:20:01.849 --> 00:20:05.410
like Tmux? Do you love Tmux? Are you on the love

00:20:05.410 --> 00:20:10.109
or hate Tmux side of the house? I've invested

00:20:10.109 --> 00:20:14.170
part of my career on Tmux. So most people that

00:20:14.170 --> 00:20:16.869
are beyond the macOS stuff will know me for Tmux.

00:20:17.009 --> 00:20:20.009
I've actually authored, how many, at least three

00:20:20.009 --> 00:20:23.710
or four Tmux plugins, all of which have hundreds

00:20:23.710 --> 00:20:26.430
of stars. I think we're almost at a thousand

00:20:26.430 --> 00:20:29.650
on Sesh. So slowly starting to build my open

00:20:29.650 --> 00:20:33.660
source. um, you know, career, you could call

00:20:33.660 --> 00:20:38.619
it on, uh, on Tmux. And so, yeah, I have a really

00:20:38.619 --> 00:20:41.559
popular video talking about how I do smart Tmux

00:20:41.559 --> 00:20:45.500
session management with Zoxide and FZF, you know,

00:20:45.500 --> 00:20:49.180
and, uh, I ended up porting that over to Golang

00:20:49.180 --> 00:20:53.000
using some, uh, a few popular Go libraries and

00:20:53.000 --> 00:20:57.640
some CLI, uh, integrations. And I was able to

00:20:57.640 --> 00:21:01.240
build Sesh. which is basically a robust version

00:21:01.240 --> 00:21:05.019
of that Zoxide FCF tool that I had originally

00:21:05.019 --> 00:21:08.299
authored a few years ago. And it's going well.

00:21:08.380 --> 00:21:10.279
I've been adding features and I've been fixing

00:21:10.279 --> 00:21:15.579
TMUX problems. And if anyone was noticing, one

00:21:15.579 --> 00:21:18.420
of the ones I maintain is a fork, but I can open

00:21:18.420 --> 00:21:23.960
URLs with a key binding. I swap out all my TMUX

00:21:23.960 --> 00:21:26.839
window names for emojis, basically, or nerd font

00:21:26.839 --> 00:21:29.920
icons. So I get a really minimalist look there.

00:21:30.640 --> 00:21:33.720
And so, yeah, I'm a huge, huge T -Mex person.

00:21:34.680 --> 00:21:39.079
Wonderful. All right. And right. Let's move on

00:21:39.079 --> 00:21:41.779
to something else then. On all the topics, I

00:21:41.779 --> 00:21:44.440
don't have them organized in a good way here.

00:21:44.559 --> 00:21:47.339
I just slapped them there and I don't think they

00:21:47.339 --> 00:21:49.559
make any sense, but we're just jumping between

00:21:49.559 --> 00:21:51.900
stuff. We could talk keyboards, I think is next

00:21:51.900 --> 00:21:54.680
on the list. Yeah. Yeah. If you want to share

00:21:54.680 --> 00:21:56.819
my screen, you can see these are the boards I

00:21:56.819 --> 00:22:01.180
use day to day. So I'm a long ZSA user. I use

00:22:01.180 --> 00:22:06.079
the ErgoDox for the longest time. So this was

00:22:06.079 --> 00:22:08.380
my main board for many, many years. And then

00:22:08.380 --> 00:22:10.680
they came out with another board, the Moonlander.

00:22:10.680 --> 00:22:12.400
I think it was like four or five years ago now.

00:22:12.480 --> 00:22:15.660
I've been using this mostly full time. When I'm

00:22:15.660 --> 00:22:19.160
on the road, I like using the Nufi Air. And I

00:22:19.160 --> 00:22:21.559
bought myself a little Lego keyboard recently.

00:22:21.839 --> 00:22:24.460
So this is made out of Lego bricks. It's kind

00:22:24.460 --> 00:22:26.359
of fun to play with. And this is another one

00:22:26.359 --> 00:22:28.359
I bought for myself a while back. It's a nice

00:22:28.359 --> 00:22:31.920
little 80 % board. So I'll swap between boards

00:22:31.920 --> 00:22:34.900
when I'm in the mood. But I would say probably

00:22:34.900 --> 00:22:39.519
80 % of the time I'm on my Moonlander. Okay.

00:22:39.599 --> 00:22:42.000
And why did you switch or why did you try a split

00:22:42.000 --> 00:22:45.279
keyboard? Was there like a... specific reason?

00:22:45.440 --> 00:22:49.480
Did you have sort of pain or something? Yeah,

00:22:49.599 --> 00:22:52.480
definitely. I didn't have carpal tunnel or any

00:22:52.480 --> 00:22:56.180
major injury yet, but I would say most of my

00:22:56.180 --> 00:22:58.720
hobbies also included a lot of hand coordination

00:22:58.720 --> 00:23:02.500
and dexterity. And so things like video games

00:23:02.500 --> 00:23:05.099
and stuff like that. And so combining all that

00:23:05.099 --> 00:23:09.099
in my probably mid -20s, I was like, hey, I need

00:23:09.099 --> 00:23:11.819
to sustain my hands. I need to not, you know,

00:23:11.839 --> 00:23:15.019
end up. you know, crippled because I spent too

00:23:15.019 --> 00:23:17.180
much time doing this stuff. So yeah, it was mostly

00:23:17.180 --> 00:23:20.400
just an intentional choice on better ergonomics.

00:23:21.059 --> 00:23:25.680
And I had other boards that I don't have any

00:23:25.680 --> 00:23:28.400
photos, but like the Microsoft sculpt was the

00:23:28.400 --> 00:23:30.339
first thing I went out and bought when I was

00:23:30.339 --> 00:23:32.539
starting to feel wrist pain with the default.

00:23:33.450 --> 00:23:36.089
Mac OS keyboard is really small and the travel

00:23:36.089 --> 00:23:38.329
is really short. So you kind of, your wrists

00:23:38.329 --> 00:23:40.950
are cramped and you end up, I can type really

00:23:40.950 --> 00:23:42.730
fast on that one, but that wasn't necessarily

00:23:42.730 --> 00:23:47.970
a benefit to my ergonomics. So, yeah. Yeah, it

00:23:47.970 --> 00:23:49.890
seems that exactly the same thing happened to

00:23:49.890 --> 00:23:52.509
me. I can type, well, I could type really fast

00:23:52.509 --> 00:23:55.250
on the Mac OS Magic Keyboard. You know, I love

00:23:55.250 --> 00:23:57.750
it. I love the way it feels, right? Because it's

00:23:57.750 --> 00:24:02.599
so... soft so smooth so i i do like the the way

00:24:02.599 --> 00:24:06.099
that it feels but i started experiencing forearm

00:24:06.099 --> 00:24:10.660
pain and it was a lot of pain so yeah i had to

00:24:10.660 --> 00:24:13.519
make a choice that's right and what board are

00:24:13.519 --> 00:24:16.720
you on now oh this is the glove 80 yeah this

00:24:16.720 --> 00:24:19.759
is the one that i decided to go with um yeah

00:24:19.759 --> 00:24:22.160
i wasn't sure if going with this one or the one

00:24:22.160 --> 00:24:24.380
that the primogen uses which is what is it called

00:24:24.380 --> 00:24:27.589
the kinesis advantage yeah That's a good board

00:24:27.589 --> 00:24:29.670
too. I'm a nerd. I know about all the boards.

00:24:29.710 --> 00:24:32.349
I don't have unlimited budget. Otherwise, I'd

00:24:32.349 --> 00:24:34.670
probably just keep buying boards. And I think

00:24:34.670 --> 00:24:36.750
it'd be fun to build my own one day. And so I

00:24:36.750 --> 00:24:39.750
have some ideas. I have some prototypes and some

00:24:39.750 --> 00:24:42.509
sketches about ways I might be able to design

00:24:42.509 --> 00:24:44.730
my own mechanical keyboard. But that'll be a

00:24:44.730 --> 00:24:47.970
whole new hobby to enter. And I'm not quite prepared

00:24:47.970 --> 00:24:51.750
for that. There's a guy in Discord that created

00:24:51.750 --> 00:24:55.369
his own prototype. I don't know how many keys

00:24:55.369 --> 00:24:58.269
it has. But he has a YouTube channel. He has

00:24:58.269 --> 00:25:02.630
a lot of subscribers. And he created his own.

00:25:03.150 --> 00:25:07.190
And it's pretty good, you know. Great. Yeah,

00:25:07.269 --> 00:25:10.670
I have a lot of people in my community where

00:25:10.670 --> 00:25:13.390
we talk a lot about keyboards. There's a lot

00:25:13.390 --> 00:25:15.809
of them that are way more hardcore than me. And

00:25:15.809 --> 00:25:17.650
I want to make a point, I guess, before we move

00:25:17.650 --> 00:25:22.009
on. And that is for this, you know, there's a

00:25:22.009 --> 00:25:26.049
thumb cluster. It's really easy to say I'm going

00:25:26.049 --> 00:25:28.569
to make up some really, really specific and custom

00:25:28.569 --> 00:25:31.970
feature or I'm going to leverage like there's

00:25:31.970 --> 00:25:34.049
a lot of cool features like auto shift where

00:25:34.049 --> 00:25:36.269
you can hold a key on these keyboards and it'll

00:25:36.269 --> 00:25:38.109
automatically shift the letter and stuff like

00:25:38.109 --> 00:25:42.269
that. I have mostly moved away from that and

00:25:42.269 --> 00:25:44.589
I have done my best to make all of my boards

00:25:44.589 --> 00:25:48.130
fairly simple. You know, the command key is mostly

00:25:48.130 --> 00:25:51.160
in the same place. For me, it's here where you'd

00:25:51.160 --> 00:25:55.160
expect the command key and alt and control. And

00:25:55.160 --> 00:25:58.400
I have to move a few things around on this board

00:25:58.400 --> 00:26:02.140
in particular because its layout is kind of weird.

00:26:02.319 --> 00:26:04.799
But when I switch keyboards, it feels familiar.

00:26:05.039 --> 00:26:07.619
So I'm not leaning into like, let me do something

00:26:07.619 --> 00:26:10.259
really, really crazy with this board and override

00:26:10.259 --> 00:26:13.359
everything with carabiner elements or with...

00:26:14.170 --> 00:26:17.650
you know qmk you know yeah yeah yeah and every

00:26:17.650 --> 00:26:22.049
keyboard yeah so i've kept it really simple um

00:26:22.049 --> 00:26:24.569
over the years i tried really complicated things

00:26:24.569 --> 00:26:27.490
and i i found that if i wanted to buy a new keyboard

00:26:27.490 --> 00:26:29.970
or plug a new keyboard in either my carabiner

00:26:29.970 --> 00:26:31.950
elements type thing would get really complicated

00:26:31.950 --> 00:26:34.130
really fast or there were features that just

00:26:34.130 --> 00:26:37.289
weren't available and so it's like okay then

00:26:37.289 --> 00:26:40.609
i'm just gonna keep it simple yeah easy i i have

00:26:40.609 --> 00:26:43.609
a similar approach everyone tells me Why don't

00:26:43.609 --> 00:26:46.109
I use layers? Because this keyboard is designed

00:26:46.109 --> 00:26:49.589
for that, right? So use layers and get stuff

00:26:49.589 --> 00:26:52.210
really complex. I don't want to. Why? Because

00:26:52.210 --> 00:26:56.250
I switched to the laptop computer and there is

00:26:56.250 --> 00:26:59.390
a regular keyboard. I want to be as fast there

00:26:59.390 --> 00:27:03.609
as I'm on this other keyboard. So I keep it simple

00:27:03.609 --> 00:27:06.970
as well. Even the numbers, I have the numbers

00:27:06.970 --> 00:27:10.210
here where they belong. I type the numbers at

00:27:10.210 --> 00:27:13.000
the top. Yeah, I don't have like a layer for

00:27:13.000 --> 00:27:15.900
numbers and symbols. Everything is just the default.

00:27:16.539 --> 00:27:18.819
Yeah, I think it works for me to keep it simple.

00:27:19.359 --> 00:27:24.099
Yeah, yeah, that's true. And let's see. Okay,

00:27:24.200 --> 00:27:26.140
let's move on to the next topic then. Let me

00:27:26.140 --> 00:27:28.599
just switch to the other screen. How do you use

00:27:28.599 --> 00:27:31.400
AI? What do you think about AI? Well, I don't

00:27:31.400 --> 00:27:34.980
want to go too in depth here, but how do you

00:27:34.980 --> 00:27:39.880
use it? Yeah, so. I can point people to, you

00:27:39.880 --> 00:27:43.720
know, I did a NeoVim and AI talk last year at

00:27:43.720 --> 00:27:46.359
NeoVimConf. And so I spoke a lot about all the

00:27:46.359 --> 00:27:50.140
options that were available at that time. So

00:27:50.140 --> 00:27:52.819
I currently use Avante a lot, which is like a

00:27:52.819 --> 00:27:57.779
cursor style NeoVim plugin, Avante. And this

00:27:57.779 --> 00:28:01.460
is the tool that lets me, you know, use language

00:28:01.460 --> 00:28:05.539
models in my code editing. And I use Copilot

00:28:05.539 --> 00:28:08.730
for completion. And so I use those a lot. And

00:28:08.730 --> 00:28:11.930
I actually am a Raycast member. So I also use,

00:28:11.950 --> 00:28:15.809
you know, Raycast Pro, which gives me access

00:28:15.809 --> 00:28:19.589
to all these models. So if I'm, I don't know

00:28:19.589 --> 00:28:22.549
if I'm moderating, not moderating, if I'm editing

00:28:22.549 --> 00:28:25.269
a document or I'm asking for a question or I'm

00:28:25.269 --> 00:28:28.250
brainstorming ideas, I use AI pretty much all

00:28:28.250 --> 00:28:32.089
day, every day. Yeah, me too. And this Avante,

00:28:32.170 --> 00:28:35.549
is it like a plugin that you run inside NeoVim

00:28:35.549 --> 00:28:38.069
or is it like it's... That's right. It's just

00:28:38.069 --> 00:28:41.130
a plugin for NeoVim. And because I'm a Copilot

00:28:41.130 --> 00:28:44.170
owner, because I have a Copilot subscription,

00:28:44.750 --> 00:28:49.470
Copilot is my provider for that tool. Interesting.

00:28:49.769 --> 00:28:52.250
And so I'm just, I'm not paying, you know, I'm

00:28:52.250 --> 00:28:57.410
not paying for Cloud API usage or OpenAI, you

00:28:57.410 --> 00:29:00.539
know, custom API key usage. I just, I'm giving

00:29:00.539 --> 00:29:03.839
GitHub Copilot, you know, a fee every, I think

00:29:03.839 --> 00:29:05.759
it's a yearly thing and it just works for me.

00:29:05.839 --> 00:29:07.819
And I think under the hood, Copilot's currently

00:29:07.819 --> 00:29:11.779
using chat GPT 4 .0 maybe as its default model.

00:29:12.740 --> 00:29:15.619
And so it's been working well. And I have lots

00:29:15.619 --> 00:29:17.440
of others. We can go into it a whole bunch, but

00:29:17.440 --> 00:29:23.420
like there's an app called Kot, Kot PS that lets

00:29:23.420 --> 00:29:26.460
you basically put autocomplete in anywhere in

00:29:26.460 --> 00:29:29.130
your computer. This one's great. This one's really,

00:29:29.230 --> 00:29:31.089
really great. And it saves me, it tells me how

00:29:31.089 --> 00:29:34.009
many words I save. I've saved 16 words today.

00:29:34.549 --> 00:29:37.009
So most of it's just common sense things, like

00:29:37.009 --> 00:29:38.569
I'm writing a sentence and it's like, hey, I

00:29:38.569 --> 00:29:40.529
think I know at the end of this sentence. Yeah.

00:29:40.789 --> 00:29:42.529
It's like, yep, yep, that's pretty good. It does

00:29:42.529 --> 00:29:46.069
it on Obsidian as well. So it's just a helpful

00:29:46.069 --> 00:29:48.410
little tool for me. That seems pretty useful,

00:29:48.490 --> 00:29:52.509
actually. But not in NeoVim, right? Not in NeoVim,

00:29:52.509 --> 00:29:54.190
because I have Copilot and all those things.

00:29:54.630 --> 00:29:58.809
Okay. Interesting. And I also recently set up

00:29:58.809 --> 00:30:04.490
an O -Lama tool that lets me ask for prompts

00:30:04.490 --> 00:30:09.289
and get the output via a language model. In this

00:30:09.289 --> 00:30:11.890
case, I just use a local language model. So I

00:30:11.890 --> 00:30:17.650
can say, say hi to link, right? And I just hit

00:30:17.650 --> 00:30:20.730
a binding in the language model. Oh, that's funny,

00:30:20.829 --> 00:30:22.930
redacted. So it's not perfect, but I've been

00:30:22.930 --> 00:30:28.309
playing around with that. And I've been experimenting

00:30:28.309 --> 00:30:34.069
with a tool for, let's see, let's just copy that,

00:30:34.269 --> 00:30:37.829
called Lumen, which is funny because I was just

00:30:37.829 --> 00:30:42.210
talking about, it's a reference to a severance

00:30:42.210 --> 00:30:45.589
that show that's out right now. I can pass Lumen,

00:30:45.750 --> 00:30:48.789
it reads the staging elements and it spits out

00:30:48.789 --> 00:30:52.049
a git commit message for me. So this one's been

00:30:52.049 --> 00:30:56.220
kind of fun to experiment with. I'm always on

00:30:56.220 --> 00:30:58.900
the lookout for interesting use cases for language

00:30:58.900 --> 00:31:03.079
models. Okay. This isn't integrated into my workflow

00:31:03.079 --> 00:31:05.859
yet, but it's a fun teaser of like, hey, there

00:31:05.859 --> 00:31:08.940
are lots of clever uses for language models that

00:31:08.940 --> 00:31:12.599
people are coming up with. Interesting. And how

00:31:12.599 --> 00:31:15.640
do you keep history of them in Raycast Pro? Can

00:31:15.640 --> 00:31:18.400
you keep history of your conversations? Or is

00:31:18.400 --> 00:31:21.380
it just like a temporary sort of thing? It's

00:31:21.380 --> 00:31:23.519
all sorts of things. It kind of varies a whole

00:31:23.519 --> 00:31:25.839
lot. You can search those things and go back

00:31:25.839 --> 00:31:30.380
to them. You can now speak to things like Apple

00:31:30.380 --> 00:31:34.640
Notes, browser, clipboard history. So you can

00:31:34.640 --> 00:31:37.200
dump a lot of data into this and get feedback

00:31:37.200 --> 00:31:40.319
out. You can drop files in here. You can generate

00:31:40.319 --> 00:31:42.480
images here. So there's a whole lot of powerful

00:31:42.480 --> 00:31:46.029
features there that I enjoy using. As I went

00:31:46.029 --> 00:31:49.329
back to the regular chat GPT copy pasting, but

00:31:49.329 --> 00:31:51.289
I think this I didn't know that you could keep

00:31:51.289 --> 00:31:53.630
history of conversation. So it's basically like

00:31:53.630 --> 00:31:56.329
a chat GPT interface, but you can use different

00:31:56.329 --> 00:31:59.549
models, right? Yep. And it's always available.

00:31:59.710 --> 00:32:02.769
So it's just one hotkey away. Interesting. And

00:32:02.769 --> 00:32:05.490
funny enough, I actually do this. I'll show you

00:32:05.490 --> 00:32:08.450
one more thing and we can go. I can say who is

00:32:08.450 --> 00:32:14.220
Link R Zoo YouTuber. And if I hit tab. I use

00:32:14.220 --> 00:32:16.319
this way more than I actually search things on

00:32:16.319 --> 00:32:19.740
the web. So I see you're on TikTok too. That's

00:32:19.740 --> 00:32:22.599
cool. Tech related tutorials and content. Oh,

00:32:22.759 --> 00:32:25.119
interesting. About these tools. And so it uses,

00:32:25.319 --> 00:32:29.099
you know, it uses web searching combined with

00:32:29.099 --> 00:32:33.380
LLMs to give me. Oh, I see. Results. It seems

00:32:33.380 --> 00:32:38.410
pretty interesting. Yeah, it's so helpful. So

00:32:38.410 --> 00:32:41.829
yeah, I could talk about AI all day. Even my

00:32:41.829 --> 00:32:45.490
search engine is AI driven. And so, yeah, I use

00:32:45.490 --> 00:32:48.670
it for everything all the time now. Okay, wonderful.

00:32:49.009 --> 00:32:52.789
Thanks for sharing all that. And what projects

00:32:52.789 --> 00:32:55.589
are you currently working on? We've been at 32

00:32:55.589 --> 00:32:59.009
minutes right now. Yeah, you know, I work on

00:32:59.009 --> 00:33:02.650
Sesh. I'm continuing to add features to it on

00:33:02.650 --> 00:33:08.240
the side. My day job, I work at a company that

00:33:08.240 --> 00:33:11.339
focuses on utility management. And so I build

00:33:11.339 --> 00:33:14.079
a lot of products for them. I looked up my get

00:33:14.079 --> 00:33:16.400
stats and I wrote something like 70 ,000 lines

00:33:16.400 --> 00:33:19.980
of code last year. So really productive. I think

00:33:19.980 --> 00:33:22.400
I was at like 5 ,000 commits or something. So,

00:33:22.400 --> 00:33:26.720
you know, ripping solutions on the day job. So

00:33:26.720 --> 00:33:30.519
I don't necessarily constantly drive myself to

00:33:30.519 --> 00:33:33.119
do more, you know, at night. But SESH is important

00:33:33.119 --> 00:33:35.500
to me. I do a little bit of game development

00:33:35.500 --> 00:33:38.440
right now. I've been learning more about 3D modeling.

00:33:38.680 --> 00:33:41.039
So, you know, just tinkering, learning some new

00:33:41.039 --> 00:33:43.700
things where I can and spending time on my open

00:33:43.700 --> 00:33:46.859
source projects when it seems important to add

00:33:46.859 --> 00:33:52.740
to or improve on those systems. Interesting.

00:33:53.039 --> 00:33:55.960
Let's just quickly go over the next one. Just

00:33:55.960 --> 00:33:59.309
name them, your three favorite CLI tools. You

00:33:59.309 --> 00:34:01.250
don't have to go in deep. Just name them basically.

00:34:01.269 --> 00:34:03.569
FCF for sure. FCF is probably the top of the

00:34:03.569 --> 00:34:06.910
list. I'm going to say Sesh because it's technically

00:34:06.910 --> 00:34:09.389
a CLI tool and it's mine. So I'm going to say

00:34:09.389 --> 00:34:14.030
Sesh. And then I'll also say, I think I'll say

00:34:14.030 --> 00:34:18.289
Lazy Git. Lazy Git. It's not perfect, but it's

00:34:18.289 --> 00:34:21.269
been really reliable for me for many years. So

00:34:21.269 --> 00:34:24.750
it's one I use every day. Wonderful. And your

00:34:24.750 --> 00:34:31.420
macOS apps? An Arc user for the web browser.

00:34:31.880 --> 00:34:34.719
It's my favorite because it's just so good. And

00:34:34.719 --> 00:34:37.139
I haven't found a good alternative yet, although

00:34:37.139 --> 00:34:40.139
we're all looking, I think. So Arc, at this point,

00:34:40.179 --> 00:34:44.000
Arc. Raycast, for sure. Raycast is probably the

00:34:44.000 --> 00:34:45.980
thing that makes me the most productive, aside

00:34:45.980 --> 00:34:51.639
from Sesh. And then the third, I'm going to call.

00:34:52.420 --> 00:34:59.059
I did call out Copiest. Hmm. I'm going to call

00:34:59.059 --> 00:35:01.440
out Tailscale. I don't know if you know what

00:35:01.440 --> 00:35:04.440
Tailscale is, but it's a way to create a virtual

00:35:04.440 --> 00:35:07.420
private network. Yeah, I did. I was trying to

00:35:07.420 --> 00:35:11.059
do a Rust server for gaming. I tried to use Tailscale,

00:35:11.159 --> 00:35:13.280
didn't work, moved on to something else. But

00:35:13.280 --> 00:35:17.179
yeah, I've heard of it. So I have some Homelab

00:35:17.179 --> 00:35:20.480
stuff. And there are moments where it would be

00:35:20.480 --> 00:35:22.480
really nice to connect to those things outside

00:35:22.480 --> 00:35:25.440
of my network. And so Tailscale, I just recently

00:35:25.440 --> 00:35:28.659
set up and it was really easy. So like Home Assistant

00:35:28.659 --> 00:35:33.219
is my smart home manager. And now without any

00:35:33.219 --> 00:35:35.880
crazy certificates or port forwarding or anything

00:35:35.880 --> 00:35:39.800
wild, I can just connect to Tailscale and pull

00:35:39.800 --> 00:35:41.559
up the Home Assistant app on my phone from anywhere

00:35:41.559 --> 00:35:44.099
and it just works. It just connects. So super

00:35:44.099 --> 00:35:48.780
nice. Wonderful. All right. And where can people

00:35:48.780 --> 00:35:51.679
find you? Let me share your screen so you can

00:35:51.679 --> 00:35:55.199
show where people can find you. Yeah, so head

00:35:55.199 --> 00:35:59.900
to joshmadesky .com. You'll see I'm on YouTube.

00:36:00.360 --> 00:36:03.440
I have a Discord server. And you follow me on,

00:36:03.440 --> 00:36:05.760
you know, I'm on all the social medias. So X.

00:36:07.820 --> 00:36:09.960
I'm on Blue Sky now. Maybe I could add that to

00:36:09.960 --> 00:36:12.900
my website. But if you just want to see my posts

00:36:12.900 --> 00:36:15.480
and videos, you can go through here. Here's the

00:36:15.480 --> 00:36:18.039
last one that I did. And I think I talked about

00:36:18.039 --> 00:36:20.820
my AI talk. So you'll find that toward the top

00:36:20.820 --> 00:36:24.099
of my website. But the Discord server is where

00:36:24.099 --> 00:36:26.639
we spend a lot of time talking about this stuff.

00:36:26.760 --> 00:36:28.519
So that's where I tend to tell people to go and

00:36:28.519 --> 00:36:31.659
have more conversations with me. Yeah, we share

00:36:31.659 --> 00:36:34.139
a lot of users. I'm pretty sure a lot of the

00:36:34.139 --> 00:36:36.519
subscribers that I have are already subscribed

00:36:36.519 --> 00:36:40.559
to your channel. Yeah, like -minded people for

00:36:40.559 --> 00:36:43.559
sure. And of course, I do recommend if you would

00:36:43.559 --> 00:36:47.079
follow me on YouTube. I'm getting there. I haven't

00:36:47.079 --> 00:36:51.929
been growing too quickly. Slow and steady, you

00:36:51.929 --> 00:36:56.369
know? Yeah. Great. Wonderful. All right. So let's

00:36:56.369 --> 00:36:59.650
move on to the next section there of the, what

00:36:59.650 --> 00:37:01.989
is this? Is it an interview? What is it? I don't

00:37:01.989 --> 00:37:06.829
know. It's just something. A lesson maybe? Yeah.

00:37:07.030 --> 00:37:12.030
Yeah. Sesh is the next topic then. So I want

00:37:12.030 --> 00:37:14.210
to try it out. I want to install it and I want

00:37:14.210 --> 00:37:19.010
to see how I can use it and how I can adapt it.

00:37:19.260 --> 00:37:22.559
adapted to my workflow so yeah so we'll talk

00:37:22.559 --> 00:37:25.099
about it yeah this is i had a similar conversation

00:37:25.099 --> 00:37:27.840
with you uh recently where we went over all of

00:37:27.840 --> 00:37:30.760
your stuff yep so i'll mention that now that'll

00:37:30.760 --> 00:37:32.679
be coming out on my youtube channel maybe at

00:37:32.679 --> 00:37:35.599
the same time this one comes out um but yeah

00:37:35.599 --> 00:37:40.179
we talked a lot about sesh uh and tmux you know

00:37:40.179 --> 00:37:42.519
session managed strategies right this is really

00:37:42.519 --> 00:37:46.420
nerdy stuff i think most people come up with

00:37:46.420 --> 00:37:49.400
like hey i want to work session and I want a

00:37:49.400 --> 00:37:52.179
personal session and I want to, I don't know,

00:37:52.199 --> 00:37:54.780
maybe there's like a SSH. I need to connect to

00:37:54.780 --> 00:37:56.519
something and you create a separate session for

00:37:56.519 --> 00:37:59.940
that. And I found that that didn't work very

00:37:59.940 --> 00:38:04.760
well for me. I really like this idea of how about

00:38:04.760 --> 00:38:07.420
I just type what I want and it will create a

00:38:07.420 --> 00:38:10.760
session for me on my behalf. And generally I

00:38:10.760 --> 00:38:12.880
think of a session as a place on my computer.

00:38:13.360 --> 00:38:15.880
So it could be a project, it could be a dot file.

00:38:16.699 --> 00:38:19.519
More specifically, it could be an area of a project.

00:38:19.599 --> 00:38:25.340
So I really start to focus it down. And it's

00:38:25.340 --> 00:38:29.380
just built up by an FCF picker and a tool called

00:38:29.380 --> 00:38:33.739
Zoxide, which is able to track recency and frequency.

00:38:34.719 --> 00:38:40.000
And so you get a score. Frecency is what they

00:38:40.000 --> 00:38:42.579
call it, but someone told me that is not even

00:38:42.579 --> 00:38:44.860
a word. Someone got upset. It's a made -up word.

00:38:45.659 --> 00:38:49.539
So, frecency is cool. And so, you'll see I have

00:38:49.539 --> 00:38:51.400
some custom configurations, which we'll talk

00:38:51.400 --> 00:38:54.920
about these cogs. But then we have all of these

00:38:54.920 --> 00:38:59.239
and all of these little windows here. These are

00:38:59.239 --> 00:39:04.130
all just places on my computer that I use. I've

00:39:04.130 --> 00:39:06.349
been experimenting with the way to talk about

00:39:06.349 --> 00:39:08.949
Sesh more, but basically I don't use the CD command.

00:39:09.550 --> 00:39:11.750
If I want to CD into something, I'm going to

00:39:11.750 --> 00:39:17.610
use this instead. So my entry point is a Sesh

00:39:17.610 --> 00:39:20.989
start script, which lists these out as icons.

00:39:21.650 --> 00:39:24.489
And then I have a few bindings that I can use.

00:39:24.550 --> 00:39:27.010
I have a preview window. So Sesh has preview

00:39:27.010 --> 00:39:30.849
support. And yeah, so this is my entry point.

00:39:32.750 --> 00:39:38.369
I just hit S and a fish abbreviation will dump

00:39:38.369 --> 00:39:42.110
out sesh start. And let's just go to like NeoVim

00:39:42.110 --> 00:39:45.849
config. And so NeoVim config, you'll see it automatically

00:39:45.849 --> 00:39:49.309
opens up my file picker, which is telescope.

00:39:49.969 --> 00:39:53.510
And Avante happens to be the file that we looked

00:39:53.510 --> 00:39:56.769
at a few minutes ago. And so it sorts everything

00:39:56.769 --> 00:40:00.530
that you see here. It's sorted by most recently

00:40:00.530 --> 00:40:04.099
opened. And so that makes it really simple that

00:40:04.099 --> 00:40:05.599
I just said, oh, yeah, I want to go to Avanti.

00:40:05.639 --> 00:40:08.980
I hit enter. Right. And then I can repeat the

00:40:08.980 --> 00:40:10.699
process. So if I want to go to my dot files,

00:40:10.880 --> 00:40:15.860
I can do that. If I want to go to Sesh, you know,

00:40:15.900 --> 00:40:18.079
the source code, you'll see that the default

00:40:18.079 --> 00:40:22.300
is to always show my session picker. And the

00:40:22.300 --> 00:40:24.800
way that that works is that you have a configuration

00:40:24.800 --> 00:40:28.119
file that can set up that behavior. So I have

00:40:28.119 --> 00:40:31.059
this startup command for every session. That

00:40:31.059 --> 00:40:34.780
automatically opens nvim, and then this is a

00:40:34.780 --> 00:40:38.139
command called gotofile that opens up my telescope

00:40:38.139 --> 00:40:42.460
picker. There's this ignore dirs is interesting.

00:40:42.659 --> 00:40:46.219
You can have this be ignored. And a preview command

00:40:46.219 --> 00:40:49.559
is the default. So how do we show it? And you'll

00:40:49.559 --> 00:40:53.280
see here that if we go down and look at some

00:40:53.280 --> 00:40:56.579
of these, it just lists out. the files, you know,

00:40:56.579 --> 00:40:58.460
because this isn't a session yet. It's just a

00:40:58.460 --> 00:41:03.039
preview of a session that could be. And then

00:41:03.039 --> 00:41:05.920
you're able to generate your own configurations.

00:41:06.659 --> 00:41:10.599
So I like to talk about the tmux config is a

00:41:10.599 --> 00:41:12.480
good example. Can we see this? All right. Yeah.

00:41:12.559 --> 00:41:16.139
So you name it, you give it a path, you give

00:41:16.139 --> 00:41:18.000
it a startup command, and you give it a preview

00:41:18.000 --> 00:41:20.699
if you want. And so any of these you don't define

00:41:20.699 --> 00:41:23.179
work as a fallback, but basically a session is

00:41:23.179 --> 00:41:25.420
a place on your computer and then you can name

00:41:25.420 --> 00:41:28.579
the session. So if I say Teamworks config, we're

00:41:28.579 --> 00:41:31.800
going to see a preview of that file. And when

00:41:31.800 --> 00:41:33.739
I choose that session, it's going to automatically

00:41:33.739 --> 00:41:37.800
open up that file because that's what the command

00:41:37.800 --> 00:41:43.039
was. And so really great. I have another version

00:41:43.039 --> 00:41:44.880
of this that I like to use. I haven't talked

00:41:44.880 --> 00:41:47.360
about it much. This idea that I want to look

00:41:47.360 --> 00:41:51.940
at. a set of, in this case, lazy .envim plugins,

00:41:52.280 --> 00:41:54.440
right? They live in this place on my computer.

00:41:54.980 --> 00:41:57.599
And I have this sort of proxy command, which

00:41:57.599 --> 00:42:00.539
will connect to the one I select, but it will

00:42:00.539 --> 00:42:03.699
first list all of the plugins and preview their

00:42:03.699 --> 00:42:08.280
readme files. So if I go to lazy plugins, we'll

00:42:08.280 --> 00:42:11.280
see that I get an additional screen that shows

00:42:11.280 --> 00:42:16.619
me previews. And if I want to go to like Avante,

00:42:17.500 --> 00:42:21.880
And I hit enter, it now generates an Avante Tmux

00:42:21.880 --> 00:42:24.460
session. A session, okay, a Tmux session, okay.

00:42:24.639 --> 00:42:28.119
And then I can do the source code things. I can

00:42:28.119 --> 00:42:30.519
edit stuff in LazyGit and whatever I want to

00:42:30.519 --> 00:42:34.079
do. And then you'll also notice that the lazy

00:42:34.079 --> 00:42:37.900
plugin picker, it like goes away on its own.

00:42:39.400 --> 00:42:42.480
I call it a proxy session, which is a clever

00:42:42.480 --> 00:42:45.420
idea. I can do the same for Tmux plugins. I can

00:42:45.420 --> 00:42:47.940
say I want to look at my nerd font window name,

00:42:48.079 --> 00:42:52.139
which is the one I mentioned earlier that it

00:42:52.139 --> 00:42:56.539
swaps out my Tmux windows for emojis or nerd

00:42:56.539 --> 00:43:01.920
font symbols. And so, yeah. It looks pretty cool.

00:43:02.179 --> 00:43:06.349
It looks pretty nice, your font. And the style,

00:43:06.489 --> 00:43:08.929
everything in the terminal looks quite nice.

00:43:09.610 --> 00:43:12.949
And I might want to look at my CPU usage, right?

00:43:13.050 --> 00:43:14.969
So I could have a session for that that runs

00:43:14.969 --> 00:43:17.849
Mac top, which is just the current one that I'm

00:43:17.849 --> 00:43:21.369
using. And if I wanted to, you know, leave that

00:43:21.369 --> 00:43:24.309
one and, but leave it open, you know, it'll run.

00:43:24.530 --> 00:43:27.070
It's, you know, this, I think this is wattage.

00:43:27.070 --> 00:43:30.090
So electrical usage or whatever. You can track

00:43:30.090 --> 00:43:33.789
things over time. Have you tried B top? Yeah,

00:43:33.829 --> 00:43:36.900
I use B top too. One of the tops is here. The

00:43:36.900 --> 00:43:39.280
Mac top is just the one I like right now. Okay.

00:43:39.960 --> 00:43:42.480
And so you can imagine it could be anything,

00:43:42.579 --> 00:43:45.280
right? Yeah. Like when I SSH into my Steam Deck,

00:43:45.460 --> 00:43:48.780
then I can do this, and I don't know if it's

00:43:48.780 --> 00:43:51.880
going to work. Yeah, so it's not enabled right

00:43:51.880 --> 00:43:54.280
now, but if it was, then I'd have a session for

00:43:54.280 --> 00:43:58.280
an SSH session. Okay. So, yeah, lots of great

00:43:58.280 --> 00:44:02.039
ideas here. For me, it's all the stuff that I

00:44:02.039 --> 00:44:04.590
do the most, like... specific dot file things

00:44:04.590 --> 00:44:08.150
like fish config ghosty config i was using ghosty

00:44:08.150 --> 00:44:12.269
for a while if i want to go to my downloads right

00:44:12.269 --> 00:44:14.670
then it's going to open up this tool which is

00:44:14.670 --> 00:44:18.489
called yazi and i can just immediately start

00:44:18.489 --> 00:44:22.170
exploring the files um so yeah sesh has been

00:44:22.170 --> 00:44:24.690
really really great and how do you bring sesh

00:44:24.690 --> 00:44:27.989
up um do you have like a key map that you can

00:44:27.989 --> 00:44:30.659
use to bring it up Yeah, Command -K. I think

00:44:30.659 --> 00:44:32.420
we talked about it earlier, but Command -K is

00:44:32.420 --> 00:44:36.079
like an action key binding. Command -K works

00:44:36.079 --> 00:44:37.960
well in Discord too, right? If you're used to

00:44:37.960 --> 00:44:41.619
switching between things in Discord. So the muscle

00:44:41.619 --> 00:44:44.840
memory is the same everywhere. Interesting. And

00:44:44.840 --> 00:44:47.639
that's something I like a lot about. I do see

00:44:47.639 --> 00:44:50.179
the benefit. Because if I want to go to my downloads

00:44:50.179 --> 00:44:52.699
directory, for example, I just go to Finder.

00:44:52.820 --> 00:44:55.239
I don't go in the terminal. Just go in Finder.

00:44:55.420 --> 00:44:58.480
But doing this, I think it would make a lot of

00:44:58.480 --> 00:45:01.519
sense for me to go to a directory faster, even

00:45:01.519 --> 00:45:05.800
faster than doing it with Finder. So do you mind

00:45:05.800 --> 00:45:08.059
just... I don't know if it's going to work out

00:45:08.059 --> 00:45:10.920
on my setup on my computer or not, because I

00:45:10.920 --> 00:45:13.480
have a lot of custom stuff. But would you like

00:45:13.480 --> 00:45:16.159
to give it a try and see if I can install it

00:45:16.159 --> 00:45:18.019
and make it work? It should work. Yeah, it takes

00:45:18.019 --> 00:45:21.340
just a few minutes to set up. Yeah. Anything

00:45:21.340 --> 00:45:23.539
else you want to show before we move to my screen?

00:45:24.860 --> 00:45:27.679
What I will say is there's a lot of features

00:45:27.679 --> 00:45:29.719
that I haven't shown off. So like SESH main,

00:45:29.920 --> 00:45:34.480
I have command shift K set up so that if I want

00:45:34.480 --> 00:45:38.050
to. look at the current, actually, let's go back

00:45:38.050 --> 00:45:41.550
a step. I can kill Tmux pretty easily. So now

00:45:41.550 --> 00:45:44.710
nothing's running and I can restart. And if I

00:45:44.710 --> 00:45:48.269
wanted to say, let's open up sesh main, you'll

00:45:48.269 --> 00:45:51.190
see that the session is called sesh slash main.

00:45:51.449 --> 00:45:54.630
And that's because sesh is really smart at determining

00:45:54.630 --> 00:45:59.789
what the configuration should be. So as an example

00:45:59.789 --> 00:46:04.059
of dot files, You know, there's lots of folders

00:46:04.059 --> 00:46:08.719
in my .files repo, right? tmux, sesh, westerm.

00:46:08.960 --> 00:46:11.699
Let's go to the westerm one. If I was to choose

00:46:11.699 --> 00:46:16.059
this as a session, it will take the git path

00:46:16.059 --> 00:46:18.980
and it will create a path that's valid based

00:46:18.980 --> 00:46:23.159
off of the git repo. So .files is the repo, config

00:46:23.159 --> 00:46:25.579
is the folder, and then westerm is the subfolder,

00:46:25.619 --> 00:46:28.480
right? And so sesh is really good at doing that.

00:46:28.619 --> 00:46:32.739
So if I want to do different things in, Let's

00:46:32.739 --> 00:46:35.639
try that again, Fish. If I wanted to have multiple

00:46:35.639 --> 00:46:38.239
different sessions open at the same time under

00:46:38.239 --> 00:46:41.719
the same repo, it's a little bit easier for me

00:46:41.719 --> 00:46:45.860
to grasp and to get around. And it's cheap, right?

00:46:45.940 --> 00:46:47.639
So I can just say, okay, I don't need that anymore.

00:46:47.780 --> 00:46:49.619
And I have a binding that lets me kill sessions.

00:46:50.480 --> 00:46:53.780
Okay. Or I can just close the final window and

00:46:53.780 --> 00:46:57.239
I have a setting enabled that says, tells Tmux

00:46:57.239 --> 00:47:00.340
don't detach, just, you know, attach to another

00:47:00.340 --> 00:47:04.170
session. If there's more than one left. And so

00:47:04.170 --> 00:47:07.489
that's been such a huge thing for me to be able

00:47:07.489 --> 00:47:10.130
to like, say, I want to be in the Zoxide and

00:47:10.130 --> 00:47:13.670
I want to list something. And then in the CLI,

00:47:13.670 --> 00:47:16.949
I want to list something as well. Now I have

00:47:16.949 --> 00:47:20.510
two different sessions, the CLI session and the

00:47:20.510 --> 00:47:23.690
Zoxide CLI session. And I can a little bit more

00:47:23.690 --> 00:47:28.219
structured and easy. easily like work my way

00:47:28.219 --> 00:47:31.099
around my file system without attempting to go

00:47:31.099 --> 00:47:33.699
through like i don't know it could be like five

00:47:33.699 --> 00:47:37.139
or ten neovin buffers yeah and so it's a different

00:47:37.139 --> 00:47:40.019
flavor but i have found that i don't have to

00:47:40.019 --> 00:47:42.760
think about it very much when i could just get

00:47:42.760 --> 00:47:45.260
to what i want very quickly yeah i i like that

00:47:45.260 --> 00:47:48.440
i like that how do you let's say that i record

00:47:48.440 --> 00:47:52.139
a video right and um i need to move in from where

00:47:52.139 --> 00:47:54.699
it's going to be in the directory that it's going

00:47:54.699 --> 00:47:57.250
to be to a different directory do you do that

00:47:57.250 --> 00:48:00.889
in the terminal or you use finder um it depends

00:48:00.889 --> 00:48:03.610
i think i use finder plenty for just drag and

00:48:03.610 --> 00:48:06.889
drop and i have a lot of things in my sidebar

00:48:06.889 --> 00:48:09.449
in finder that just are quick places for me to

00:48:09.449 --> 00:48:13.309
drop things okay okay so this is more for config

00:48:13.309 --> 00:48:17.289
files and code right config files and code yeah

00:48:17.289 --> 00:48:20.769
okay wonderful all right let's give it a try

00:48:20.769 --> 00:48:24.010
then i'm ready i'm gonna switch to my screen

00:48:25.130 --> 00:48:26.929
I'm ready when you're ready for the installation

00:48:26.929 --> 00:48:30.349
then. Yeah, so you have brew. So all you have

00:48:30.349 --> 00:48:32.730
to do is say brew install sesh. Oh, just like

00:48:32.730 --> 00:48:38.809
that? Yep. And let me quit out of here. Brew

00:48:38.809 --> 00:48:43.949
install sesh. That's it. So if you don't already

00:48:43.949 --> 00:48:46.530
have Zoxide or Tmux, it will also install those

00:48:46.530 --> 00:48:48.670
just because they're dependencies on the project.

00:48:49.289 --> 00:48:53.000
Oh, interesting. Okay. I think I have both. I'm

00:48:53.000 --> 00:48:55.460
not sure. Yeah. Well, you have T -Max for sure.

00:48:55.820 --> 00:49:00.360
Yeah. And so now it's just a level of how do

00:49:00.360 --> 00:49:02.639
you want to configure it? So if you want to do

00:49:02.639 --> 00:49:08.360
sesh list. Space like this? Yep. It's just a

00:49:08.360 --> 00:49:12.639
command. Yep. That's your basics. So the top

00:49:12.639 --> 00:49:15.539
elements, the first two are going to be those

00:49:15.539 --> 00:49:19.219
sessions. If you want to repeat the command and

00:49:19.219 --> 00:49:23.300
do dash I. uh specialist dash i you get icons

00:49:23.300 --> 00:49:27.559
so the first two are your team accessions and

00:49:27.559 --> 00:49:32.440
all the ones below are yours oxide results and

00:49:32.440 --> 00:49:35.119
where did this where did it get the icons from

00:49:35.119 --> 00:49:39.019
from the this is nerd font yeah it's a nerd font

00:49:39.019 --> 00:49:41.840
go get access just knows like hey these are what

00:49:41.840 --> 00:49:45.780
the sources are okay right and so interesting

00:49:45.780 --> 00:49:50.030
do you use raycast yep i do use raycast so there

00:49:50.030 --> 00:49:53.989
is if you go to pop -up raycast let me bring

00:49:53.989 --> 00:49:57.630
it over to this screen sure and just search store

00:49:57.630 --> 00:50:01.510
okay in the settings right no just right here

00:50:01.510 --> 00:50:05.550
store okay and go to that and then just type

00:50:05.550 --> 00:50:09.750
sesh so it's kind of fun you can use sesh as

00:50:09.750 --> 00:50:12.769
well in raycast so if you want to do this somehow

00:50:12.769 --> 00:50:16.829
globally you can But this is on offer if you

00:50:16.829 --> 00:50:20.389
want to install this. Oh, okay. So it already

00:50:20.389 --> 00:50:23.190
installed it, right? So I bring it up. I didn't

00:50:23.190 --> 00:50:25.550
show it up, but yep, connect. So if you hit enter,

00:50:25.670 --> 00:50:28.469
it's probably going to ask you what your terminal

00:50:28.469 --> 00:50:30.530
emulator is. So you have to select it for the

00:50:30.530 --> 00:50:35.949
first time. Okay. You can type it out. Go see.

00:50:36.630 --> 00:50:40.110
Okay. Continue. All right. And so there you go.

00:50:40.190 --> 00:50:42.590
So this also works out of the box without any

00:50:42.590 --> 00:50:44.730
really crazy configurations. You can switch.

00:50:44.989 --> 00:50:50.369
So you can type like .files, hit enter. .files

00:50:50.369 --> 00:50:54.090
latest, this one. Sure. I just hit enter there

00:50:54.090 --> 00:50:56.130
and it's going to create a session? It'll create

00:50:56.130 --> 00:51:00.510
a session. Okay. Okay. I already had a session,

00:51:00.710 --> 00:51:03.929
I think. But yours was J. So if you go back to

00:51:03.929 --> 00:51:07.610
Raycast and look at the pop -up. I see. I see.

00:51:08.339 --> 00:51:10.920
So you could set up that to a key binding if

00:51:10.920 --> 00:51:15.679
you wanted. But what I'd recommend is this switcher

00:51:15.679 --> 00:51:17.699
that you have right now, you can swap out for

00:51:17.699 --> 00:51:23.860
the configuration from the Sesh Readme has a

00:51:23.860 --> 00:51:26.579
good example. Okay. So if you want to copy that

00:51:26.579 --> 00:51:30.639
and bring it in, you can. Let me go there. I

00:51:30.639 --> 00:51:32.239
think in the near future, we're going to have

00:51:32.239 --> 00:51:35.440
some sort of playground where we can show off

00:51:35.440 --> 00:51:38.480
people's different... ways of configuring, but

00:51:38.480 --> 00:51:40.719
I have some reasonable defaults here with FCF.

00:51:41.280 --> 00:51:44.099
Okay. So Brew's installed, Sesh is installed.

00:51:44.639 --> 00:51:48.039
If you scroll down, you'll see some basic usage.

00:51:48.380 --> 00:51:51.500
So that would be your most basic usage. You see

00:51:51.500 --> 00:51:53.179
that example there, you want to Sesh connect.

00:51:53.719 --> 00:51:56.280
But before you Sesh connect, you want to list

00:51:56.280 --> 00:51:59.699
and FCF that list so that you can choose from

00:51:59.699 --> 00:52:02.719
it. So if you want, you can try that. This is

00:52:02.719 --> 00:52:07.800
your sort of entry point into Yeah, there you

00:52:07.800 --> 00:52:11.619
go. Okay, this, okay. So now you would just type

00:52:11.619 --> 00:52:13.960
what you want to type and it would, when you

00:52:13.960 --> 00:52:16.519
hit enter, it's going to connect to that session.

00:52:16.519 --> 00:52:23.760
Okay, let's see if I go to this. It creates a

00:52:23.760 --> 00:52:27.900
session. Okay, great. I don't have to keep track

00:52:27.900 --> 00:52:32.320
of all the different directories that I want

00:52:32.320 --> 00:52:35.820
to create sessions for. What does it search like?

00:52:36.780 --> 00:52:40.940
If I run this, what is it going, like, is it

00:52:40.940 --> 00:52:43.360
going to start at the root directory and I can

00:52:43.360 --> 00:52:48.199
type basically anything? So it will only list

00:52:48.199 --> 00:52:52.079
Zoxide results. Oh. So whatever you put in Zoxide,

00:52:52.139 --> 00:52:55.199
it shows. And it does a little bit of human readable

00:52:55.199 --> 00:52:57.800
things. So if you hit enter on this command,

00:52:58.059 --> 00:53:00.260
it takes everything from your home directory

00:53:00.260 --> 00:53:03.079
and it substituted for that curly brace so that

00:53:03.079 --> 00:53:04.960
you know, okay, this is home directory stuff.

00:53:05.840 --> 00:53:09.659
It makes it easy to read. But yeah, anything

00:53:09.659 --> 00:53:11.800
that you've ever, if you know how Zoxide works,

00:53:11.980 --> 00:53:17.380
anytime you cd into a directory, Zoxide will

00:53:17.380 --> 00:53:21.179
add that entry or increase its score. So if there's

00:53:21.179 --> 00:53:22.920
something that's not showing up in this list

00:53:22.920 --> 00:53:24.840
and you want it, you just Zoxide add and you

00:53:24.840 --> 00:53:28.219
add the thing. And then it shows that. And every

00:53:28.219 --> 00:53:31.099
time you ever select this option, so if you were

00:53:31.099 --> 00:53:34.369
to choose OBS script again, Zoxide will automatically

00:53:34.369 --> 00:53:38.949
increase the score. Okay. So as you use Sesh,

00:53:39.150 --> 00:53:42.989
yeah, it still knows where it's located and it

00:53:42.989 --> 00:53:46.010
still increases the Zoxide score. Okay. And it

00:53:46.010 --> 00:53:48.110
just switches to that session if everything exists?

00:53:48.469 --> 00:53:50.730
It switches if it's already there. Yep. Okay.

00:53:51.030 --> 00:53:53.989
Interesting. So it creates sessions or it switches

00:53:53.989 --> 00:53:57.159
to sessions. Okay. What should I do next then?

00:53:57.239 --> 00:53:59.260
What did you say that there was in the readme?

00:53:59.300 --> 00:54:02.099
Yeah, so this is the next one. You can combine

00:54:02.099 --> 00:54:04.900
TMUX and FCF. If you want, you can copy this

00:54:04.900 --> 00:54:09.659
whole thing. Okay. And this will be bound to

00:54:09.659 --> 00:54:12.900
capital T. Capital T, okay. Just go to my TMUX

00:54:12.900 --> 00:54:15.860
config file. And then edit your TMUX config file.

00:54:17.500 --> 00:54:20.099
Okay, here is the file. And you'll just have

00:54:20.099 --> 00:54:22.380
to put this somewhere. If you have other bindings,

00:54:22.400 --> 00:54:25.030
you could put them near there. let me see if

00:54:25.030 --> 00:54:27.429
i have i don't think i have capital t i don't

00:54:27.429 --> 00:54:30.050
think i'm using capital t it's not a reserved

00:54:30.050 --> 00:54:33.070
one so it shouldn't unless you've explicitly

00:54:33.070 --> 00:54:36.710
set that before yeah and so you can see a little

00:54:36.710 --> 00:54:38.710
bit more going on here so we're listing with

00:54:38.710 --> 00:54:45.530
icons the pop -up is 70 80 by 70 percent we disable

00:54:45.530 --> 00:54:48.750
the sorting from fcf because we don't want fcf

00:54:48.750 --> 00:54:52.940
to sort we want to use sessions sorted output,

00:54:53.340 --> 00:54:57.000
you know, directly. ANSI is something I use to

00:54:57.000 --> 00:55:00.280
prevent, to do color. So that may or may not

00:55:00.280 --> 00:55:02.619
be helpful to you. And then the rest of it is

00:55:02.619 --> 00:55:06.239
just helpful bindings. So you can play around

00:55:06.239 --> 00:55:09.980
with those if you want. Okay. The preview window

00:55:09.980 --> 00:55:12.920
as well has been set up. And so this should just

00:55:12.920 --> 00:55:15.480
work. It should just, you know, you have to restart

00:55:15.480 --> 00:55:18.699
your Tmux config. Let me just reload it. Yep.

00:55:18.780 --> 00:55:21.119
Yeah, you can source it and then. And then give

00:55:21.119 --> 00:55:25.659
it a prefix capital T. Okay. And so now you can

00:55:25.659 --> 00:55:27.280
switch between your projects with that binding.

00:55:27.719 --> 00:55:30.280
Or you can set up your own binding. Or in my

00:55:30.280 --> 00:55:33.719
case, I bound my Mac OS binding to interpret

00:55:33.719 --> 00:55:38.539
prefix capital T. So I hit command K and it does

00:55:38.539 --> 00:55:43.199
the same thing. Interesting. So these are sessions.

00:55:43.340 --> 00:55:45.760
I know that these are existing sessions because

00:55:45.760 --> 00:55:49.619
of the icon, right? Yep. okay so that's what

00:55:49.619 --> 00:55:52.739
tells you okay these are existing sessions how

00:55:52.739 --> 00:55:56.099
can i kill one of these from here control d is

00:55:56.099 --> 00:55:59.260
the binding i have set up control d let me see

00:55:59.260 --> 00:56:03.619
if i try to kill this one control d okay nice

00:56:03.619 --> 00:56:06.039
and if you want to list only the team accessions

00:56:06.039 --> 00:56:09.800
you can do control t control t oh if you want

00:56:09.800 --> 00:56:12.800
to do only these oxide results it's control x

00:56:12.800 --> 00:56:18.019
control x okay And then back to all is control

00:56:18.019 --> 00:56:22.440
A. Control A. And I don't use these very much.

00:56:22.500 --> 00:56:24.659
I tend to just use this window as you see it.

00:56:24.840 --> 00:56:26.940
But there's an interesting option for people

00:56:26.940 --> 00:56:30.440
that want to explore their, you know, what's

00:56:30.440 --> 00:56:34.079
available to them a little bit more. Okay. Okay.

00:56:34.400 --> 00:56:36.599
Let's say that I want to create a session for,

00:56:36.900 --> 00:56:43.920
where can I go? That is not dangerous. Let me

00:56:43.920 --> 00:56:47.400
go to the. the scene switcher again you'll notice

00:56:47.400 --> 00:56:52.139
all you had to type was sc and it it matched

00:56:52.139 --> 00:56:54.239
within two letters that matched to the thing

00:56:54.239 --> 00:56:58.219
that you most recently used right okay nice so

00:56:58.219 --> 00:57:01.320
it makes it so that you don't have to type very

00:57:01.320 --> 00:57:05.139
much to get where you want to very quickly interesting

00:57:05.139 --> 00:57:07.719
that seems really useful because the way that

00:57:07.719 --> 00:57:12.059
i do it right now as of today is i need to have

00:57:12.059 --> 00:57:15.670
some pre -configured paths right so if i type

00:57:15.670 --> 00:57:19.630
right hyper tn i think it is but but these i

00:57:19.630 --> 00:57:23.070
have to specifically configure these paths right

00:57:23.070 --> 00:57:28.050
so it's not as as efficient you know because

00:57:28.050 --> 00:57:32.949
i want to go somewhere to some other directories

00:57:32.949 --> 00:57:35.750
you know different times not only to these so

00:57:35.750 --> 00:57:39.590
well and i'll show you the power of this tooling

00:57:39.590 --> 00:57:45.179
is the the custom configs So you'll need to go

00:57:45.179 --> 00:57:49.400
to your .config folder. Okay, let me go there.

00:57:51.380 --> 00:57:55.679
Okay. And then you'll just, you'll probably end

00:57:55.679 --> 00:57:57.639
up symbolically linking this so that it's in

00:57:57.639 --> 00:57:59.920
your .files, but for the sake of today, just

00:57:59.920 --> 00:58:05.460
make a directory called sesh. Okay. Sesh, just

00:58:05.460 --> 00:58:10.440
like this, right? Mm -hmm. Okay. And then, yeah.

00:58:12.139 --> 00:58:14.139
Yeah, you can switch to it now that it's there.

00:58:14.239 --> 00:58:16.340
Yep, and now you could do, I'll show you a new

00:58:16.340 --> 00:58:20.099
one, do sesh connect, and then there's an argument

00:58:20.099 --> 00:58:22.480
for a period. Are you familiar with this in the

00:58:22.480 --> 00:58:25.900
command line? So space and then period. Just

00:58:25.900 --> 00:58:29.159
period? Yeah, so that is representing the current

00:58:29.159 --> 00:58:31.159
directory. Oh, this directory. Okay, yep. And

00:58:31.159 --> 00:58:33.199
so if you hit enter, it'll create a session based

00:58:33.199 --> 00:58:35.920
off of the folder that you're in. And look at

00:58:35.920 --> 00:58:40.239
that. Oh. So that's another helpful. you know,

00:58:40.280 --> 00:58:43.059
feature of Sesh. I can keep that as a session

00:58:43.059 --> 00:58:46.380
there and go back to it when I want it, right?

00:58:46.460 --> 00:58:48.739
And I can just bring Sesh. You said it's, this

00:58:48.739 --> 00:58:51.400
is not working for me. Well, this is not Sesh.

00:58:51.559 --> 00:58:55.019
This is the Tmux. Do you know how to map this

00:58:55.019 --> 00:58:57.000
in Ghosty? Because you mentioned that you use

00:58:57.000 --> 00:58:59.820
control K, right? Have you used Ghosty? Yeah,

00:58:59.820 --> 00:59:02.179
I can give you some tips on how to do it in Ghosty.

00:59:02.559 --> 00:59:07.269
I want to try and see if command. K works. That's

00:59:07.269 --> 00:59:08.789
the one that you used. You mentioned, right?

00:59:08.849 --> 00:59:13.030
Command K. Yep. Let's see if we can make it work.

00:59:14.690 --> 00:59:19.289
Yeah. So you can add a new key bind. Yeah. Add

00:59:19.289 --> 00:59:23.610
a new key bind. I don't think I have any. There

00:59:23.610 --> 00:59:29.110
you go. You got one. It'll equal super. Yep.

00:59:29.170 --> 00:59:33.929
So it'll be super plus K. Okay. And it'll enter

00:59:33.929 --> 00:59:38.940
text. So T -E -X -T colon. And then we're just

00:59:38.940 --> 00:59:43.300
going to dump a hex code. Okay. So what is your

00:59:43.300 --> 00:59:47.820
prefix bound to? It's the default one. Okay,

00:59:47.820 --> 00:59:52.000
great. Control B. So swap the period out for

00:59:52.000 --> 00:59:54.500
a colon. Kind of like you see how inspector.

00:59:54.719 --> 00:59:58.039
There you go. Not semicolon, but colon. And then

00:59:58.039 --> 01:00:02.199
you'll do backslash. That's forward slash. So

01:00:02.199 --> 01:00:04.840
try the other one. There you go. And then X02

01:00:04.840 --> 01:00:11.420
is a hex code for 02, sorry. That's the hex code

01:00:11.420 --> 01:00:14.139
for prefix B. And then you'll do forward slash

01:00:14.139 --> 01:00:21.960
again, or backslash, sorry, for X4C is the one

01:00:21.960 --> 01:00:24.840
you want. So give that a save and give command

01:00:24.840 --> 01:00:27.500
K a try. Okay, I already saved. I don't know

01:00:27.500 --> 01:00:30.059
if I need to restart ghosting. Let's see. I don't

01:00:30.059 --> 01:00:35.090
know. No, command K, it's not working. No. I

01:00:35.090 --> 01:00:38.269
don't know if my prefix, hold on. Oh, it's try

01:00:38.269 --> 01:00:45.289
B, not C. My bad. X4, B. B, okay. Yeah. Let's

01:00:45.289 --> 01:00:48.090
see. I think ghosty does have to reload its config.

01:00:48.510 --> 01:00:54.590
I don't know how to reload. Super R? No, but

01:00:54.590 --> 01:00:57.510
I think I have a different prefix. Hold on. If

01:00:57.510 --> 01:01:00.210
your prefix is different, it won't work. Yeah,

01:01:00.250 --> 01:01:03.260
you have to bind it to the prefix. No. Control

01:01:03.260 --> 01:01:08.019
B. Control B. Yep. Did I mistype something maybe?

01:01:08.860 --> 01:01:12.940
X02, X4, B. Let me quit out of ghosty and try

01:01:12.940 --> 01:01:19.840
it again, okay? Just to make sure. So, command

01:01:19.840 --> 01:01:24.000
K. Do I have it mapped already? Okay, what do

01:01:24.000 --> 01:01:27.159
I have on command K? I don't remember if I had

01:01:27.159 --> 01:01:30.920
to overwrite it. And I can... troubleshoot with

01:01:30.920 --> 01:01:33.199
you after this yeah that's not relevant right

01:01:33.199 --> 01:01:36.000
now at least i know how to bring it up and it

01:01:36.000 --> 01:01:39.059
i i do see the benefit yeah and i have a video

01:01:39.059 --> 01:01:42.940
on how you can get the hex codes there so that

01:01:42.940 --> 01:01:46.280
the x02 x4b how did i get that i have a whole

01:01:46.280 --> 01:01:49.139
youtube video on how that works it's called mac

01:01:49.139 --> 01:01:52.000
os key bindings for tmux or something like that

01:01:52.000 --> 01:01:57.219
which yeah that first one there this one so that

01:01:57.219 --> 01:01:59.960
whole video shows you how it works And basically

01:01:59.960 --> 01:02:03.400
you just translate that to text, you know, text

01:02:03.400 --> 01:02:06.980
colon, and then you dump the hex code in. Okay.

01:02:07.119 --> 01:02:09.840
Okay. Wonderful. And so I was able to get most

01:02:09.840 --> 01:02:12.119
of the features I wanted working with Ghosty

01:02:12.119 --> 01:02:16.739
when I experimented with it. Okay. What did you

01:02:16.739 --> 01:02:20.420
know away from Ghosty, by the way? They don't

01:02:20.420 --> 01:02:23.179
offer that background image feature yet, which

01:02:23.179 --> 01:02:25.059
I think is really interesting and helpful for

01:02:25.059 --> 01:02:28.699
me. Okay. And I don't like that it's a static.

01:02:29.119 --> 01:02:31.099
config file right it's like kind of like shell

01:02:31.099 --> 01:02:34.619
i guess similar i like lua i like the dynamic

01:02:34.619 --> 01:02:38.420
ability to you know program things and repeat

01:02:38.420 --> 01:02:41.619
some of my features and logic and things using

01:02:41.619 --> 01:02:44.280
a programming language so i really enjoy that

01:02:44.280 --> 01:02:49.059
okay wonderful what else should i check on um

01:02:49.059 --> 01:02:52.769
what else should i So there's a ton of features,

01:02:52.869 --> 01:02:54.730
but I think the real power of Sesh comes from

01:02:54.730 --> 01:02:57.710
custom configurations. So things like I want

01:02:57.710 --> 01:03:00.469
to edit my Tmux config file. Well, you don't

01:03:00.469 --> 01:03:03.269
need to open up .files and then find the Tmux

01:03:03.269 --> 01:03:05.730
file and then go to it. You can just have a custom

01:03:05.730 --> 01:03:09.869
config that sends you directly to that file with

01:03:09.869 --> 01:03:14.570
the Sesh picker. So that's where the Sesh config

01:03:14.570 --> 01:03:18.550
file can be really helpful in configuring stuff

01:03:18.550 --> 01:03:23.699
like that. Okay. If I bring it up, it's capital

01:03:23.699 --> 01:03:30.639
T, okay? And if I type tmux... So you won't have

01:03:30.639 --> 01:03:32.480
any matches, right? Because you've never been

01:03:32.480 --> 01:03:35.000
to a tmux folder or anything like that. But it

01:03:35.000 --> 01:03:38.360
will be in your .files, right? Yeah. But you'll

01:03:38.360 --> 01:03:41.360
need to create a custom config. So you can go

01:03:41.360 --> 01:03:47.480
back to sesh and you can switch to the sesh session.

01:03:47.699 --> 01:03:50.840
Now we're getting meta. you have another session

01:03:50.840 --> 01:03:54.460
called sesh okay okay so the session that i had

01:03:54.460 --> 01:03:57.599
okay hold on let me bring it here okay this one

01:03:57.599 --> 01:04:02.940
yeah and you'll touch a sesh .toml file okay

01:04:02.940 --> 01:04:06.619
can i do it right you can invent yep okay however

01:04:06.619 --> 01:04:14.739
you make files sesh .toml great and so now to

01:04:14.739 --> 01:04:19.360
define a new session you use um double angle

01:04:19.360 --> 01:04:21.420
brackets and you're welcome to go back to the

01:04:21.420 --> 01:04:25.039
the readme readme if you scroll down access session

01:04:25.039 --> 01:04:27.079
configurations there's a couple of good options

01:04:27.079 --> 01:04:32.059
okay let me know where that is yep it's in the

01:04:32.059 --> 01:04:36.300
config section okay so default i talked to you

01:04:36.300 --> 01:04:39.639
about where i can You know, run a command on

01:04:39.639 --> 01:04:42.239
any session. I don't want to run the shell. I

01:04:42.239 --> 01:04:45.360
want to like open Vim and call telescope or something.

01:04:45.519 --> 01:04:49.239
Oh, okay. But the Tmex config example is there.

01:04:49.480 --> 01:04:53.019
Oh, okay. Okay. So I can grab the entire thing,

01:04:53.079 --> 01:04:55.380
right? Sure. Yeah. Yeah. There's a couple options

01:04:55.380 --> 01:04:59.280
here. Okay. So downloads is fairly obvious. And

01:04:59.280 --> 01:05:02.079
then the Tmex config, mine, you're going to want

01:05:02.079 --> 01:05:05.760
to change line eight to whatever yours is. You

01:05:05.760 --> 01:05:08.860
could just drop C slash dot files if you wanted.

01:05:09.760 --> 01:05:12.059
Or if you have your dot file path, you could

01:05:12.059 --> 01:05:15.840
fill that out. Which is the entire path, right?

01:05:16.900 --> 01:05:21.320
To the directory. So you want go C swapped out

01:05:21.320 --> 01:05:24.019
with tmux. Hold on. Yeah, I didn't go to the

01:05:24.019 --> 01:05:25.920
right one. Where is tmux? Well, and remember,

01:05:26.039 --> 01:05:29.760
we haven't mapped it. Your tmux. Yeah, there

01:05:29.760 --> 01:05:32.099
you go. So you don't want the file because the

01:05:32.099 --> 01:05:34.699
path is just the directory. And then it looks

01:05:34.699 --> 01:05:37.559
like you have a .sh on your tmux -conf file,

01:05:37.739 --> 01:05:41.199
so you'll have to add that below. So on the startup

01:05:41.199 --> 01:05:43.900
command, you have to say, I want to nvm tmux

01:05:43.900 --> 01:05:47.000
-conf .sh, right? Okay, okay, okay. Do I leave

01:05:47.000 --> 01:05:50.239
this forward slash here? It doesn't matter. Sesh

01:05:50.239 --> 01:05:54.480
can handle either. Is that the way that I have

01:05:54.480 --> 01:05:58.699
it? Let me see. tmux -conf .sh. The only reason

01:05:58.699 --> 01:06:01.840
I did that .sh is for syntax highlighting. I

01:06:01.840 --> 01:06:05.639
think. I don't remember. Yeah, I've got a tip

01:06:05.639 --> 01:06:09.079
I can send you later that you can write auto

01:06:09.079 --> 01:06:12.739
command to auto do that. But anyway, do you have

01:06:12.739 --> 01:06:15.619
bat? Is the bat something that you use? Yeah,

01:06:15.619 --> 01:06:18.019
I think I have an alternative. I think I have

01:06:18.019 --> 01:06:23.179
it installed. So now if you open up the sesh

01:06:23.179 --> 01:06:28.699
picker and you type tmux. Okay, let's see. You're

01:06:28.699 --> 01:06:31.079
going to get a custom config there. Okay. And

01:06:31.079 --> 01:06:35.860
if you hit enter. It's going to open up your

01:06:35.860 --> 01:06:39.460
TMX config file. Interesting. That is really

01:06:39.460 --> 01:06:44.639
useful. It's using like a different theme, you

01:06:44.639 --> 01:06:47.000
know? Oh, you got some theming problems. Yeah,

01:06:47.039 --> 01:06:49.699
so it's not perfect. Everybody's setup's a little

01:06:49.699 --> 01:06:53.699
different. Your Z shell that has to wait and

01:06:53.699 --> 01:06:56.260
pull before it can execute, there may be something

01:06:56.260 --> 01:07:00.000
to that that is a little bit funky. Okay. I may

01:07:00.000 --> 01:07:02.739
need to look into that. Yeah, we can take a look

01:07:02.739 --> 01:07:05.960
at that later. That's fine. We've been here for

01:07:05.960 --> 01:07:09.400
over an hour. So I know you have stuff to do.

01:07:09.619 --> 01:07:12.460
Is there anything else you want to share or something

01:07:12.460 --> 01:07:15.360
that people should look into or that I should

01:07:15.360 --> 01:07:18.639
look into before we wrap it up? You know, there's

01:07:18.639 --> 01:07:20.320
a whole lot of features in Sesh we didn't talk

01:07:20.320 --> 01:07:24.159
about. You can clone repos to a specific place

01:07:24.159 --> 01:07:26.280
and automatically create a session all in one

01:07:26.280 --> 01:07:30.440
step, which is really nice. I made a fix to the

01:07:30.440 --> 01:07:33.940
last command that's built into Tmux. I made an

01:07:33.940 --> 01:07:37.099
improvement on that feature by creating a sesh

01:07:37.099 --> 01:07:38.860
last command, which we didn't get to cover either.

01:07:40.639 --> 01:07:45.500
There's also a whole lot of really good configuration

01:07:45.500 --> 01:07:50.019
styles. Some of them we talked about today. But

01:07:50.019 --> 01:07:51.860
yeah, I would encourage people, go give it a

01:07:51.860 --> 01:07:54.760
star. It only takes... a few minutes to get going

01:07:54.760 --> 01:07:57.099
i mean with me and you it took maybe less than

01:07:57.099 --> 01:07:58.820
two minutes and you had it installed and you

01:07:58.820 --> 01:08:01.440
could use it now configuring it and making it

01:08:01.440 --> 01:08:03.639
work for your specific needs will take a little

01:08:03.639 --> 01:08:05.699
bit more time but actually getting off the ground

01:08:05.699 --> 01:08:09.940
running is almost immediate so find a good binding

01:08:09.940 --> 01:08:13.800
start learning the muscle memory and don't do

01:08:13.800 --> 01:08:16.840
custom you know tmx sessions anymore just let

01:08:16.840 --> 01:08:20.350
sesh handle everything for you and learn that

01:08:20.350 --> 01:08:23.069
the least amount of keys needed typically get

01:08:23.069 --> 01:08:25.689
you to what you need because of that freesense

01:08:25.689 --> 01:08:29.890
algorithm. So as you get used to it and as you

01:08:29.890 --> 01:08:32.430
configure it to your needs, you'll find that

01:08:32.430 --> 01:08:34.050
you don't really have to think about session

01:08:34.050 --> 01:08:35.989
switching much anymore. You just type what you

01:08:35.989 --> 01:08:38.649
need quickly, hit enter, and you're where you

01:08:38.649 --> 01:08:43.609
need to be. And so, yeah, it's a great tool.

01:08:44.109 --> 01:08:46.550
Everyone that has used it so far has said nice

01:08:46.550 --> 01:08:49.319
things about it. There's been a few weird edge

01:08:49.319 --> 01:08:52.899
cases. And so I'm active on GitHub and doing

01:08:52.899 --> 01:08:57.260
my best to fix anything that comes up. And there'll

01:08:57.260 --> 01:08:59.619
be some more features coming. So yeah, thanks

01:08:59.619 --> 01:09:02.800
for trying this out. And I hope it works well

01:09:02.800 --> 01:09:06.399
for you. Yeah, thank you very much for coming

01:09:06.399 --> 01:09:09.079
over, Josh. Hold on, give me a minute. Sorry,

01:09:09.260 --> 01:09:12.579
so my wife decided to use the printer. right

01:09:12.579 --> 01:09:15.500
now she prints from the first floor i'm on the

01:09:15.500 --> 01:09:18.659
second floor and it started making a lot of noise

01:09:18.659 --> 01:09:25.300
okay so yeah so um maybe let's see how people

01:09:25.300 --> 01:09:27.800
react to the to the video and if you have time

01:09:27.800 --> 01:09:30.279
another day we can do like a part two or something

01:09:30.279 --> 01:09:33.739
we'll see what people say in the comments just

01:09:33.739 --> 01:09:37.220
remember guys go and give this a star the repo

01:09:37.220 --> 01:09:40.979
and most importantly make sure to go and subscribe

01:09:40.979 --> 01:09:44.729
to josh's youtube channel great thanks for having

01:09:44.729 --> 01:09:50.029
me yeah any final words no just this i was this

01:09:50.029 --> 01:09:52.170
was fun i could talk a lot more about this stuff

01:09:52.170 --> 01:09:54.810
i'm sure i will and i'm sure we'll keep in touch

01:09:54.810 --> 01:09:58.210
so yeah it was fun all right thank you very much

01:09:58.210 --> 01:10:01.609
josh we'll see you another day bye