WEBVTT 00:00:00.000 --> 00:00:03.759 in gh - you define sections in a yaml file and 00:00:03.759 --> 00:00:06.820 you can specify like this section is specifically 00:00:06.820 --> 00:00:10.220 for gh - and i can easily see like which prs 00:00:10.220 --> 00:00:14.439 are waiting for my review i have a question does 00:00:14.439 --> 00:00:19.280 this replace lasik it or does it add to lasik 00:00:19.280 --> 00:00:23.640 it i'm i'm confused there i honestly don't want 00:00:23.640 --> 00:00:26.460 to go the next down the next rabbit hole how 00:00:26.460 --> 00:00:29.920 has that been Yeah, I can totally get it, but 00:00:29.920 --> 00:00:34.020 it's not an immediate benefit like moving to 00:00:34.020 --> 00:00:36.679 Neovim. I think it's more like if you're interested 00:00:36.679 --> 00:00:40.280 in the technology, and this is the readme for 00:00:40.280 --> 00:00:43.520 my .files, and you can see images render just 00:00:43.520 --> 00:00:49.079 fine. If I want to look at repos that are interesting 00:00:49.079 --> 00:00:51.460 to me, I don't want to type them over and over 00:00:51.460 --> 00:00:54.079 again. I just save them here. If you're listening 00:00:54.079 --> 00:00:55.740 to this as a podcast, remember that it was originally 00:00:55.740 --> 00:00:57.130 recorded as a video. If you're not following 00:00:57.130 --> 00:00:58.630 along, you can go to my YouTube channel. My username 00:00:58.630 --> 00:01:00.130 is Linkarzu. And if you want to support me to 00:01:00.130 --> 00:01:01.810 keep this podcast going, you can donate in Ko 00:01:01.810 --> 00:01:02.969 -Fi. I'm going to leave a link in the description. 00:01:03.210 --> 00:01:04.569 All right. So let's get started with this chapter 00:01:04.569 --> 00:01:09.950 then. All right. So I'm asking everywhere. Where 00:01:09.950 --> 00:01:13.569 can I find people to interview? Right. Like if 00:01:13.569 --> 00:01:15.930 people have a GitHub repo and stuff like that 00:01:15.930 --> 00:01:20.409 to reach out to me and some folks do. Right. 00:01:20.450 --> 00:01:24.730 So one day I'm just wandering around and GitHub. 00:01:25.370 --> 00:01:32.129 Right. And find this repo. GH dash. And I was 00:01:32.129 --> 00:01:37.650 like, I kind of recognize this username. I think 00:01:37.650 --> 00:01:40.430 I've seen this guy in Discord. I went to Discord 00:01:40.430 --> 00:01:44.930 and I noticed that it was you. And this is 8000 00:01:44.930 --> 00:01:50.799 stars. So why didn't you reach out, man? Oh, 00:01:50.799 --> 00:01:54.120 yeah. I don't know. I'm in all the developer 00:01:54.120 --> 00:02:00.120 stuff discords. So when a new one opened, I just 00:02:00.120 --> 00:02:03.680 joined yours immediately because there's not 00:02:03.680 --> 00:02:07.599 a ton of content for, you know, TMAX, NeoVim, 00:02:07.680 --> 00:02:14.520 all that matrix of tooling. And yeah, I guess 00:02:14.520 --> 00:02:18.560 I don't like to... i see it as bragging or i 00:02:18.560 --> 00:02:22.240 don't know why some psychology thing i don't 00:02:22.240 --> 00:02:26.479 know why i uh didn't reach out yeah yeah because 00:02:26.479 --> 00:02:28.979 i was like if you guys have any repo that is 00:02:28.979 --> 00:02:33.120 above 500 stars just reach out i didn't i didn't 00:02:33.120 --> 00:02:36.500 see it yeah you didn't see it yeah i'm asking 00:02:36.500 --> 00:02:40.020 in in the neovim subreddit and i'm asking everywhere 00:02:40.020 --> 00:02:44.120 and uh it's wonderful to have you here thank 00:02:44.120 --> 00:02:47.270 you Yeah, I actually enjoyed your other videos, 00:02:47.509 --> 00:02:53.930 so glad to be on one. Yeah, yeah. And which ones 00:02:53.930 --> 00:02:56.930 do you watch the most? Niobe -related stuff? 00:02:59.490 --> 00:03:01.849 Yeah, I have a backlog to watch the other ones 00:03:01.849 --> 00:03:04.629 because they are interesting as well. But yeah, 00:03:04.889 --> 00:03:09.129 the one with Maria was very interesting as she 00:03:09.129 --> 00:03:13.860 has insights into Niobe itself. contributing 00:03:13.860 --> 00:03:20.120 to it. Yeah. And everything T -Max, NeoVim, even 00:03:20.120 --> 00:03:26.240 being exposed to other stuff like Emacs and what 00:03:26.240 --> 00:03:30.620 was it? Alfred. Yeah. Oh, interesting. Okay. 00:03:30.819 --> 00:03:36.379 So let's just harass you here for a little while. 00:03:36.460 --> 00:03:41.659 Let's stalk you in social networks and all that 00:03:41.659 --> 00:03:46.710 stuff. i see that this is your website um your 00:03:46.710 --> 00:03:51.169 name is dole right yeah okay so i see that this 00:03:51.169 --> 00:03:55.270 is your blog post you have some articles in there 00:03:55.270 --> 00:04:01.210 this is your github profile the repos you have 00:04:01.210 --> 00:04:06.330 this one has 8 000 stars where is it here th 00:04:06.330 --> 00:04:09.349 dash so if there's people wondering what we're 00:04:09.349 --> 00:04:13.479 doing today we're covering this basically demoing 00:04:13.479 --> 00:04:17.220 this get to know it more how to use it all that 00:04:17.220 --> 00:04:20.980 stuff and get to know the live a lot more right 00:04:20.980 --> 00:04:23.600 so i also noticed you have a youtube channel 00:04:23.600 --> 00:04:26.480 you don't have too many videos there these are 00:04:26.480 --> 00:04:30.860 really old are there plans to continue on youtube 00:04:30.860 --> 00:04:35.839 uh not really if there's like a particular topic 00:04:35.839 --> 00:04:38.899 that i'm very interested in and i think a video 00:04:38.899 --> 00:04:41.779 of it would do a better job than a blog post, 00:04:42.000 --> 00:04:45.699 I might create another one. But it's it's a lot 00:04:45.699 --> 00:04:50.259 of work, a lot of work. Hmm. Yeah, it is. So 00:04:50.259 --> 00:04:53.300 you want to share something about yourself, like 00:04:53.300 --> 00:04:59.639 who you are? Yeah. So I live in Tel Aviv, Israel, 00:04:59.959 --> 00:05:07.319 married and 35 years old. And in terms of jobs, 00:05:07.519 --> 00:05:11.620 I've been to big companies like Facebook and 00:05:11.620 --> 00:05:15.939 Wix. And for the past four years, I've tried 00:05:15.939 --> 00:05:19.199 startups. So I'm at my second startup now called 00:05:19.199 --> 00:05:27.100 Port. And yeah, full stack developer. Basically, 00:05:27.100 --> 00:05:31.740 I like to do everything. Okay. Okay. Wonderful. 00:05:32.079 --> 00:05:37.560 And let's see. That's all that we're going to 00:05:37.560 --> 00:05:44.589 be going at today. What is that about? You mind 00:05:44.589 --> 00:05:47.629 sharing a little bit more about it? Yeah, the 00:05:47.629 --> 00:05:51.370 story behind it is that basically when I worked 00:05:51.370 --> 00:05:55.069 at Facebook, we had an internal tool for pretty 00:05:55.069 --> 00:05:58.910 much anything. And one of the tools was called 00:05:58.910 --> 00:06:01.230 Fabricator. I think it's actually not built by 00:06:01.230 --> 00:06:05.589 Facebook. I think it's an external tool. And 00:06:05.589 --> 00:06:09.649 basically what it had is like, different sections 00:06:09.649 --> 00:06:14.250 for PRs. So you can easily see what PR you need 00:06:14.250 --> 00:06:17.110 to review, what are your PRs that are waiting 00:06:17.110 --> 00:06:20.970 on others, and you can configure these sections 00:06:20.970 --> 00:06:27.029 how you'd like. And when I left Facebook and 00:06:27.029 --> 00:06:30.829 joined Wix, basically Wix has a repo for everything. 00:06:31.250 --> 00:06:34.250 If in Facebook it's like a monorepo for everything, 00:06:34.370 --> 00:06:37.410 in Wix it's like polyrepo. It's like a repo for 00:06:37.410 --> 00:06:41.319 every a different package. And it was hard for 00:06:41.319 --> 00:06:45.600 me to track which PRs I have open, how should 00:06:45.600 --> 00:06:48.839 I merge them, in which order. And giving reviews 00:06:48.839 --> 00:06:53.000 was like, I needed to ask someone, or you needed 00:06:53.000 --> 00:06:55.540 someone to send you the PR to review. You couldn't 00:06:55.540 --> 00:06:58.879 do it proactively because it was all over the 00:06:58.879 --> 00:07:03.660 place. Yeah, so I basically want to recreate 00:07:03.660 --> 00:07:07.939 what Facebook did. And actually, there was like 00:07:07.939 --> 00:07:12.720 a startup of ex -Facebookers who created a product 00:07:12.720 --> 00:07:16.620 around the whole experience. And it's actually, 00:07:16.740 --> 00:07:19.319 I think, quite popular. But if you look at it, 00:07:19.459 --> 00:07:21.459 it's very similar to how it was on Facebook. 00:07:22.879 --> 00:07:26.259 Interesting. Okay. And do you personally use 00:07:26.259 --> 00:07:30.519 your tool still? Yeah, I use it all the time. 00:07:30.639 --> 00:07:33.319 If I didn't use it, I think it would be much 00:07:33.319 --> 00:07:36.000 harder for me to keep developing, to keep working 00:07:36.000 --> 00:07:40.860 on it. But since I have so many stuff like I 00:07:40.860 --> 00:07:45.240 personally want, then it's a lot easier to implement 00:07:45.240 --> 00:07:49.000 them. Oh, okay. Let me just update the topic 00:07:49.000 --> 00:07:58.680 here. Okay. So... I have some questions about 00:07:58.680 --> 00:08:01.680 the tool. Do you want to give us a quick demo? 00:08:01.720 --> 00:08:03.980 I don't know if there's stuff that you cannot 00:08:03.980 --> 00:08:07.740 show, or do you have, like, environments? Oh, 00:08:07.740 --> 00:08:13.980 yeah, I can just... Let me see. Yeah, this one 00:08:13.980 --> 00:08:18.819 has private PLs. Yeah, I can just show this one. 00:08:18.959 --> 00:08:24.889 Yeah, this screen is just PLs. Yeah. Okay. Yeah, 00:08:24.949 --> 00:08:29.509 so basically, this is GHDash. It's basically 00:08:29.509 --> 00:08:35.289 composed of different tabs. So in GitHub, you 00:08:35.289 --> 00:08:39.970 have basically four tabs, and you can control 00:08:39.970 --> 00:08:44.330 which PRs are shown on which tab. You have my 00:08:44.330 --> 00:08:50.070 PR, PRs that I need to review, and another two. 00:08:50.269 --> 00:08:56.519 In GHDash, you define... sections in a YAML file, 00:08:56.620 --> 00:08:59.620 in the config file of gh -. And you can specify, 00:08:59.759 --> 00:09:02.440 like, this section is specifically for gh -, 00:09:02.580 --> 00:09:07.519 and I can easily see which PRs are waiting for 00:09:07.519 --> 00:09:12.879 my review. The review tab and my tab have PRs 00:09:12.879 --> 00:09:15.960 that are related to my job, so I won't show them, 00:09:16.039 --> 00:09:22.039 but you can imagine this has... different prs 00:09:22.039 --> 00:09:24.659 like these are prs from projects i'm interested 00:09:24.659 --> 00:09:31.139 in or stuff like that um and basically my goal 00:09:31.139 --> 00:09:36.419 is to not go into github basically because it's 00:09:36.419 --> 00:09:40.519 slow it's uh not very keyboard friendly as opposed 00:09:40.519 --> 00:09:46.639 to like a terminal ui and you can do a bunch 00:09:46.639 --> 00:09:52.519 of different stuff on every pr And it's all a 00:09:52.519 --> 00:09:56.919 single key press away. Like if I do D, then it's 00:09:56.919 --> 00:10:01.240 going to diff. And I can easily see what's the 00:10:01.240 --> 00:10:06.379 PR about. I can approve, assign, comment, all 00:10:06.379 --> 00:10:11.059 this stuff. And I can define custom key binds. 00:10:11.340 --> 00:10:16.139 For example, G is lazy git. So I can easily... 00:10:17.159 --> 00:10:20.120 Press G, then I'm in lazy git. Press Q, I'm back 00:10:20.120 --> 00:10:25.960 in GH dash. And there's like support for issues 00:10:25.960 --> 00:10:29.059 as well. I don't use that as much. I did it more 00:10:29.059 --> 00:10:31.879 for the community because we don't use issues 00:10:31.879 --> 00:10:36.799 at work. But sometimes I look at issues for my 00:10:36.799 --> 00:10:42.440 project and I can easily figure out if I want 00:10:42.440 --> 00:10:46.350 to fix some of them. So you can see the issues 00:10:46.350 --> 00:10:49.990 there as well. And can you see discussions as 00:10:49.990 --> 00:10:54.990 well? No, no. Okay. Some stuff I want to add 00:10:54.990 --> 00:10:59.809 in the future are like, I think the most missing 00:10:59.809 --> 00:11:03.970 feature is around, for me, around check runs. 00:11:04.629 --> 00:11:09.909 Like I can see that my repo doesn't have any 00:11:09.909 --> 00:11:12.769 checks, but if it had, then it would have listed 00:11:12.769 --> 00:11:16.990 them. but you can't see the output of a job. 00:11:17.190 --> 00:11:22.330 So then I have to press O to open the PR and 00:11:22.330 --> 00:11:26.429 go to the check step to actually see why my job 00:11:26.429 --> 00:11:29.830 failed. But I want to integrate it into GH dash. 00:11:30.309 --> 00:11:34.350 But for now, I can see the list of checks that 00:11:34.350 --> 00:11:37.490 are being executed and if they passed or if they 00:11:37.490 --> 00:11:41.389 didn't pass. Is that right? Right, here. This 00:11:41.389 --> 00:11:47.649 is PR from Neovim. And you can see here, these 00:11:47.649 --> 00:11:53.210 ones have failed. This one passed. And you can 00:11:53.210 --> 00:11:58.129 see the summary, just like in GitHub. Wonderful. 00:11:58.889 --> 00:12:02.470 And then the other tabs are like activity, which 00:12:02.470 --> 00:12:06.889 are comments. And files changed, which is just 00:12:06.889 --> 00:12:10.860 a summary of the changes. And then you can press 00:12:10.860 --> 00:12:13.100 D. You can always press D and see the changes. 00:12:13.919 --> 00:12:17.159 The view. Okay. And you can also comment. If 00:12:17.159 --> 00:12:19.639 someone leaves a comment there, you can comment 00:12:19.639 --> 00:12:26.559 stuff in that. Right. I can comment and write 00:12:26.559 --> 00:12:32.960 something. I'm from Tel Aviv or something. And 00:12:32.960 --> 00:12:37.279 then press control D to submit it. And then if 00:12:37.279 --> 00:12:42.129 I go to activity, I can see it. But you can't 00:12:42.129 --> 00:12:45.250 comment on a specific comment that someone left 00:12:45.250 --> 00:12:51.309 on your changes. It's always global comments. 00:12:52.149 --> 00:12:56.429 But you could... Okay, I see. Not like in a thread? 00:12:56.950 --> 00:13:00.230 Not in a thread, yeah. But you can put a comment 00:13:00.230 --> 00:13:05.629 globally in the pull request, right? Yeah, exactly. 00:13:05.830 --> 00:13:09.259 And you can approve a PR if you press V. for 00:13:09.259 --> 00:13:12.360 me, I think, then you can leave an approval comment. 00:13:12.679 --> 00:13:14.879 That's another type of comment that I support. 00:13:15.919 --> 00:13:22.320 Okay. Can you merge after your PR has been approved 00:13:22.320 --> 00:13:25.019 by a co -worker, for example? Can you merge from 00:13:25.019 --> 00:13:28.899 here? Yeah, you can merge. It's M by default, 00:13:29.019 --> 00:13:32.440 and then it asks you if you'd like to squash. 00:13:32.759 --> 00:13:37.470 It basically uses the GHCLI. the GitHub CLI under 00:13:37.470 --> 00:13:41.070 the hood, and it starts it in a different process, 00:13:41.250 --> 00:13:43.090 and then GitHub asks you a bunch of questions 00:13:43.090 --> 00:13:44.710 if you want to squash, if you want to merge. 00:13:46.870 --> 00:13:51.029 And then, yeah, that's basically the flow. And 00:13:51.029 --> 00:13:55.809 I have a question. Does this replace LazyKit, 00:13:55.909 --> 00:14:00.750 or does it add to LazyKit? I'm confused there. 00:14:01.490 --> 00:14:04.889 Yeah, it doesn't really. it's a companion to 00:14:04.889 --> 00:14:09.289 lazy git because lazy git is really good at managing 00:14:09.289 --> 00:14:15.250 your local work committing and rebasing and creating 00:14:15.250 --> 00:14:18.090 branches and stuff like that so i do still use 00:14:18.090 --> 00:14:20.990 lazy git but then lazy git doesn't really have 00:14:20.990 --> 00:14:25.509 any connection to github so i can't see if this 00:14:25.509 --> 00:14:30.370 branch is actually something that i have a pr 00:14:30.370 --> 00:14:34.710 open for or not What's the status of it? And 00:14:34.710 --> 00:14:38.909 I wish LaserGit had this integration, but LaserGit 00:14:38.909 --> 00:14:42.129 is only for Git, and my tool is basically only 00:14:42.129 --> 00:14:48.750 for GitHub. So they're working together. Oh, 00:14:48.870 --> 00:14:54.049 okay. And are there plans to expand your tool 00:14:54.049 --> 00:14:58.409 to do more stuff with Git? Yeah, I actually have 00:14:58.409 --> 00:15:02.799 a design, I think. This is how it looks. But 00:15:02.799 --> 00:15:06.779 I think it's too much work and LazyGit is a really 00:15:06.779 --> 00:15:11.740 great tool. But what I wanted it to have is basically 00:15:11.740 --> 00:15:16.340 a view of branches, but that also shows you if 00:15:16.340 --> 00:15:20.460 it's a PR, this is this little icon, or if it's 00:15:20.460 --> 00:15:23.600 just a commit, a branch on your local machine. 00:15:24.259 --> 00:15:27.580 And if it's a PR, I'd like to see the review 00:15:27.580 --> 00:15:32.370 status and the check status. And then it's very 00:15:32.370 --> 00:15:34.750 similar to LazyGit, and then you'd have a panel 00:15:34.750 --> 00:15:41.870 for your changes, and you can still switch. I 00:15:41.870 --> 00:15:45.190 initially thought of it as having a separate 00:15:45.190 --> 00:15:50.409 tab for Git, and then the regular gh -github 00:15:50.409 --> 00:15:56.710 pull request tab. But yeah, LazyGit is a really 00:15:56.710 --> 00:16:00.169 complex project, and it's... It's working really 00:16:00.169 --> 00:16:04.529 great. So I don't know if I have the required 00:16:04.529 --> 00:16:08.710 amount of motivation to write something big like 00:16:08.710 --> 00:16:14.330 this. But for now, it's sufficient for me to 00:16:14.330 --> 00:16:17.629 just press G and be in lazy git and then Q. But 00:16:17.629 --> 00:16:21.149 it's still a little bit annoying that I can't 00:16:21.149 --> 00:16:31.179 see which branch is which PR. I see. So if LazyGit 00:16:31.179 --> 00:16:35.179 would integrate with the GitHub CLI, it could 00:16:35.179 --> 00:16:37.379 probably retrieve this information and show it 00:16:37.379 --> 00:16:40.960 to you in LazyGit, right? Yeah, right. I actually 00:16:40.960 --> 00:16:46.320 commented on one issue in LazyGit with a solution 00:16:46.320 --> 00:16:51.200 how he could fetch all the pull requests that 00:16:51.200 --> 00:16:55.299 are linked to a branch you have locally. So you 00:16:55.299 --> 00:17:00.379 won't have to basically do a big network request 00:17:00.379 --> 00:17:03.320 so i suggested some efficient way to do it but 00:17:03.320 --> 00:17:08.920 i haven't worked on it other than that yeah okay 00:17:08.920 --> 00:17:12.160 i noticed a message there at the bottom that 00:17:12.160 --> 00:17:15.299 said fetching something does this automatically 00:17:15.299 --> 00:17:18.680 pull every x amount of minutes or how does that 00:17:18.680 --> 00:17:23.480 work yeah so basically uh you have like a config 00:17:23.480 --> 00:17:32.569 file You have a config file, and then you can 00:17:32.569 --> 00:17:37.829 see, I think it's auto and refresh interval minutes. 00:17:37.910 --> 00:17:41.109 So mine is set to refresh every 10 minutes, and 00:17:41.109 --> 00:17:46.369 also it refreshes when you focus GH -. So if 00:17:46.369 --> 00:17:52.769 I switch to the GH - application for my browser, 00:17:52.789 --> 00:17:57.000 for example, it also refreshes. Okay. When the 00:17:57.000 --> 00:18:01.700 focus is gained, right? It refreshes. Okay. Now, 00:18:01.700 --> 00:18:07.599 is this GH - a new event plugin or is it a tool 00:18:07.599 --> 00:18:13.640 on its own? So it's actually a tool of its own, 00:18:13.779 --> 00:18:18.279 but it's like a GitHub CLI plugin. So you have 00:18:18.279 --> 00:18:23.740 to have GH installed. All the authentication 00:18:23.740 --> 00:18:27.859 is done through the GitHub CLI. And a lot of 00:18:27.859 --> 00:18:32.460 the commands are calling the GH CLI. So, yeah. 00:18:33.440 --> 00:18:37.079 You can install it standalone, but probably some 00:18:37.079 --> 00:18:41.680 missing functionality. Yeah. Okay. So, my question 00:18:41.680 --> 00:18:45.380 was more towards Neovim. Can I run it from within 00:18:45.380 --> 00:18:47.880 Neovim, or I have to switch to another Tmux? 00:18:48.539 --> 00:18:51.559 window and open it there how do you use it yeah 00:18:51.559 --> 00:18:56.359 actually so uh so i'm using it as like uh basically 00:18:56.359 --> 00:19:02.220 i press command g uh and it opens gh dash and 00:19:02.220 --> 00:19:05.920 what is what are we looking at is this tmux and 00:19:05.920 --> 00:19:09.319 is that a new window or yeah exactly this is 00:19:09.319 --> 00:19:12.500 tmux and when i press command g i have a key 00:19:12.500 --> 00:19:16.299 binding for it it opens uh gh dash in a new window 00:19:16.299 --> 00:19:19.900 and then i usually If I want to switch back to 00:19:19.900 --> 00:19:22.420 NeoVM, I usually have a keybind to go to the 00:19:22.420 --> 00:19:26.039 last session. So then I can switch between them. 00:19:26.740 --> 00:19:31.359 Oh, I see. I see. Okay. Have you seen... I don't 00:19:31.359 --> 00:19:37.099 know how Folky does it, but... Where is it? If 00:19:37.099 --> 00:19:41.940 I type here, Alt -G, I don't know what this is. 00:19:42.039 --> 00:19:44.880 I don't know the exact... way that he does it 00:19:44.880 --> 00:19:47.119 but he brings up lasik it i don't know if this 00:19:47.119 --> 00:19:52.480 is like um oh i don't know yeah i actually saw 00:19:52.480 --> 00:19:56.880 a plugin i think it's a plugin for new vim what 00:19:56.880 --> 00:20:00.519 you just showed me so a couple of days ago actually 00:20:00.519 --> 00:20:03.640 like last week someone created the plugin for 00:20:03.640 --> 00:20:07.400 gh dash so we can open it inside new vim and 00:20:07.400 --> 00:20:09.720 i think what folky does is just basically put 00:20:09.720 --> 00:20:15.849 it full screen yep But yeah, there's also an 00:20:15.849 --> 00:20:19.069 option to do that now. And is this plugin developed 00:20:19.069 --> 00:20:22.809 by someone else? Have you tested it? What are 00:20:22.809 --> 00:20:25.289 your thoughts there? Yeah, I actually haven't 00:20:25.289 --> 00:20:28.670 because I usually separate my NuVim from other 00:20:28.670 --> 00:20:34.289 tools. I usually open a new window in TMAX. But 00:20:34.289 --> 00:20:38.809 I haven't tested it. I think you mentioned some 00:20:38.809 --> 00:20:43.690 issues with conflicting keybinds. between neovim 00:20:43.690 --> 00:20:48.589 and gh - but yeah whoever uses it will need to 00:20:48.589 --> 00:20:51.730 check it out yeah we'll figure it out okay we'll 00:20:51.730 --> 00:20:56.750 figure it out yeah okay wonderful so um is there 00:20:56.750 --> 00:21:00.049 something else you want to demo about gh dash 00:21:00.049 --> 00:21:02.769 before we get to know you a little bit more because 00:21:02.769 --> 00:21:05.950 i see that you use tmux neovim you're in mac 00:21:05.950 --> 00:21:08.630 os so i just want to talk about all that stuff 00:21:09.039 --> 00:21:12.000 anything else you would like to or you know what 00:21:12.000 --> 00:21:15.380 let me just um go through the docs real quick 00:21:15.380 --> 00:21:17.000 and i'm just going to be asking you questions 00:21:17.000 --> 00:21:21.660 if that's okay okay yeah sure so because this 00:21:21.660 --> 00:21:24.220 is what a new user is going to go through right 00:21:24.220 --> 00:21:29.240 so see the docs yeah okay so it's i just went 00:21:29.240 --> 00:21:31.619 through the docs a little bit not a lot right 00:21:31.619 --> 00:21:36.759 so first install the github cli right you leave 00:21:36.759 --> 00:21:39.970 a link to the installation instructions. I'm 00:21:39.970 --> 00:21:45.130 in Mac OS, so basically just run this. Install 00:21:45.130 --> 00:21:48.250 it. Then you also mentioned right now that this 00:21:48.250 --> 00:21:51.829 is a GitHub extension. I didn't even know that 00:21:51.829 --> 00:21:54.769 they had extensions. So this is why this command 00:21:54.769 --> 00:21:57.690 is there, right? So it's extension install and 00:21:57.690 --> 00:22:01.569 your extension. Exactly. I think there's a subcommand 00:22:01.569 --> 00:22:05.710 to browse all the available extensions so we 00:22:05.710 --> 00:22:07.349 can check out other extensions. Pretty cool. 00:22:08.079 --> 00:22:15.700 Let's see. I think run gh extension and then 00:22:15.700 --> 00:22:22.299 dash dash help. Extension help. Okay, there we 00:22:22.299 --> 00:22:25.079 go. Yeah, and then browse is the subcommand. 00:22:25.900 --> 00:22:29.539 Browse. I didn't know they had extensions in 00:22:29.539 --> 00:22:38.000 the Gist. And then execute it. Let's see. Is 00:22:38.000 --> 00:22:44.319 it like a marketplace then? Basically, yeah. 00:22:44.640 --> 00:22:49.779 I think they're looking for a tag on your repo 00:22:49.779 --> 00:22:54.700 that says it's a GH extension. And then they 00:22:54.700 --> 00:22:58.220 sort it by styles or something here. Yeah, because 00:22:58.220 --> 00:23:02.900 yours is at the top, right? Yeah, there's not 00:23:02.900 --> 00:23:05.839 a ton of extensions, but there are a few that 00:23:05.839 --> 00:23:11.819 are useful. I don't know, has GitHub reached 00:23:11.819 --> 00:23:14.660 out and mentioned something about your extensions? 00:23:14.740 --> 00:23:19.559 Is it so popular? Not really. They once contributed 00:23:19.559 --> 00:23:24.380 because they made a breaking change in GH, in 00:23:24.380 --> 00:23:27.779 the CLI. So they contributed a fix for it. So 00:23:27.779 --> 00:23:31.109 it was pretty nice. but other than that uh no 00:23:31.109 --> 00:23:35.609 so they definitely use it the developers in github 00:23:35.609 --> 00:23:40.750 definitely use your tool yeah yeah yeah i think 00:23:40.750 --> 00:23:43.269 i think there's definitely one or two employees 00:23:43.269 --> 00:23:45.890 the github is a huge company i i bet there's 00:23:45.890 --> 00:23:49.809 someone that uses it yeah but they are aware 00:23:49.809 --> 00:23:52.890 of it because they've contributed interesting 00:23:52.890 --> 00:23:56.750 so let's see let me go back here once you install 00:23:56.750 --> 00:24:01.480 the extension the icons to render properly, just 00:24:01.480 --> 00:24:04.759 have a nerd font, which is what we usually have. 00:24:04.940 --> 00:24:07.420 If we use NeoVim, if you use NeoVim, you have 00:24:07.420 --> 00:24:09.680 this already, right? Exactly. That thing's special. 00:24:10.319 --> 00:24:13.900 Okay. This, I guess, is just a different way 00:24:13.900 --> 00:24:16.200 of doing it if you want to clone the repo. So 00:24:16.200 --> 00:24:19.000 that's it. This is all that is needed to install 00:24:19.000 --> 00:24:23.359 it. Yeah, yeah. The real magic comes from the 00:24:23.359 --> 00:24:26.500 configuration, you know? NeoVim is also easy 00:24:26.500 --> 00:24:28.769 to install, but then... You need to configure 00:24:28.769 --> 00:24:33.190 it and it's all another story. Yeah, definitely. 00:24:33.470 --> 00:24:37.029 Okay, but that gives people a better idea on 00:24:37.029 --> 00:24:40.930 what to do, right? So I guess everything is documented 00:24:40.930 --> 00:24:44.750 here. I have not, I think I installed it. Yeah, 00:24:44.789 --> 00:24:47.309 but I have not configured it. I will play around 00:24:47.309 --> 00:24:49.549 with it. And if I have other questions, I'll 00:24:49.549 --> 00:24:51.750 let you know. I will probably create a video 00:24:51.750 --> 00:24:56.849 about it, you know, and all that stuff. Yep. 00:24:57.230 --> 00:24:59.349 anything else you want to share hear from the 00:24:59.349 --> 00:25:02.589 documentation or stuff that people ask all the 00:25:02.589 --> 00:25:05.029 time that would help you not to be answering 00:25:05.029 --> 00:25:07.849 the same question all the time yeah there's actually 00:25:07.849 --> 00:25:10.890 a really good video that uh charme charme is 00:25:10.890 --> 00:25:14.430 the library that like a company that wrote a 00:25:14.430 --> 00:25:16.750 bunch of libraries for developing terminal uis 00:25:16.750 --> 00:25:20.609 and they made a video about gh dash so if you 00:25:20.609 --> 00:25:22.650 want to understand like why you should use it 00:25:23.519 --> 00:25:27.359 how it can help you, and also how to actually 00:25:27.359 --> 00:25:30.059 use it, then this video is a great... It's actually 00:25:30.059 --> 00:25:35.019 linked in my README. It's pretty recent, so it's... 00:25:35.019 --> 00:25:40.700 Yeah, exactly. Okay. Okay. So this helps a lot 00:25:40.700 --> 00:25:43.180 if you're just getting started. Yeah, if you 00:25:43.180 --> 00:25:46.500 just want to get to know what ghdash is and why 00:25:46.500 --> 00:25:49.759 to use it without even installing it. And then 00:25:49.759 --> 00:25:52.809 maybe it piques your interest. You install it 00:25:52.809 --> 00:25:58.869 later. Yeah. Okay. Wonderful. So we already went 00:25:58.869 --> 00:26:02.730 through the demo. If it replaces LazyKit, that's 00:26:02.730 --> 00:26:07.029 a question that I had. And if it's not, I already 00:26:07.029 --> 00:26:09.950 shared about you as well. Where people can find 00:26:09.950 --> 00:26:12.069 you, I'm going to leave all of those links there. 00:26:12.890 --> 00:26:15.710 And you mind sharing a little bit more about 00:26:15.710 --> 00:26:19.509 the experience of maintaining open source? Because 00:26:19.509 --> 00:26:22.460 it's a pretty popular repo. How has it been? 00:26:23.940 --> 00:26:28.519 Yeah, I think first of all, you learn a lot about 00:26:28.519 --> 00:26:33.079 areas that you don't touch in your regular work. 00:26:33.259 --> 00:26:36.460 Like I haven't wrote a lot of GitHub actions 00:26:36.460 --> 00:26:42.019 and I haven't dealt with publishing stuff to 00:26:42.019 --> 00:26:45.680 Homebrew or releasing assets to GitHub. So all 00:26:45.680 --> 00:26:51.890 of that is like novel knowledge. And then I guess 00:26:51.890 --> 00:26:54.829 it depends really on the owner of the repo because 00:26:54.829 --> 00:27:00.490 I take it super chill. Like if I don't feel like 00:27:00.490 --> 00:27:03.349 working on it, I don't work on it for a few weeks. 00:27:03.869 --> 00:27:07.829 I know a lot of people work on open source projects 00:27:07.829 --> 00:27:10.069 that a lot of companies depend on. Then it's 00:27:10.069 --> 00:27:12.410 a whole different story because they need to 00:27:12.410 --> 00:27:14.390 fix urgent bugs. They need to basically be on 00:27:14.390 --> 00:27:19.640 call for their project. But this is a side project 00:27:19.640 --> 00:27:24.559 that aims to give a better experience on top 00:27:24.559 --> 00:27:27.279 of GitHub. It's not something that can break 00:27:27.279 --> 00:27:33.640 people's workflows. And then I received a few 00:27:33.640 --> 00:27:36.180 contributions along the way, like the documentation 00:27:36.180 --> 00:27:39.220 site that you just saw. Someone actually contributed 00:27:39.220 --> 00:27:42.980 the whole thing. It was like 20 ,000 lines or 00:27:42.980 --> 00:27:46.829 something. I guess because of the framework they 00:27:46.829 --> 00:27:50.970 used, they wrote a ton of content for the documentation, 00:27:51.269 --> 00:27:55.869 and I tried to maintain it ever since. And I 00:27:55.869 --> 00:27:58.630 think support for theming was also contributed, 00:27:59.049 --> 00:28:02.869 so you don't all have to use my specific colors. 00:28:04.670 --> 00:28:07.829 You can specify, because I have a set of colors 00:28:07.829 --> 00:28:10.329 that I use, so I can specify them in the configuration 00:28:10.329 --> 00:28:14.900 file? Yeah, exactly. Yeah, it's YAML, and then 00:28:14.900 --> 00:28:18.079 you specify a bunch of different main text, secondary 00:28:18.079 --> 00:28:23.319 text, a bunch of colors. Yeah, or it falls back 00:28:23.319 --> 00:28:26.920 to your terminal colors if you didn't specify 00:28:26.920 --> 00:28:30.740 something. Oh, yeah. I apply the colors. It might 00:28:30.740 --> 00:28:33.160 work out of the box. I don't know. Yeah, because 00:28:33.160 --> 00:28:35.779 I apply the colors in Ghosty as well, so it will 00:28:35.779 --> 00:28:37.680 pick them up. I don't need to touch it then. 00:28:38.890 --> 00:28:41.609 Yeah, maybe you need to tweak some stuff, then 00:28:41.609 --> 00:28:48.549 you can always override it. Okay. So, yeah, it's 00:28:48.549 --> 00:28:53.569 really fun. Okay. And the support aspect of it, 00:28:53.630 --> 00:28:58.089 how has it been? Too many issues, discussions? 00:29:01.950 --> 00:29:05.910 Yeah, so I'm not super responsive on issues. 00:29:06.329 --> 00:29:10.890 I do... use it every day, so I know there aren't 00:29:10.890 --> 00:29:13.589 any major bugs. And if there are, I usually try 00:29:13.589 --> 00:29:18.650 to deal with them pretty quickly. I do like when 00:29:18.650 --> 00:29:22.029 someone comes out of the blue, creates a detailed 00:29:22.029 --> 00:29:25.650 issue with what he wants, and then I usually 00:29:25.650 --> 00:29:28.170 comment, that sounds great, because I usually 00:29:28.170 --> 00:29:31.950 don't block a lot of feature requests. And then 00:29:31.950 --> 00:29:37.470 if he works on a PR, that's awesome. Yeah. it 00:29:37.470 --> 00:29:40.210 doesn't require really long discussions on technical 00:29:40.210 --> 00:29:43.950 details or something it's usually pretty uh features 00:29:43.950 --> 00:29:46.329 in my projects are pretty uh straightforward 00:29:46.329 --> 00:29:51.789 okay yeah and what if a user comes in uh comes 00:29:51.789 --> 00:29:54.650 up with a new idea they want to implement it 00:29:54.650 --> 00:29:56.529 what would you recommend would you recommend 00:29:56.529 --> 00:29:58.930 for them to start a discussion first or just 00:29:58.930 --> 00:30:03.170 submit the code and um what do you suggest there 00:30:04.490 --> 00:30:08.349 So for the wrong sake, I'd recommend opening 00:30:08.349 --> 00:30:11.170 an issue first because you might work on the 00:30:11.170 --> 00:30:15.490 code and then I'm going to say this is too niche 00:30:15.490 --> 00:30:19.809 of a use case. I don't want every user to get 00:30:19.809 --> 00:30:25.329 this basically as a bloat because it fits your 00:30:25.329 --> 00:30:30.430 workflow. So I usually try to generalize the 00:30:30.430 --> 00:30:33.920 solution in the issue. so it fits all users, 00:30:34.480 --> 00:30:40.180 or implement some kind of plug -in mechanism, 00:30:40.299 --> 00:30:44.220 like I did for the custom commands. So we can 00:30:44.220 --> 00:30:47.299 basically define key bindings to run arbitrary 00:30:47.299 --> 00:30:50.920 commands, and then this gives a solution for 00:30:50.920 --> 00:30:56.220 specific users' needs. They don't have to touch 00:30:56.220 --> 00:31:01.720 any of the gh -code. And they can use their own 00:31:01.720 --> 00:31:06.079 workflows however they want. Oh, I see. So just 00:31:06.079 --> 00:31:09.299 to save you the trouble of writing the code and 00:31:09.299 --> 00:31:15.579 then getting rejected if it's too niche, I suggest 00:31:15.579 --> 00:31:19.880 to open a niche first. Okay, great. Have you 00:31:19.880 --> 00:31:23.700 had bad experiences with users? Have you gotten 00:31:23.700 --> 00:31:31.150 into fights in GitHub? No, I don't. yeah no i've 00:31:31.150 --> 00:31:34.490 heard of like uh github discussions that uh turned 00:31:34.490 --> 00:31:40.509 uh yeah to be pretty heated but uh no no it didn't 00:31:40.509 --> 00:31:45.529 happen to me okay wonderful so uh yeah that covers 00:31:45.529 --> 00:31:49.250 all the questions that i had about you know um 00:31:49.250 --> 00:31:55.329 open source basically so when you showed uh the 00:31:55.329 --> 00:31:58.630 demo I noticed that you use Neovim. Is that your 00:31:58.630 --> 00:32:03.170 main editor? Yeah, I use Neovim as my main editor. 00:32:03.690 --> 00:32:11.109 And why is that? Because basically it started 00:32:11.109 --> 00:32:14.730 as a rabbit hole. I started having pain in my 00:32:14.730 --> 00:32:18.349 arm like every programmer. And then I started 00:32:18.349 --> 00:32:23.849 heavily using VS Code key bindings. But it wasn't 00:32:23.849 --> 00:32:27.670 enough, basically. Sometimes I needed to reach 00:32:27.670 --> 00:32:31.769 the file explorer. It wasn't really a native 00:32:31.769 --> 00:32:38.170 experience for keyboard users. A lot of features 00:32:38.170 --> 00:32:46.029 rely heavily on the mouse. Then I swallowed a 00:32:46.029 --> 00:32:50.690 Paramogen pill, like many others. That's how 00:32:50.690 --> 00:32:54.630 you got started. Yeah, yeah, and then I've dug 00:32:54.630 --> 00:32:58.150 a hole deeper and deeper, yeah, basically. Yeah, 00:32:58.289 --> 00:33:00.809 it's hard to get out of there. And for how long 00:33:00.809 --> 00:33:04.589 have you been using NeoVim? I think for three 00:33:04.589 --> 00:33:07.390 years, something like that. Oh, three years, 00:33:07.450 --> 00:33:10.549 that's a lot of time. And you use your own config 00:33:10.549 --> 00:33:14.970 or a distro? Yeah, I use my own config. I started 00:33:14.970 --> 00:33:19.750 back when I think there was LunarVim or something 00:33:19.750 --> 00:33:23.880 and AstroVim, but I started... I started on my 00:33:23.880 --> 00:33:26.200 own and then I've been maintaining and improving 00:33:26.200 --> 00:33:30.359 it along the years. What are your thoughts on 00:33:30.359 --> 00:33:36.819 distributions? Yeah, they look great, but I require 00:33:36.819 --> 00:33:41.099 like too much. I wanted to tweak it too much. 00:33:41.460 --> 00:33:44.660 And then distributions usually get in your way. 00:33:46.720 --> 00:33:50.250 But I haven't. fully tried like LazyVim or something 00:33:50.250 --> 00:33:53.269 like that, to honestly tell you if it's hard 00:33:53.269 --> 00:33:58.930 to customize. But having your own distribution 00:33:58.930 --> 00:34:03.349 gives you full control, basically. Yeah, that 00:34:03.349 --> 00:34:09.929 is correct. Yep. And is your NeoVim config, because 00:34:09.929 --> 00:34:13.489 it looks quite good. Your setup looks really 00:34:13.489 --> 00:34:15.570 awesome, to be honest. Do you have it in your 00:34:15.570 --> 00:34:20.170 .files or is that private? Yeah. Yeah. I have 00:34:20.170 --> 00:34:24.769 like a repo for my .files. It's in my GitHub 00:34:24.769 --> 00:34:31.489 and NuVim is inside. Basically it's under Nix 00:34:31.489 --> 00:34:35.110 module and then Envim. This is my entire config. 00:34:35.670 --> 00:34:41.050 So you use Nix, Nix Darwin. Is that right? Yeah. 00:34:41.130 --> 00:34:44.469 I beat a bullet on that as well. Pretty, yeah. 00:34:44.670 --> 00:34:49.250 Not, not too long ago. Yeah. How long ago? I 00:34:49.250 --> 00:34:54.369 think it's like six months ago. How has that 00:34:54.369 --> 00:34:57.130 been? Because everyone keeps telling me to try 00:34:57.130 --> 00:35:00.190 either Linux, that I should move to Linux, or 00:35:00.190 --> 00:35:04.170 that I should use Nix. And I'm like, oh no. I 00:35:04.170 --> 00:35:08.489 honestly don't want to go down the Nix rabbit 00:35:08.489 --> 00:35:11.610 hole. How has that been? Yeah, I can totally 00:35:11.610 --> 00:35:16.179 get it. It's not an immediate benefit like moving 00:35:16.179 --> 00:35:19.099 to NuVim. I think it's more like if you're interested 00:35:19.099 --> 00:35:23.880 in the technology and also willing to configure 00:35:23.880 --> 00:35:27.760 Nix to learn stuff, then it's great. But it's 00:35:27.760 --> 00:35:31.679 not like I'm replacing laptops every two weeks 00:35:31.679 --> 00:35:35.239 or I have three different machines. So that's 00:35:35.239 --> 00:35:37.579 not the reason. If you do have three different 00:35:37.579 --> 00:35:39.219 machines and you want them all configured... 00:35:39.550 --> 00:35:46.389 The same, or if you're using Nix for your job, 00:35:46.510 --> 00:35:51.429 or I'm using something in my job that uses Nix 00:35:51.429 --> 00:35:54.469 under the hood, then it's nice to know how it 00:35:54.469 --> 00:36:00.409 works. But I don't think it's a better developer 00:36:00.409 --> 00:36:04.309 experience than using something like, what's 00:36:04.309 --> 00:36:07.050 it called, Stow, or one of the more standard 00:36:07.050 --> 00:36:12.269 tools. Yeah. But it's pretty cool, yeah. But 00:36:12.269 --> 00:36:17.630 Nix is pretty cool. I think it has a lot of potential 00:36:17.630 --> 00:36:20.210 for tools to be built on top of it. And the tools 00:36:20.210 --> 00:36:23.469 I use for my job, for my day job, it uses Nix, 00:36:23.489 --> 00:36:28.030 so pretty awesome. But yeah, it's another rabbit 00:36:28.030 --> 00:36:31.869 hole. If you're bored from Nivim one day, then 00:36:31.869 --> 00:36:36.570 just open the Nix docs and start digging your 00:36:36.570 --> 00:36:42.489 grave. And do you recommend Nix? Honestly, would 00:36:42.489 --> 00:36:45.789 you recommend it? Like for someone like me, if 00:36:45.789 --> 00:36:48.730 I need to deploy a new Mac, I have, I even create 00:36:48.730 --> 00:36:51.809 a video, right? So I have bash scripts. That's 00:36:51.809 --> 00:36:54.289 what I use. And I install everything, you know, 00:36:54.289 --> 00:36:58.449 all my applications with brew files, right? So 00:36:58.449 --> 00:37:01.690 install all of them, set up all the Mac OS system 00:37:01.690 --> 00:37:04.289 settings in the bash script as well. You know, 00:37:04.289 --> 00:37:07.840 even the hot corners. everything in that script, 00:37:08.079 --> 00:37:11.500 would it make sense? Or would you recommend it? 00:37:11.780 --> 00:37:14.420 I don't think I would recommend it. If you have 00:37:14.420 --> 00:37:18.800 a setup that works for you already and uses scripts, 00:37:19.139 --> 00:37:21.500 I think it's the most simple way to manage your 00:37:21.500 --> 00:37:24.539 environment. If you're switching laptops every 00:37:24.539 --> 00:37:28.059 five, six years, then it's totally an overkill 00:37:28.059 --> 00:37:35.300 to use Nix. It's like, I don't know what to compare 00:37:35.300 --> 00:37:38.679 it to, like learning Kubernetes on your own. 00:37:38.739 --> 00:37:41.420 If you don't use Kubernetes at your day job, 00:37:41.559 --> 00:37:44.539 then you probably don't need it. I think it's 00:37:44.539 --> 00:37:50.159 similar for me in Nix. But further learning experience 00:37:50.159 --> 00:37:53.179 is good, especially if you use it at work, right? 00:37:53.280 --> 00:37:57.360 So you would benefit from that. Exactly. I think 00:37:57.360 --> 00:38:01.300 that's the main benefit for me. Because I use 00:38:01.300 --> 00:38:06.179 a single laptop, I don't really need Nix. Nix 00:38:06.179 --> 00:38:11.980 is another kill for me. But it made my move like 00:38:11.980 --> 00:38:16.420 a sweet jobs, I think, four months ago, and it 00:38:16.420 --> 00:38:19.480 was a single install. But I guess you can achieve 00:38:19.480 --> 00:38:23.239 that with script as well. It's not a must to 00:38:23.239 --> 00:38:27.099 use Nix. Okay, makes sense. Okay. Good to know. 00:38:27.239 --> 00:38:29.739 I noticed that the file explorer that you use 00:38:29.739 --> 00:38:34.219 in Neobim is minidotfiles. Is that right or I'm 00:38:34.219 --> 00:38:37.820 wrong there? Yeah, exactly. Yeah, minidotfiles. 00:38:38.219 --> 00:38:41.019 I didn't know that you could have relative line 00:38:41.019 --> 00:38:43.599 numbers in minidotfiles. Is that built -in or 00:38:43.599 --> 00:38:46.420 something you came up with yourself? I think 00:38:46.420 --> 00:38:53.059 I did configure it. I don't know if I did it 00:38:53.059 --> 00:38:58.150 here. Yeah, exactly here. I created another command 00:38:58.150 --> 00:39:03.590 that whenever the window is updated, I apply 00:39:03.590 --> 00:39:09.590 these options. Interesting. So if you type that 00:39:09.590 --> 00:39:12.369 number, it'll jump directly to that file and 00:39:12.369 --> 00:39:16.969 open it? Or how do you do it? So I usually use 00:39:16.969 --> 00:39:20.949 relative line numbers a lot. So if I want to 00:39:20.949 --> 00:39:24.280 go to dressing .lua, And then I can just press 00:39:24.280 --> 00:39:29.099 25K and I'm there. And then I use L to open it 00:39:29.099 --> 00:39:34.300 and Q to close mini .files. So it's pretty smooth. 00:39:36.440 --> 00:39:41.820 I never used relative line numbers. I even disabled 00:39:41.820 --> 00:39:45.079 them and I just left them as regular line numbers. 00:39:45.360 --> 00:39:48.179 And it looks horrible. There are some files in 00:39:48.179 --> 00:39:50.699 which I have like 4 ,000 lines. Let me show you 00:39:50.699 --> 00:39:57.829 one. uh let's see like my key maps key maps look 00:39:57.829 --> 00:40:03.230 at that how many keybinds do you have oh i have 00:40:03.230 --> 00:40:06.090 have a lot of crazy stuff going on there man 00:40:06.090 --> 00:40:09.449 but look at this look at the gutter i think it's 00:40:09.449 --> 00:40:12.110 called oh yeah i'm not gonna type four digits 00:40:12.110 --> 00:40:17.989 yeah but i i disabled Relative line numbers. 00:40:18.190 --> 00:40:20.750 I never use them. What I'm trying to use more 00:40:20.750 --> 00:40:25.170 is flash, right? So jump using flash, but I don't 00:40:25.170 --> 00:40:28.429 know. I just don't use it. You know, I never 00:40:28.429 --> 00:40:31.070 got used to it. I just got used to doing this 00:40:31.070 --> 00:40:35.849 or control you control control D. I know it's 00:40:35.849 --> 00:40:38.369 not a good practice. How do you navigate around? 00:40:38.550 --> 00:40:41.210 Do you use relative line numbers a lot? Did you 00:40:41.210 --> 00:40:44.619 get used to them? Yeah, I also didn't start out 00:40:44.619 --> 00:40:47.579 using relative line numbers. For the longest 00:40:47.579 --> 00:40:51.199 time, I just did the J and K or control D, control 00:40:51.199 --> 00:40:57.539 U. But I found myself also, like I did a lot 00:40:57.539 --> 00:41:00.420 of exploration, if I wanted to jump to this word 00:41:00.420 --> 00:41:03.920 text. So I have a couple of options, and I think 00:41:03.920 --> 00:41:07.380 one of them is Flash, which tries to solve both 00:41:07.380 --> 00:41:10.460 navigating horizontally and... and vertically. 00:41:10.719 --> 00:41:13.400 But now what I usually do is like, I can see 00:41:13.400 --> 00:41:16.860 it's eight lights down. So I do eight AJ and 00:41:16.860 --> 00:41:24.980 then I usually do FFS or a bunch of W's. Yeah, 00:41:25.079 --> 00:41:29.679 basically spam W. I didn't find all the jump 00:41:29.679 --> 00:41:34.159 plugins to work for me as well. I didn't find 00:41:34.159 --> 00:41:38.480 that. Like this relative line numbers is more 00:41:38.480 --> 00:41:43.659 simple, I guess, to use. Yeah. I guess it also 00:41:43.659 --> 00:41:47.300 depends on how you have your numbers laid out. 00:41:47.420 --> 00:41:50.280 Because I don't use layouts on my keyboard. I 00:41:50.280 --> 00:41:51.940 don't know if you're able to see it there. Let 00:41:51.940 --> 00:41:55.699 me switch this other one. My numbers are there 00:41:55.699 --> 00:42:02.329 at the top. So I cannot reach them. Yeah, I guess 00:42:02.329 --> 00:42:07.130 I can show, if you can see, my numbers are basically 00:42:07.130 --> 00:42:15.050 these three rows. So if I toggle a layer, these 00:42:15.050 --> 00:42:17.949 are my numbers. So it's this layer. And then 00:42:17.949 --> 00:42:23.630 I can just, one, two, three, super quickly type 00:42:23.630 --> 00:42:30.539 numbers. So it's pretty... Yeah, you have to 00:42:30.539 --> 00:42:35.340 have the right setup for relative line numbers 00:42:35.340 --> 00:42:39.739 to work. Yep. Now that you showed... Oh, and 00:42:39.739 --> 00:42:42.340 mini .dat files. Let's just go back there and 00:42:42.340 --> 00:42:44.800 then we can talk about your keyboard. Yeah, so 00:42:44.800 --> 00:42:47.679 I actually started with, I think it was nvim3. 00:42:51.440 --> 00:42:58.429 And I found that it wasn't really working. for 00:42:58.429 --> 00:43:02.210 me in terms of going up a directory, going down 00:43:02.210 --> 00:43:07.670 a directory. Basically, I saw other people use 00:43:07.670 --> 00:43:12.969 oil .envim, which is a similar plugin. And I 00:43:12.969 --> 00:43:15.190 was kind of jealous, but I didn't want to use 00:43:15.190 --> 00:43:18.570 oil because it was too far away from a regular 00:43:18.570 --> 00:43:23.969 file tree. It was harder to see, like mini .files 00:43:23.969 --> 00:43:28.929 shows you, the full path of the files. OL .envim 00:43:28.929 --> 00:43:32.630 is just a single directory. And I think mini 00:43:32.630 --> 00:43:35.570 .files is basically best of both worlds. It's 00:43:35.570 --> 00:43:39.849 similar to envim3 in that it's almost like a 00:43:39.849 --> 00:43:47.210 file explorer, but it has the functionality of 00:43:47.210 --> 00:43:51.909 treating your files like lines in a buffer kind 00:43:51.909 --> 00:43:55.349 of way that you can delete lines. or move files 00:43:55.349 --> 00:43:57.510 by deleting the line and pasting it in another 00:43:57.510 --> 00:44:05.250 folder. So yeah, it's a pretty cool plugin, yeah. 00:44:05.909 --> 00:44:09.010 And I noticed, just like Maria, that you have 00:44:09.010 --> 00:44:11.909 the preview disabled. Is there a reason for that? 00:44:13.309 --> 00:44:17.769 Yeah, I think I found it too distracting, basically. 00:44:18.429 --> 00:44:23.559 I usually don't... look at the preview. Even 00:44:23.559 --> 00:44:28.599 in my smart picker of Snacks, the Snacks plugin, 00:44:28.860 --> 00:44:35.519 I disabled the preview. Not in all the views, 00:44:35.599 --> 00:44:39.760 like in my buffers view, I do use the preview 00:44:39.760 --> 00:44:44.079 to see what line I had it opened on, basically. 00:44:46.559 --> 00:44:49.460 Okay, interesting. So you use minidet files? 00:44:50.239 --> 00:44:56.300 your picker is snacks um right so yeah i noticed 00:44:56.300 --> 00:44:59.420 that you don't have oh yeah you do have tabs 00:44:59.420 --> 00:45:03.880 at the top are those tabs yeah the top is the 00:45:03.880 --> 00:45:08.800 my uh tmx no i don't usually do tabs but uh sometimes 00:45:08.800 --> 00:45:11.820 they i like my tabs show up at the bottom here 00:45:11.820 --> 00:45:16.099 and if i open like my uh diffu plugin then it 00:45:16.099 --> 00:45:21.039 usually then it opens in a new tab So I use tabs 00:45:21.039 --> 00:45:26.980 very rarely. But yeah, same for splits. I don't 00:45:26.980 --> 00:45:32.179 usually use splits. OK, yeah, me neither. I don't 00:45:32.179 --> 00:45:34.880 use them too much. Tabs, I don't use them. How 00:45:34.880 --> 00:45:37.880 do you navigate files then with the stacks picker, 00:45:37.880 --> 00:45:41.300 the buffer thingy? Or how do you do it? Yeah, 00:45:41.380 --> 00:45:46.210 I use the smart picker a lot. I use the buffers 00:45:46.210 --> 00:45:51.869 thingy. I also have kind of like a Harpoon kind 00:45:51.869 --> 00:45:54.409 of plugin. I don't remember its name exactly, 00:45:54.570 --> 00:45:59.130 but you can basically mark files and then jump 00:45:59.130 --> 00:46:03.030 to them pretty quickly. And you can delete them 00:46:03.030 --> 00:46:07.550 like a regular buffer or move them around. So 00:46:07.550 --> 00:46:10.630 if I work on a feature that requires five different 00:46:10.630 --> 00:46:14.829 files, I usually reach out to this plugin. Because 00:46:14.829 --> 00:46:17.949 the small picker doesn't always suggest the most 00:46:17.949 --> 00:46:25.050 relevant file that I need to jump to. Yeah. Yeah, 00:46:25.170 --> 00:46:29.070 so this is basically my workflow. No, I think 00:46:29.070 --> 00:46:36.849 it's called not small open. What is it called? 00:46:39.630 --> 00:46:48.460 Let's see. Reticle? No. No. Oh, Smear Cursor. 00:46:48.599 --> 00:46:51.340 That's why I see the animations there in Eovim, 00:46:51.420 --> 00:46:54.960 right? Yeah. Is that the plugin? Yeah, yeah, 00:46:55.000 --> 00:46:58.300 exactly. Yeah, that's Smear. I noticed you're 00:46:58.300 --> 00:47:00.360 using Ghosty, and I think it doesn't have those 00:47:00.360 --> 00:47:04.119 animations. Not sure. Exactly. Exactly, yeah. 00:47:05.099 --> 00:47:09.880 I saw Kitty introduce it a while ago, and it's 00:47:09.880 --> 00:47:12.530 pretty cool. It really helps, like... I don't 00:47:12.530 --> 00:47:14.849 use it for the cool effect. I use it for seeing 00:47:14.849 --> 00:47:19.869 where my cursor came from, basically. So it's 00:47:19.869 --> 00:47:23.469 really good for that. I tried the other plugins 00:47:23.469 --> 00:47:26.130 like smooth scrolling and stuff like that to 00:47:26.130 --> 00:47:30.389 not have the scrolling be so abrupt, but it was 00:47:30.389 --> 00:47:34.909 too slow for me. I like the instance, the way 00:47:34.909 --> 00:47:39.030 that it's instant, but I also like to see a little 00:47:39.030 --> 00:47:43.119 bit of where I jumped from. Yeah. Yeah, I opened 00:47:43.119 --> 00:47:46.559 lace even one day and my cursor was like, I don't 00:47:46.559 --> 00:47:49.619 know really slow and I was like, what's happening 00:47:49.619 --> 00:47:54.460 here? I Don't know if Oki made a change and I 00:47:54.460 --> 00:47:58.500 don't know what plug -in it was that it Enabled 00:47:58.500 --> 00:48:02.400 but I do get that the cursor slow for me was 00:48:02.400 --> 00:48:06.380 like no Because it you can see the cursor moving 00:48:06.380 --> 00:48:10.980 slowly. No was too slow for me Exactly. I tried 00:48:10.980 --> 00:48:13.539 to configure it to be as fast as possible, but 00:48:13.539 --> 00:48:17.320 it's not really... I really wish Terminal supported 00:48:17.320 --> 00:48:19.840 smooth scrolling, but it's not really smooth 00:48:19.840 --> 00:48:22.539 scrolling because you can't achieve that in NeoVim. 00:48:24.699 --> 00:48:29.480 But yeah, I do envy the smoothness of crawling 00:48:29.480 --> 00:48:34.539 in a proper GUI app. Oh, or in Neobite. Neobite 00:48:34.539 --> 00:48:41.219 is a little bit... Better, I think. Do you use 00:48:41.219 --> 00:48:45.119 Neovite or no? No, but I'm thinking of integrating 00:48:45.119 --> 00:48:49.320 it because I recently moved my notes from Obsidian 00:48:49.320 --> 00:48:53.900 to Neovim because of the editing experience. 00:48:54.199 --> 00:48:56.860 And I'm thinking of maybe using a separate app 00:48:56.860 --> 00:49:00.199 for my notes. So Neovite sounds like a great 00:49:00.199 --> 00:49:03.420 option. Oh, so it will be like your dedicated 00:49:03.420 --> 00:49:08.769 app for notes. Exactly. I'd like to know more 00:49:08.769 --> 00:49:12.050 about that, the nodes. Why did you switch from 00:49:12.050 --> 00:49:17.670 Obsidian to NeoBeam? Basically, I found the... 00:49:17.670 --> 00:49:23.809 Yeah, the beam integration to be too slow. Like, 00:49:23.809 --> 00:49:29.110 it moves and it's kind of laggy and not all the 00:49:29.110 --> 00:49:31.349 keybinds work that I'm used to. Like, I'm used 00:49:31.349 --> 00:49:34.309 to pressing little, little to switch to my alternate 00:49:34.309 --> 00:49:38.780 buffer. and even making these relative line numbers 00:49:38.780 --> 00:49:44.500 work was really a pain i had to configure a css 00:49:44.500 --> 00:49:48.119 rule for each line so i made like a hundred of 00:49:48.119 --> 00:49:52.179 them so if if there's more than a hundred there's 00:49:52.179 --> 00:49:54.059 probably not more than a hundred relative lines 00:49:54.059 --> 00:49:58.699 uh in this screen but it's gonna break oh okay 00:49:58.699 --> 00:50:02.599 yeah and then you know the other amenities of 00:50:02.599 --> 00:50:06.949 like my smart picker and uh my yeah it's it's 00:50:06.949 --> 00:50:11.769 more tuned to my uh workflow yeah once you're 00:50:11.769 --> 00:50:15.190 used to new vim switching to obsidian feels like 00:50:15.190 --> 00:50:21.110 up i'm i'm not going i don't expect to offend 00:50:21.110 --> 00:50:25.190 anyone but it doesn't feel optimized for any 00:50:25.190 --> 00:50:27.429 of them user that's what i'm gonna go with right 00:50:27.429 --> 00:50:31.449 because i do like using the surround motions 00:50:31.449 --> 00:50:37.199 a lot right so gs exactly select around quotes 00:50:37.199 --> 00:50:41.420 and all that or delete around quotes. I couldn't 00:50:41.420 --> 00:50:44.139 do it in Obsidian. Maybe there's a plugin, you 00:50:44.139 --> 00:50:47.280 know, but it felt too different. I needed to 00:50:47.280 --> 00:50:51.619 look for workarounds in Obsidian that I had in 00:50:51.619 --> 00:50:56.340 NeoVim. So I just decided to also switch my notes 00:50:56.340 --> 00:51:00.840 fully to NeoVim. Do you view images in NeoVim 00:51:00.840 --> 00:51:07.110 or you don't in your notes? Yeah, I do. Yeah, 00:51:07.309 --> 00:51:10.530 this is the readme for my .files, and you can 00:51:10.530 --> 00:51:16.710 see images render just fine. Yeah, that's pretty 00:51:16.710 --> 00:51:21.130 awesome. I tried other plugins before Falky wrote 00:51:21.130 --> 00:51:27.650 snacks .image, and they often broke, but this 00:51:27.650 --> 00:51:32.210 one works perfectly, yeah. Yeah. What is the 00:51:32.210 --> 00:51:36.670 other one called? Image .envim, man, yep. Yeah, 00:51:36.730 --> 00:51:41.210 by third. Yeah, by third. I used that one for 00:51:41.210 --> 00:51:45.190 a long time. Worked wonderfully, but I don't 00:51:45.190 --> 00:51:49.530 know. Snacks image, to me, feels more stable. 00:51:49.769 --> 00:51:54.730 And so far, it has been working great. Yeah, 00:51:54.789 --> 00:51:57.309 I didn't have to configure it too much or play 00:51:57.309 --> 00:52:03.840 around with it, but... I do remember like third 00:52:03.840 --> 00:52:09.559 .image, this one, required a lot of configuration 00:52:09.559 --> 00:52:12.820 to make it work. I don't really remember. I think 00:52:12.820 --> 00:52:15.599 I copied some of the old stuff to delete the 00:52:15.599 --> 00:52:21.260 images and stuff, yeah? Yep. But snacks .image, 00:52:21.500 --> 00:52:25.059 this is my configuration. Yeah. And it just works. 00:52:25.559 --> 00:52:28.659 And if you open a picker, you can just view the 00:52:28.659 --> 00:52:31.800 images there. You can even... preview pdf files 00:52:31.800 --> 00:52:35.320 or videos it shows you the image of a video so 00:52:35.320 --> 00:52:41.079 it's i mean works just great yep yeah yeah okay 00:52:41.079 --> 00:52:44.280 and um what's the color scheme that you're using 00:52:44.280 --> 00:52:49.659 i'm a tokenite user so fall killed away okay 00:52:49.659 --> 00:52:55.519 looks quite cool yep okay and um let's see the 00:52:55.519 --> 00:52:57.699 tool that you use to push to version control 00:52:57.699 --> 00:53:01.110 we already know you use lazy git most of the 00:53:01.110 --> 00:53:05.949 times right exactly i just command g and then 00:53:05.949 --> 00:53:09.429 usually g afterwards to go into laser git and 00:53:09.429 --> 00:53:12.250 uh basically this is what i do go between gh 00:53:12.250 --> 00:53:17.769 dash and laser kit okay okay wonderful and um 00:53:17.769 --> 00:53:26.769 tmux why tmux uh wow tmux is a love story no 00:53:26.769 --> 00:53:34.090 i love tmux um Basically, I think before all 00:53:34.090 --> 00:53:36.630 the terminal emulators had proper tabs and windows 00:53:36.630 --> 00:53:42.130 and stuff like that, I started using Tmux. And 00:53:42.130 --> 00:53:43.889 then I actually found myself going through a 00:53:43.889 --> 00:53:46.750 lot of terminals. So I tried Kitty and Westterm 00:53:46.750 --> 00:53:55.800 and iTerm in the long distance past. TMAX always 00:53:55.800 --> 00:53:59.079 enabled me to maintain my workflow. It's the 00:53:59.079 --> 00:54:03.239 same in every terminal that I use. And I find 00:54:03.239 --> 00:54:10.079 it a pretty awesome experience. You can customize 00:54:10.079 --> 00:54:14.119 it. I customize it at home. I don't use the prefix 00:54:14.119 --> 00:54:22.480 of TMAX. I use command keybinds. By using, like, 00:54:22.480 --> 00:54:27.059 my... You do the send keys thing there? Yeah, 00:54:27.579 --> 00:54:30.239 so I use ghosty, and ghosty has... I think a 00:54:30.239 --> 00:54:34.099 lot of the terminals have these keybinds stuff. 00:54:34.219 --> 00:54:38.699 So basically, it sends the text, this is my prefix 00:54:38.699 --> 00:54:43.719 key, and then, like, to close the tab, it's X 00:54:43.719 --> 00:54:49.139 afterwards. this is control a basically and then 00:54:49.139 --> 00:54:52.940 it sends x to file off the the relevant tmux 00:54:52.940 --> 00:54:58.780 command to close the tab um yeah it works great 00:54:58.780 --> 00:55:01.199 like even like switching between tabs i have 00:55:01.199 --> 00:55:04.000 it bound to command and then the number like 00:55:04.000 --> 00:55:07.420 in the browser where we go through tabs okay 00:55:07.420 --> 00:55:10.340 uh yeah there's a keybind for everything pretty 00:55:10.340 --> 00:55:14.519 much man here that files i'm gonna be a scavenger 00:55:14.519 --> 00:55:17.320 there because I'm pretty sure I'm going to be 00:55:17.320 --> 00:55:19.420 able to find a lot of useful information. And 00:55:19.420 --> 00:55:25.420 don't even doubt that the people in Discord is 00:55:25.420 --> 00:55:29.559 going to be all over your .files. Oh, yeah, .files. 00:55:30.159 --> 00:55:34.219 Yeah. Those guys are professional scavengers, 00:55:34.260 --> 00:55:36.619 so they'll go in there and just copy everything 00:55:36.619 --> 00:55:41.199 and then call it their own. Yeah, yeah, I do 00:55:41.199 --> 00:55:45.420 that all the time, yeah. How do you do that in 00:55:45.420 --> 00:55:49.440 Tmux? In Tmux, did you configure something special 00:55:49.440 --> 00:55:58.980 for these keys? Yeah, so sometimes they need 00:55:58.980 --> 00:56:08.760 to work in tandem together. So I bound G to open. 00:56:08.900 --> 00:56:13.460 I don't use this one. I think I use GH dash. 00:56:14.139 --> 00:56:18.380 Yeah, so command shift G is basically opening 00:56:18.380 --> 00:56:24.079 GH dash. So I had to configure it here and then 00:56:24.079 --> 00:56:29.800 also in... In Ghosty. In Ghosty, exactly. So 00:56:29.800 --> 00:56:33.539 Ghosty sends the capital G, right? And then you 00:56:33.539 --> 00:56:37.719 pick that in Tmux. Yeah. That's why you have... 00:56:37.719 --> 00:56:40.780 Ghosty sends the prefix of Tmux, which is control 00:56:40.780 --> 00:56:45.309 A and then capital G. And then... tmax as it 00:56:45.309 --> 00:56:49.750 bound to capital G, to prefix capital G, then 00:56:49.750 --> 00:56:54.010 it executes. I think I needed to do something. 00:56:54.269 --> 00:56:57.570 Let's see. I think I did something similar a 00:56:57.570 --> 00:57:02.230 few days ago. Here's my ghosty config. Where 00:57:02.230 --> 00:57:06.409 is it? Oh, no. Yep. I was trying to do control 00:57:06.409 --> 00:57:11.539 enter, but I couldn't, right? Because... Go see 00:57:11.539 --> 00:57:14.599 sense these characters when I do ctrl enter I 00:57:14.599 --> 00:57:17.239 couldn't pick up that any of them because I wanted 00:57:17.239 --> 00:57:20.940 to do this. Let me show you here There's something 00:57:20.940 --> 00:57:27.440 in emacs Is it test markdown I Wanted to create 00:57:27.440 --> 00:57:30.639 another heading if I'm here, right? I don't want 00:57:30.639 --> 00:57:33.579 to go to the section below because I have headings 00:57:33.579 --> 00:57:37.099 here right inside So I just wanted to hit ctrl 00:57:37.099 --> 00:57:40.090 enter and for it to create another heading so 00:57:40.090 --> 00:57:47.329 i can start typing right so i had to to come 00:57:47.329 --> 00:57:50.289 up because if i didn't do this what i usually 00:57:50.289 --> 00:57:55.969 did is go here go all the way here and then create 00:57:55.969 --> 00:57:59.710 the heading here and it's just too slow right 00:57:59.710 --> 00:58:04.329 so with this um control enter thing that i did 00:58:04.329 --> 00:58:08.969 where is it just gonna delete this um and tmux 00:58:13.380 --> 00:58:23.159 where is it enter this one yep so control enter 00:58:23.159 --> 00:58:26.320 since this and it works quite well i knew of 00:58:26.320 --> 00:58:29.059 him it was pretty simple but it took me a while 00:58:29.059 --> 00:58:31.739 to figure it out because ghosty was sending this 00:58:31.739 --> 00:58:35.480 and um i didn't know i didn't know how to yeah 00:58:35.480 --> 00:58:39.400 yeah it takes a while to figure out i think actually 00:58:39.400 --> 00:58:43.960 i use kitty for figuring out like what keys uh 00:58:43.960 --> 00:58:49.719 i think it has like kitten if you know what it 00:58:49.719 --> 00:58:53.460 means i don't know yeah show key exactly and 00:58:53.460 --> 00:58:56.820 then if you press uh ctrl enter i don't know 00:58:56.820 --> 00:59:00.239 why it's not working but oh i don't have it installed 00:59:00.239 --> 00:59:02.960 properly but if you if you run this on your machine 00:59:02.960 --> 00:59:05.920 and then you type whatever you want it actually 00:59:05.920 --> 00:59:09.940 shows you like the keys that you pressed, like 00:59:09.940 --> 00:59:14.800 their codes. Oh, you can do that with cat, actually. 00:59:14.940 --> 00:59:19.960 If you do... Let's try it and let's see. I have 00:59:19.960 --> 00:59:24.639 it documented here somewhere. Where is it? Let's 00:59:24.639 --> 00:59:26.480 see if it works on your side. I just want to 00:59:26.480 --> 00:59:30.539 see. But I have it in my .files. So this is the 00:59:30.539 --> 00:59:36.219 way that I did it. Yep. So let me just close 00:59:36.219 --> 00:59:39.769 out of here. I don't know why it does not find 00:59:39.769 --> 00:59:42.750 cats if I run it without bin at the beginning. 00:59:43.489 --> 00:59:45.909 So I just had to run it. I think I have to do 00:59:45.909 --> 00:59:48.750 it as well because I have a fish abbreviation 00:59:48.750 --> 00:59:52.349 for cat that makes it, that changes it to bat. 00:59:53.170 --> 00:59:54.969 That could be why. Which is like the fancy cat. 00:59:55.750 --> 01:00:01.530 That could be why you're right. Yep. So it works 01:00:01.530 --> 01:00:05.050 with this by running it like this, shows you 01:00:05.050 --> 01:00:07.909 the keys. But I think... I do have that as well. 01:00:07.969 --> 01:00:14.909 Let me see. Oh, I just... Not fixed my .chrc 01:00:14.909 --> 01:00:17.349 file because I don't have a single file. I mean, 01:00:17.349 --> 01:00:20.769 I have a lot of different files. But I think 01:00:20.769 --> 01:00:27.070 I have it in... Where could it be? This is why 01:00:27.070 --> 01:00:30.369 I like mini .files .preview because it gives 01:00:30.369 --> 01:00:33.030 me an idea like... Oh, it could be in this file. 01:00:33.130 --> 01:00:35.670 I wish I could scroll here, but it's not possible. 01:00:35.829 --> 01:00:40.610 I asked H .S. Nobsky if that would be possible, 01:00:40.750 --> 01:00:45.070 but no, it's not possible at all. Yeah. Where 01:00:45.070 --> 01:00:49.590 did I store that? Man, I don't remember. But 01:00:49.590 --> 01:00:55.849 it's somewhere in my .files. Yep. Yeah. Oh, yeah, 01:00:55.909 --> 01:00:58.650 I tried running bin slash bin slash cat and then 01:00:58.650 --> 01:01:00.730 pressing control enter, but I don't see anything. 01:01:01.449 --> 01:01:05.809 Like if I press another key, I do see it. Oh, 01:01:05.809 --> 01:01:12.429 this is control V. Oh, okay. So it works for 01:01:12.429 --> 01:01:16.030 some of them. Yeah, yeah. Maybe control enter, 01:01:16.110 --> 01:01:20.690 I think, is like a special key that terminal 01:01:20.690 --> 01:01:23.269 emulators don't really like. I think there's 01:01:23.269 --> 01:01:26.309 some kind of... There's a few keys that terminal 01:01:26.309 --> 01:01:28.929 emulators don't like, yeah. Yeah, it took me 01:01:28.929 --> 01:01:32.050 like... two hours to try to figure that out you 01:01:32.050 --> 01:01:34.889 know i was like but i want to use because emacs 01:01:34.889 --> 01:01:37.750 does that right so in emacs you press ctrl enter 01:01:37.750 --> 01:01:40.429 and that is the key that creates a new heading 01:01:40.429 --> 01:01:42.829 below i was like but i want to do it the same 01:01:42.829 --> 01:01:45.769 way because if i ever switch to emacs i don't 01:01:45.769 --> 01:01:48.550 want to do things differently there what are 01:01:48.550 --> 01:01:51.469 your thoughts on emacs have you yeah i understand 01:01:51.469 --> 01:01:56.760 that you're lying tmax maybe yeah you're eyeing 01:01:56.760 --> 01:02:00.840 t -max to maybe switch to it someday these are 01:02:00.840 --> 01:02:06.239 the vibes i'm getting yeah um not fully switched 01:02:06.239 --> 01:02:10.579 to emacs you know but i think it's interesting 01:02:10.579 --> 01:02:13.980 if you do it for your notes for example because 01:02:13.980 --> 01:02:17.400 i like taking a lot of notes that's my my thing 01:02:17.400 --> 01:02:20.429 i'm on the infrastructure side of things i like 01:02:20.429 --> 01:02:23.210 taking notes not because i like notes it's because 01:02:23.210 --> 01:02:26.070 i know myself and i will not remember stuff in 01:02:26.070 --> 01:02:29.449 three months right so i don't wanna go through 01:02:29.449 --> 01:02:32.710 documentation again because it takes time right 01:02:32.710 --> 01:02:36.190 if i have it in my notes two minutes and i just 01:02:36.190 --> 01:02:38.489 refreshed my memory and i can do it quite fast 01:02:38.489 --> 01:02:41.650 but that's the reason why i do notes and i think 01:02:41.650 --> 01:02:46.900 emacs it's not a bad idea for your notes and 01:02:46.900 --> 01:02:50.659 organizing your stuff like the calendar and all 01:02:50.659 --> 01:02:53.519 that stuff the settle casting method i could 01:02:53.519 --> 01:02:57.019 probably use settle casting there because i had 01:02:57.019 --> 01:03:00.820 a call with dina he uses he was a huge neobim 01:03:00.820 --> 01:03:04.000 user that moved to yeah i watched that yeah how 01:03:04.000 --> 01:03:09.530 did you feel No, I think, honestly, Emacs is 01:03:09.530 --> 01:03:14.349 a better software for writing notes because internal 01:03:14.349 --> 01:03:16.829 emulators, you don't have variable font sizes. 01:03:17.010 --> 01:03:23.389 And I think text hierarchy really helps with 01:03:23.389 --> 01:03:28.809 the readability of notes. And then you can always, 01:03:28.949 --> 01:03:33.489 like, I hear the integration of NeoVim inside 01:03:33.489 --> 01:03:38.030 Emacs is pretty good. So I can totally understand 01:03:38.030 --> 01:03:42.409 why. If you're mainly a writer, I think it's 01:03:42.409 --> 01:03:45.110 probably a better experience. But for coding, 01:03:45.210 --> 01:03:49.889 I think NeoVim does the job really well. Yeah. 01:03:50.289 --> 01:03:54.489 And I always think, like, why one? Why not the 01:03:54.489 --> 01:03:56.750 two, right? I mean, it's double configuration. 01:03:56.849 --> 01:03:59.789 You need to configure both of them and maintain 01:03:59.789 --> 01:04:04.110 both of them, which is more work. It's two different 01:04:04.110 --> 01:04:06.570 tools that you can use for two different purposes, 01:04:06.769 --> 01:04:10.190 right? If I ever decide a code, of course I'm 01:04:10.190 --> 01:04:12.510 going to be using UBM. But for my notes and all 01:04:12.510 --> 01:04:15.230 that stuff, I could probably use Emacs. I don't 01:04:15.230 --> 01:04:18.289 know. I'm just thinking about it and we'll see. 01:04:19.289 --> 01:04:22.190 Yeah, it depends on how hard it is to maintain 01:04:22.190 --> 01:04:26.429 the configuration because you probably know yourself 01:04:26.429 --> 01:04:29.070 and you probably need to customize it exactly 01:04:29.070 --> 01:04:34.559 to your liking. Yeah. That is the reason that 01:04:34.559 --> 01:04:38.579 I haven't opened D -Max. Because I know that 01:04:38.579 --> 01:04:41.699 once I open it, it's just not going to stop. 01:04:41.900 --> 01:04:44.019 And it's just going to be like two, three months 01:04:44.019 --> 01:04:47.539 of tweaking it to my liking. I don't want to 01:04:47.539 --> 01:04:52.800 go through that. And so going back to T -Max, 01:04:52.880 --> 01:04:56.119 then what else do you use T -Max for? So you 01:04:56.119 --> 01:05:00.340 use it to switch between windows. You said that 01:05:00.340 --> 01:05:03.409 you don't use panes too much. what about sessions 01:05:03.409 --> 01:05:08.750 do you use sessions yeah i actually use uh sesh 01:05:08.750 --> 01:05:11.769 by josh medesky was on your uh youtube channel 01:05:11.769 --> 01:05:18.050 so i use that to if i need to navigate to some 01:05:18.050 --> 01:05:21.190 session that isn't my last one because for my 01:05:21.190 --> 01:05:24.949 last one i have a key binding to switch between 01:05:24.949 --> 01:05:27.969 the last two sessions and also the last two windows 01:05:27.969 --> 01:05:31.559 in in the same session so i usually rely heavily 01:05:31.559 --> 01:05:33.800 on that but if i need to go something further 01:05:33.800 --> 01:05:38.380 in the past like i i use uh command k i have 01:05:38.380 --> 01:05:42.239 it bound to command k and yeah it's pretty uh 01:05:42.239 --> 01:05:51.780 smooth um yeah okay and then yeah go ahead i'm 01:05:51.780 --> 01:05:56.119 sorry uh yeah i just wanted to add that uh like 01:05:56.119 --> 01:06:00.039 i i if i have more than two windows in the same 01:06:00.039 --> 01:06:01.960 session i use the numbers like in the browser 01:06:01.960 --> 01:06:08.219 uh okay yeah okay so each session that you have 01:06:08.219 --> 01:06:13.659 is it a github repo is it yeah it's exactly yeah 01:06:13.659 --> 01:06:16.260 it's a github repo and then i usually have like 01:06:16.260 --> 01:06:21.239 um a window for my shell, a window for Neovim, 01:06:21.340 --> 01:06:23.800 and then a window for my build process or gh 01:06:23.800 --> 01:06:29.960 - or stuff like that. And then I just jam between 01:06:29.960 --> 01:06:33.519 them. I like my stuff to be full screen, basically. 01:06:33.840 --> 01:06:37.300 I have one monitor. It runs one application at 01:06:37.300 --> 01:06:41.079 the front. And then I usually look at one window 01:06:41.079 --> 01:06:45.400 because if it's too many, like if I open panes 01:06:45.400 --> 01:06:48.940 and stuff, I find it usually is a distraction 01:06:48.940 --> 01:06:52.619 for me. It's very hard for me to focus on one 01:06:52.619 --> 01:06:56.800 task. I agree. Completely agree. We have a very 01:06:56.800 --> 01:07:03.179 similar workflow, to be honest. Yep. And do you 01:07:03.179 --> 01:07:06.219 have keys for the sessions that you use the most? 01:07:06.380 --> 01:07:08.599 Like, let's say that you need to go to, I don't 01:07:08.599 --> 01:07:11.260 know, th - to the project itself, and you're 01:07:11.260 --> 01:07:14.719 working on it a lot. Do you have a key for it, 01:07:14.760 --> 01:07:17.920 or do you use sesh? Yeah, no, I don't have keys. 01:07:18.000 --> 01:07:22.719 I usually use sesh for that. Yeah, if I'm at 01:07:22.719 --> 01:07:26.019 work, I usually work on one session because it's 01:07:26.019 --> 01:07:29.639 a monorepo. If I work on gh -, I usually just 01:07:29.639 --> 01:07:35.440 use that session. So I don't find myself switching 01:07:35.440 --> 01:07:39.199 too many sessions. If I'm going to work on my 01:07:39.199 --> 01:07:42.679 notes inside NeoVim and not Obsidian, then I 01:07:42.679 --> 01:07:45.000 would have to find a solution for it because... 01:07:45.230 --> 01:07:47.050 I would probably want to have a single keybind. 01:07:47.550 --> 01:07:50.190 Just like I'm going between my browser and my 01:07:50.190 --> 01:07:53.329 terminal, I want to have a keybind for my notes. 01:07:54.230 --> 01:07:58.889 And then I might use Neovide so it has a separate 01:07:58.889 --> 01:08:05.489 keybind. I did see your solution of using chords, 01:08:05.769 --> 01:08:09.809 I think. And that's also a possible solution, 01:08:09.989 --> 01:08:15.039 like a prefix and then a key. Oh, okay. Of using 01:08:15.039 --> 01:08:20.159 what, you said? Chords? Are they called? I don't 01:08:20.159 --> 01:08:26.279 know. Yep. Hyper sublayers, right? Hyper sublayers. 01:08:26.399 --> 01:08:31.840 Yep, yep. So, yep. That's how I basically switch 01:08:31.840 --> 01:08:36.899 the scenes here. That's how I basically navigate 01:08:36.899 --> 01:08:42.380 my entire setup, right? So, nodes .files, home 01:08:42.380 --> 01:08:46.920 directory. block post, you know, scenes, I need 01:08:46.920 --> 01:08:51.539 to switch. So I'm already used to all of that. 01:08:52.439 --> 01:08:54.840 Yeah, I think if you cross a certain threshold 01:08:54.840 --> 01:08:57.779 of keybinds, then you have to go for a solution 01:08:57.779 --> 01:09:01.340 like that. But I like the way that it's instant. 01:09:01.439 --> 01:09:04.000 If you just press a single key and not have to 01:09:04.000 --> 01:09:06.859 press the prefix first, like this is how I made 01:09:06.859 --> 01:09:10.000 my TMAX thing work. I just press command T, I 01:09:10.000 --> 01:09:13.760 don't have to press. a sublayer to open it so 01:09:13.760 --> 01:09:16.600 I can spam it. I don't know, it's easier for 01:09:16.600 --> 01:09:20.779 me. But people use tmux with prefix. I think 01:09:20.779 --> 01:09:24.079 this is the most common way people use tmux. 01:09:24.220 --> 01:09:27.260 So I guess it's just a matter of getting used 01:09:27.260 --> 01:09:30.600 to. But if I'm going to run out of keymaps... 01:09:30.890 --> 01:09:34.270 It's going to be an issue. I don't like the prefix. 01:09:34.550 --> 01:09:37.569 I did try it for some time, but it's like you 01:09:37.569 --> 01:09:40.750 have to press the prefix and then another key. 01:09:40.810 --> 01:09:45.489 No, I just, I don't like it at all. And this 01:09:45.489 --> 01:09:48.850 feels, yeah, you mentioned like a chord, right? 01:09:48.909 --> 01:09:53.189 So I never just lift my fingers, right? So hyper 01:09:53.189 --> 01:09:56.869 A, just leave them pressed and then. k for my 01:09:56.869 --> 01:10:00.510 browser right or oh okay j for my terminal so 01:10:00.510 --> 01:10:03.069 it feels like a single key map right it's a key 01:10:03.069 --> 01:10:05.989 map of three keys basically right because we're 01:10:05.989 --> 01:10:09.130 used to key maps of two keys right ctrl a or 01:10:09.130 --> 01:10:13.289 whatever but this is well no command shift a 01:10:13.850 --> 01:10:15.670 it's something like that you know it's similar 01:10:15.670 --> 01:10:19.149 to any other key map of three keys right so oh 01:10:19.149 --> 01:10:22.149 yeah i figure it's it's probably a lot better 01:10:22.149 --> 01:10:24.470 than what i uh imagined because i imagined you 01:10:24.470 --> 01:10:26.409 pressing the prefix lifting your fingers and 01:10:26.409 --> 01:10:28.789 then there's this small delay that you that i 01:10:28.789 --> 01:10:32.630 hate and no yeah no no no yeah i would hate that 01:10:32.630 --> 01:10:36.289 i would definitely hate that but it's like any 01:10:36.289 --> 01:10:38.890 other key map in which you press three keys right 01:10:38.890 --> 01:10:42.319 so I'm going to switch to the guest scene right 01:10:42.319 --> 01:10:45.960 now in OBS. So it's hyper O. I remember that, 01:10:46.039 --> 01:10:49.279 right? O is for OBS and G is to see the guests, 01:10:49.359 --> 01:10:52.020 right? So notice that I'm leaving pressed hyper 01:10:52.020 --> 01:10:56.079 O right now. And then I tap G. Now this looks 01:10:56.079 --> 01:10:58.699 awesome. Yeah, this looks awesome. I do have 01:10:58.699 --> 01:11:02.779 like, I have command shift Y for my snippets. 01:11:02.939 --> 01:11:06.079 So if I press command shift Y, it's three keys. 01:11:06.159 --> 01:11:10.029 So it's probably very same experience. yes exactly 01:11:10.029 --> 01:11:13.170 the same experience and the good thing is that 01:11:13.170 --> 01:11:17.649 you can specify where those keys are right because 01:11:17.649 --> 01:11:20.350 if i want to type command shift look at this 01:11:20.350 --> 01:11:24.069 my left hand command shift a that sucks my fingers 01:11:24.069 --> 01:11:28.569 are in a weird position but here my hyper is 01:11:28.569 --> 01:11:32.350 here on my thumb so hyper and then i just have 01:11:32.350 --> 01:11:38.020 my two my four fingers And I have a lot of combinations, 01:11:38.460 --> 01:11:40.699 right? Yeah, you basically have the key maps 01:11:40.699 --> 01:11:44.739 on separate hands and then you can easily reach 01:11:44.739 --> 01:11:49.180 the... Yeah, and I just remember A is for applications, 01:11:49.560 --> 01:11:52.300 right? So hyper A, this is for the terminal, 01:11:52.380 --> 01:11:57.020 which is what I use the most. Browser and YouTube 01:11:57.020 --> 01:12:02.340 and stuff like that, right? Or OBS or Tmux. If 01:12:02.340 --> 01:12:04.640 I want to switch to my Tmux sessions, it's hyper 01:12:04.640 --> 01:12:09.489 T. Right. So hybrid T this or this or this. Right. 01:12:09.569 --> 01:12:14.510 So that's how I use. So, yeah, I use I use option 01:12:14.510 --> 01:12:19.109 as my like prefix for applications. So my terminal 01:12:19.109 --> 01:12:22.470 is actually option I because I started up in 01:12:22.470 --> 01:12:28.210 I term and it stayed that way. Yeah. But the 01:12:28.210 --> 01:12:30.729 problem is that then you run out of keys. Right. 01:12:31.470 --> 01:12:34.500 Yeah. Yeah. Yeah. It'll get to a point in which 01:12:34.500 --> 01:12:37.960 you're like, I cannot introduce new key maps 01:12:37.960 --> 01:12:41.279 or I have to get really creative because I basically 01:12:41.279 --> 01:12:44.079 used all of them already. With sublayers, man, 01:12:44.340 --> 01:12:48.220 you have no... I don't think anyone actually 01:12:48.220 --> 01:12:52.899 uses all the sublayers. No, you have a lot of 01:12:52.899 --> 01:12:56.560 options. No, I think your setup is like the next 01:12:56.560 --> 01:12:59.520 level that I'm going to reach at some point. 01:13:00.140 --> 01:13:03.270 Use it and let me know. Everyone tells me it's 01:13:03.270 --> 01:13:06.989 over -engineered, but the first days, it's complicated 01:13:06.989 --> 01:13:09.569 because you're not used to it. But once you get 01:13:09.569 --> 01:13:13.050 used to it, man, you can do everything. Maybe 01:13:13.050 --> 01:13:16.689 the next app that I'm going to install and need 01:13:16.689 --> 01:13:19.489 to use, maybe I'll put it in a sublayer and then 01:13:19.489 --> 01:13:23.109 see if I can easily launch just that app and 01:13:23.109 --> 01:13:27.750 then gradually move over. Yeah, that's a good 01:13:27.750 --> 01:13:31.050 idea. Look at this one. I even have this hyper... 01:13:31.650 --> 01:13:36.750 S for system and T for tasks. I just needed to 01:13:36.750 --> 01:13:39.029 come up with something, right? And it shows me 01:13:39.029 --> 01:13:41.930 like a list of scripts that I can run. Like these 01:13:41.930 --> 01:13:44.869 scripts, I need to run them from time to time 01:13:44.869 --> 01:13:48.390 like this. You buy one, I need to run it every 01:13:48.390 --> 01:13:52.050 time you buy updates, right? I could do it automatically, 01:13:52.189 --> 01:13:55.109 but I just do it on my own. Or if I need to switch 01:13:55.109 --> 01:13:59.189 this in OBS. So, man, it's... i don't know i 01:13:59.189 --> 01:14:01.869 think you actually saved like a couple hundred 01:14:01.869 --> 01:14:04.810 dollars because you don't need to buy like the 01:14:04.810 --> 01:14:08.750 elgato streaming device you just have that is 01:14:08.750 --> 01:14:11.550 all your key maps in your keyboard yeah that 01:14:11.550 --> 01:14:14.449 is correct i don't need to buy any additional 01:14:14.449 --> 01:14:17.909 device you can manage obs with my keyboard pretty 01:14:17.909 --> 01:14:22.409 you know a pretty simple way and i have a video 01:14:22.409 --> 01:14:26.710 about it too i just I explained all of that in 01:14:26.710 --> 01:14:28.770 a video. If someone is interested in doing it, 01:14:28.869 --> 01:14:31.090 they're just going to go in and check that there. 01:14:31.470 --> 01:14:36.029 So let's talk about the OS. Notice that you're 01:14:36.029 --> 01:14:40.829 using macOS. Yeah. Want to share on that? Why 01:14:40.829 --> 01:14:46.170 macOS and why not Linux? I think it's the classic 01:14:46.170 --> 01:14:48.869 story. I started out on Windows because I wanted 01:14:48.869 --> 01:14:53.850 to game, and then my first job gave me a Mac. 01:14:55.009 --> 01:15:00.109 And it can do everything basically in terms of 01:15:00.109 --> 01:15:07.170 being a Unix system. So it has a normal shell. 01:15:07.369 --> 01:15:10.850 So for a developer like me, it works perfectly. 01:15:13.050 --> 01:15:20.210 Yeah, regarding Linux, I think that I would want 01:15:20.210 --> 01:15:24.180 to try Linux someday because... you can customize 01:15:24.180 --> 01:15:27.300 it even further and even something like Nix works 01:15:27.300 --> 01:15:36.180 better on Linux. And it's also my values about 01:15:36.180 --> 01:15:43.020 supporting Linux and this cool company called 01:15:43.020 --> 01:15:46.119 Framework that develops laptops that are easy 01:15:46.119 --> 01:15:49.779 to upgrade and it fits my whole repairability 01:15:49.779 --> 01:15:53.250 and stuff like that. fits my values so i think 01:15:53.250 --> 01:15:56.829 i'm gonna try it one day but i think the downside 01:15:56.829 --> 01:15:59.529 of switching to something like that is that the 01:15:59.529 --> 01:16:05.090 performance of mac is is really good so if my 01:16:05.090 --> 01:16:09.590 job uh brings me uh you know five thousand dollars 01:16:09.590 --> 01:16:16.510 laptop i'm not gonna say uh no yeah yeah that's 01:16:16.510 --> 01:16:19.569 how i got started with mac os as well my previous 01:16:19.569 --> 01:16:23.449 job you know hey it you need to use a mac so 01:16:23.449 --> 01:16:26.510 i was like okay i'll give it a try they were 01:16:26.510 --> 01:16:31.050 intel based max back then yeah they got hot they 01:16:31.050 --> 01:16:34.109 were not yeah they were not good right but oh 01:16:34.109 --> 01:16:37.310 yeah the fan went crazy now yes really quiet 01:16:37.310 --> 01:16:41.609 um yeah it's a really good machine yeah the hardware 01:16:41.609 --> 01:16:45.670 is is wonderful and what are your thoughts on 01:16:45.670 --> 01:16:53.079 windows I do like what they've done in the last 01:16:53.079 --> 01:16:57.960 couple of years with the WSL, but the fact that 01:16:57.960 --> 01:17:03.140 it's not natively Unix -based basically leaves 01:17:03.140 --> 01:17:09.039 it to niches like word processing and video editing 01:17:09.039 --> 01:17:13.199 or gaming. And for developers, it's really not 01:17:13.199 --> 01:17:21.840 very well suited. I always wonder what, how the 01:17:21.840 --> 01:17:25.560 world would be if Microsoft would still have 01:17:25.560 --> 01:17:29.779 the Unix variant that they had at the beginning, 01:17:29.920 --> 01:17:32.979 right? Because they had this ZNX operating system 01:17:32.979 --> 01:17:38.020 and it was Unix based, but then they decided 01:17:38.020 --> 01:17:44.899 to go with their DOS thing and it just went downhill 01:17:44.899 --> 01:17:51.119 from there. I don't know. It's like a tech debt, 01:17:51.180 --> 01:17:58.899 I guess. It's like the Americans use the imperial 01:17:58.899 --> 01:18:01.779 system, right? I think it's called. And not the 01:18:01.779 --> 01:18:04.180 metric system. And it causes a lot of confusion 01:18:04.180 --> 01:18:07.199 around the world. And I think even a rocket once, 01:18:07.439 --> 01:18:10.119 like one of the Apollo missions, I think, crashed 01:18:10.119 --> 01:18:14.859 because of an error converting between the units. 01:18:14.979 --> 01:18:18.119 And I think... I see Windows in the same way. 01:18:18.359 --> 01:18:22.619 Like, if it had been Unix, it'd probably make 01:18:22.619 --> 01:18:28.859 a lot of stuff easier. Then, yeah, I guess the 01:18:28.859 --> 01:18:32.279 alternative future would have been better. Yeah. 01:18:32.779 --> 01:18:35.960 Do they regret it? Because now they're bringing 01:18:35.960 --> 01:18:41.260 Unix to Windows with WSL, right? And every developer 01:18:41.260 --> 01:18:45.229 that I know that uses Windows... If it's not 01:18:45.229 --> 01:18:47.470 developing for Windows, of course, because if 01:18:47.470 --> 01:18:49.869 you are, you're going to use Windows and all 01:18:49.869 --> 01:18:52.850 its apps and all that stuff. But most of the 01:18:52.850 --> 01:18:55.289 people that I talk to is like, yeah, I use Windows, 01:18:55.510 --> 01:18:59.029 but with WSL. So you're basically not using Windows. 01:18:59.109 --> 01:19:02.630 You're using Linux there, right? So I don't know 01:19:02.630 --> 01:19:06.130 how Microsoft feels about that decision. Do they 01:19:06.130 --> 01:19:09.890 feel like, man, we should have stuck to Unix? 01:19:10.010 --> 01:19:14.810 It's too late. It's too late. Yeah. yeah definitely 01:19:14.810 --> 01:19:20.029 okay and um we already talked about operating 01:19:20.029 --> 01:19:22.869 systems window manager what do you use on mac 01:19:22.869 --> 01:19:28.829 os oh yeah i use aerospace which is like i used 01:19:28.829 --> 01:19:31.930 to use uh your buy and then there was another 01:19:31.930 --> 01:19:34.909 one i don't remember his name but yeah i use 01:19:34.909 --> 01:19:38.069 aerospace but i use it in a very basic way because 01:19:38.069 --> 01:19:41.010 all my applications are full screen all the time 01:19:41.010 --> 01:19:45.060 so when i switch between them aerospace takes 01:19:45.060 --> 01:19:49.699 care of them being open. Even if I quit out of 01:19:49.699 --> 01:19:53.439 Arc and then open it, it's going to open full 01:19:53.439 --> 01:19:57.420 screen. And that's how I like using my... But 01:19:57.420 --> 01:20:03.199 if I work on, let's say, my website or something 01:20:03.199 --> 01:20:08.899 like that, and I want to open up DevTools, then 01:20:08.899 --> 01:20:16.720 I might use... Split. Yeah, split. Exactly. How 01:20:16.720 --> 01:20:20.180 do you do that? How do you manage it? Okay, I 01:20:20.180 --> 01:20:22.960 have a few questions here. Because I use Yabai 01:20:22.960 --> 01:20:26.020 in stack mode and basically the same way that 01:20:26.020 --> 01:20:28.979 you use it. Because I also believe that having 01:20:28.979 --> 01:20:31.079 more than one application on the screen is just 01:20:31.079 --> 01:20:33.600 going to distract you. That's why I don't use 01:20:33.600 --> 01:20:37.500 Tmux panes a lot or NeoVim splits or Windows 01:20:37.500 --> 01:20:40.659 or however they're called. i'm always focused 01:20:40.659 --> 01:20:44.699 on one right i cannot pay attention to two at 01:20:44.699 --> 01:20:48.319 the same time how do you do you open another 01:20:48.319 --> 01:20:50.899 workspace in which you have a different config 01:20:50.899 --> 01:20:53.800 and you can have two apps or how does that work 01:20:53.800 --> 01:20:59.600 with aerospace uh yes so in aerospace you you 01:20:59.600 --> 01:21:04.340 define uh workspace i think they're called um 01:21:07.399 --> 01:21:10.500 Yeah, so I have, like, basically, I have this 01:21:10.500 --> 01:21:14.739 bit of code that when Ghosty opens, it moves 01:21:14.739 --> 01:21:19.720 it to the I workspace. And then that makes sure 01:21:19.720 --> 01:21:23.920 that Ghosty is always there. And if I press option 01:21:23.920 --> 01:21:29.220 I, it basically just moves to that workspace. 01:21:29.420 --> 01:21:35.789 And yeah, this option I basically... opens up 01:21:35.789 --> 01:21:39.189 ghosty and moves it and then the the bit of code 01:21:39.189 --> 01:21:42.770 there moves it to the i workspace so when i switch 01:21:42.770 --> 01:21:49.770 to it when i switch to it it basically goes to 01:21:49.770 --> 01:21:51.850 the workspace that the application is open on 01:21:51.850 --> 01:21:54.470 and since i always open it on on the i workspace 01:21:54.470 --> 01:21:56.909 it goes to you can see it here it goes to the 01:21:56.909 --> 01:22:01.489 i workspace okay so you have one application 01:22:01.489 --> 01:22:05.770 for a workspace and right Yeah, yeah, exactly. 01:22:06.810 --> 01:22:10.550 Yeah, I also like having a nice background, so 01:22:10.550 --> 01:22:15.310 I like to have the terminal be the only application 01:22:15.310 --> 01:22:18.569 in this workspace. But if I go to my calendar, 01:22:18.810 --> 01:22:21.750 it usually has a bunch of applications stacked, 01:22:21.909 --> 01:22:25.409 but I don't really use that feature. I usually 01:22:25.409 --> 01:22:31.590 just go full screen. Okay, okay, I see. On each 01:22:31.590 --> 01:22:34.069 workspace, you have a different config, and in 01:22:34.069 --> 01:22:36.909 some workspaces, sometimes you open more than 01:22:36.909 --> 01:22:40.770 one application at a time. Yeah, yeah, basically, 01:22:40.949 --> 01:22:48.170 yeah. Oh, but you have to decide on which workspace 01:22:48.170 --> 01:22:50.810 each application is going to live. Isn't that 01:22:50.810 --> 01:22:55.250 a little bit more overhead? Like, why not use 01:22:55.250 --> 01:22:57.770 your buy -in stack mode, for example, right? 01:22:57.850 --> 01:23:00.010 Because you don't have to think about where... 01:23:00.220 --> 01:23:03.000 Each application lives. I just keep all of them 01:23:03.000 --> 01:23:05.960 in the same desktop. If I show you the apps that 01:23:05.960 --> 01:23:08.979 I have open here, if I bring up the macOS thingy, 01:23:09.060 --> 01:23:11.720 I hope I don't have anything that I shouldn't 01:23:11.720 --> 01:23:16.739 show there. No, I don't, it seems. But all of 01:23:16.739 --> 01:23:21.699 them are in the same desktop, right? So I don't 01:23:21.699 --> 01:23:24.159 move them to different desktops. I just switch 01:23:24.159 --> 01:23:30.229 between apps, basically, right? So why? Why do 01:23:30.229 --> 01:23:36.489 you use aerospace in that mode? So it's basically 01:23:36.489 --> 01:23:40.829 two reasons. I have my terminal. I like to show 01:23:40.829 --> 01:23:46.189 the background of my desktop. So this is one 01:23:46.189 --> 01:23:48.069 stupid reason. And the other one is basically 01:23:48.069 --> 01:23:51.529 when I'm in my browser and open up the developer 01:23:51.529 --> 01:23:55.630 tools, and then I like it to be side by side 01:23:55.630 --> 01:23:59.840 because you usually need to inspect. And if I 01:23:59.840 --> 01:24:02.380 had more applications opened in this workspace, 01:24:02.619 --> 01:24:11.659 it would show them, right? But if only my browser 01:24:11.659 --> 01:24:14.380 is in this workspace, I can easily go between 01:24:14.380 --> 01:24:20.159 full screen and tiled mode and easily switch 01:24:20.159 --> 01:24:25.470 between it. Makes sense. Yeah, it's not the most 01:24:25.470 --> 01:24:27.949 perfect solution because it leaves the browser 01:24:27.949 --> 01:24:31.890 pretty small and also the devtools are pretty 01:24:31.890 --> 01:24:35.090 small. They both need a lot of screen. Like if 01:24:35.090 --> 01:24:38.470 you go to the network tab and things start to 01:24:38.470 --> 01:24:42.989 get a little bit crammed, you know. It's not 01:24:42.989 --> 01:24:45.510 the perfect solution, but yeah. I'm still looking 01:24:45.510 --> 01:24:50.550 for one if you know. Yeah. Yeah, I debate that 01:24:50.550 --> 01:24:57.000 a lot. i don't know like for example right if 01:24:57.000 --> 01:25:05.960 i how would i do that let's see um so you just 01:25:05.960 --> 01:25:09.680 take this small window out of here into its own 01:25:09.680 --> 01:25:14.159 how do i do that here i have no idea like maybe 01:25:14.159 --> 01:25:21.029 here so i use this in mac os a lot and i know 01:25:21.029 --> 01:25:24.229 it's not the best uh way why is my camera looking 01:25:24.229 --> 01:25:27.170 like this this one the keyboard one it's not 01:25:27.170 --> 01:25:30.510 following my hands it's unfocused should i know 01:25:30.510 --> 01:25:35.189 this but i have a dedicated key like which is 01:25:35.189 --> 01:25:37.890 command tilde right but in my keyboard i have 01:25:37.890 --> 01:25:40.109 this key that i don't use for anything basically 01:25:40.109 --> 01:25:44.090 so i switch between that like the two instances 01:25:44.090 --> 01:25:47.539 of the same app I don't do web depth, so I'm 01:25:47.539 --> 01:25:50.420 not sure how comfortable someone would be like 01:25:50.420 --> 01:25:53.439 going here and scrolling and then coming here. 01:25:53.680 --> 01:25:56.739 Or if you need to have them side by side. Yeah, 01:25:56.859 --> 01:25:58.220 you need to have them side by side because you 01:25:58.220 --> 01:26:00.619 usually inspect an element and then you click 01:26:00.619 --> 01:26:03.619 that little arrow in the top left corner and 01:26:03.619 --> 01:26:05.359 then you choose the element you want to inspect 01:26:05.359 --> 01:26:07.899 and you usually change some CSS stuff and want 01:26:07.899 --> 01:26:12.649 to see it immediately reflect. And Chrome DevTools 01:26:12.649 --> 01:26:15.430 have some kind of hotkeys, like they have command 01:26:15.430 --> 01:26:20.090 shift P, which I use a lot to open up this command 01:26:20.090 --> 01:26:22.750 palette. And then I could usually type network 01:26:22.750 --> 01:26:26.369 and go to network, but it's not, I wish there 01:26:26.369 --> 01:26:29.529 was a two for it. Then you would know the key 01:26:29.529 --> 01:26:33.289 binds will be super comfortable. But yeah, I 01:26:33.289 --> 01:26:36.890 usually do tab tab and stuff like that and get 01:26:36.890 --> 01:26:41.630 to where I want, but it's not perfect. I still 01:26:41.630 --> 01:26:44.390 need to use my mouse to, you know, pick whatever 01:26:44.390 --> 01:26:48.029 I want to inspect. Stuff like that. Okay, makes 01:26:48.029 --> 01:26:51.710 sense. Yeah, I think the solution that I'm going 01:26:51.710 --> 01:26:58.409 to have to end up with is have two modes, basically, 01:26:58.590 --> 01:27:02.310 right? So, Yabai, I will probably have to run 01:27:02.310 --> 01:27:05.369 a script. Use Yabai in stack mode, but if I need 01:27:05.369 --> 01:27:07.979 to do that side -by -side thing... run another 01:27:07.979 --> 01:27:10.880 script that configures configures your buy in 01:27:10.880 --> 01:27:14.000 a different mode move stuff around i don't know 01:27:14.000 --> 01:27:17.340 i'll i'll have to think about it when it'll put 01:27:17.340 --> 01:27:21.500 a couple of hours into it yeah yeah yeah a couple 01:27:21.500 --> 01:27:24.560 of hours yeah okay why did you move away from 01:27:24.560 --> 01:27:30.560 your buy um i think you needed to disable system 01:27:30.560 --> 01:27:34.300 integrity or something to have to have the moving 01:27:34.300 --> 01:27:36.539 between applications be instant because it uses 01:27:36.539 --> 01:27:41.119 spaces under the hood, like macOS spaces. And 01:27:41.119 --> 01:27:44.680 then it had that small delay. And I've watched 01:27:44.680 --> 01:27:47.300 Linux videos where people just switch instantly 01:27:47.300 --> 01:27:52.140 between applications. And I wanted that to be 01:27:52.140 --> 01:27:56.000 instant. And the way that aerospace works, it 01:27:56.000 --> 01:28:00.060 basically just puts your applications at the 01:28:00.060 --> 01:28:03.409 bottom right corner. You can barely see them 01:28:03.409 --> 01:28:07.689 if you have more than one. But then it uses one 01:28:07.689 --> 01:28:11.289 workspace, one macOS space, and switching is 01:28:11.289 --> 01:28:16.250 instant. So, yeah, it's the little things. Yeah. 01:28:17.329 --> 01:28:20.449 I guess, yeah, but it works for me because I 01:28:20.449 --> 01:28:25.430 don't use macOS desktops. I keep everything in 01:28:25.430 --> 01:28:29.260 the same space. If I would have them in different 01:28:29.260 --> 01:28:33.760 desktops, I think probably would not work out 01:28:33.760 --> 01:28:40.319 quite well. Yeah. But yeah, I want to try aerospace. 01:28:41.500 --> 01:28:44.020 I want to install it. I want to do it live. Why 01:28:44.020 --> 01:28:47.300 so serious? He's a Discord user. He has to guide 01:28:47.300 --> 01:28:48.859 me through the process. We're going to do it 01:28:48.859 --> 01:28:51.640 live. I don't know when next week or someday 01:28:51.640 --> 01:28:54.000 if you want to join would be great. So you can 01:28:54.000 --> 01:28:58.930 just share. tips there as well and uh single 01:28:58.930 --> 01:29:03.470 monitor is there a reason for that uh yeah i 01:29:03.470 --> 01:29:06.710 think i have like uh something called hyper focus 01:29:06.710 --> 01:29:10.909 where i can i really if i focus on something 01:29:10.909 --> 01:29:15.409 i'm really focused into it and uh if if there's 01:29:15.409 --> 01:29:18.609 some noise from the outside i get totally thrown 01:29:18.609 --> 01:29:24.130 out of my focus um So that's the way I feel about 01:29:24.130 --> 01:29:27.949 multiple monitors. Basically, whenever I tried 01:29:27.949 --> 01:29:30.489 using two monitors, I've never looked at the 01:29:30.489 --> 01:29:32.890 other monitor or I find myself looking at the 01:29:32.890 --> 01:29:37.529 other monitor for 30 minutes with my neck bent 01:29:37.529 --> 01:29:43.470 like that and it would start hurting. Yeah, so 01:29:43.470 --> 01:29:45.609 basically I can only focus on one thing at a 01:29:45.609 --> 01:29:49.970 time. Otherwise, it's not working for me. Yeah. 01:29:51.529 --> 01:29:53.810 And when you use the laptop by itself, I guess 01:29:53.810 --> 01:29:57.149 you want to keep the same workflow, right? Desk 01:29:57.149 --> 01:30:00.390 or laptop and be as efficient just in the laptop, 01:30:00.550 --> 01:30:04.569 right? Yeah, that's something that I need to 01:30:04.569 --> 01:30:08.430 work on still. But I do use the Mac keyboard 01:30:08.430 --> 01:30:12.229 without any modifications. I can easily go between 01:30:12.229 --> 01:30:16.789 my Moonlander and my laptop. So if I go to a 01:30:16.789 --> 01:30:19.470 coffee shop and work from there, I just use my 01:30:19.470 --> 01:30:23.239 laptops. keyboard but if it's a longer session 01:30:23.239 --> 01:30:28.399 and i know that that i will get neck pain or 01:30:28.399 --> 01:30:33.520 hand pain then i would use my uh full -blown 01:30:33.520 --> 01:30:37.579 setup here that's one of the reasons why i don't 01:30:37.579 --> 01:30:40.680 use layers in my keyboard um because i could 01:30:40.680 --> 01:30:44.510 have a layer for the numbers right but I usually 01:30:44.510 --> 01:30:46.930 just unplug the computer and take it somewhere 01:30:46.930 --> 01:30:49.609 else and work there. And I want to have the same 01:30:49.609 --> 01:30:52.930 workflow, the exact same. I want to be as efficient, 01:30:53.149 --> 01:30:56.210 you know, as on my desk, as on the laptop by 01:30:56.210 --> 01:31:00.649 itself. So I use the numbers, you know, the traditional 01:31:00.649 --> 01:31:04.109 way. I use them in the laptop the same way. So 01:31:04.109 --> 01:31:08.510 I don't know. I'm kind of against layers in the 01:31:08.510 --> 01:31:12.409 keyboard because of that reason. But I don't 01:31:12.409 --> 01:31:17.199 know. yeah i get i get that i i think it's not 01:31:17.199 --> 01:31:21.560 that hard to have uh to be accustomed to both 01:31:21.560 --> 01:31:27.699 uh at the same time like i yeah i'm used to just 01:31:27.699 --> 01:31:31.319 pressing command one if i'm on my laptop then 01:31:31.319 --> 01:31:34.399 i'm gonna press it one way if i'm on my woundlander 01:31:34.399 --> 01:31:37.680 it just comes naturally um i don't know why it 01:31:37.680 --> 01:31:40.619 comes naturally but it works for me yeah yes 01:31:40.619 --> 01:31:44.520 so you got used to the two already Yeah, I think 01:31:44.520 --> 01:31:47.920 there are programs like Vial, I think one is 01:31:47.920 --> 01:31:49.979 called, that allows you to modify any keyboard, 01:31:50.119 --> 01:31:52.520 like even your built -in Mac keyboard. And then 01:31:52.520 --> 01:31:56.659 you can have a Vial configuration on top of your 01:31:56.659 --> 01:32:00.020 Moonlander configuration. So it would work the 01:32:00.020 --> 01:32:05.340 same. I might check it out. Yeah, that's what 01:32:05.340 --> 01:32:09.060 I want to do. If I create layers, I create them 01:32:09.060 --> 01:32:14.250 in software, in Karabiner. I have them both in 01:32:14.250 --> 01:32:18.189 the Club 80 and the Mac keyboard. I can use hyper 01:32:18.189 --> 01:32:21.310 sub layers in the Mac keyboard. So the workflow 01:32:21.310 --> 01:32:24.470 is the same, right? So if I type hyper A something 01:32:24.470 --> 01:32:26.970 on the Mac keyboard, it works. Because I do it 01:32:26.970 --> 01:32:30.930 in software. I don't do it in the hardware itself. 01:32:31.550 --> 01:32:36.149 And how do you feel when people send hello messages 01:32:36.149 --> 01:32:38.869 with the focus thing that you mentioned? Have 01:32:38.869 --> 01:32:41.930 you ever received messages that are just... hello 01:32:41.930 --> 01:32:46.409 in slack or any other tool and nothing else how 01:32:46.409 --> 01:32:49.189 does that make what do you mean what oh like 01:32:49.189 --> 01:32:52.029 oh someone reaches out yeah and they just type 01:32:52.029 --> 01:32:57.270 hello and that's it and you know i i do that 01:32:57.270 --> 01:33:00.470 sometimes too so i can't do it i can't blame 01:33:00.470 --> 01:33:03.229 other people if i usually do it i do it i do 01:33:03.229 --> 01:33:06.409 it like and because i'm typing a lot of messages 01:33:06.409 --> 01:33:09.510 and press enter enter to send a bunch of stuff 01:33:09.510 --> 01:33:15.010 i don't i hate slacks like it's not vim so you 01:33:15.010 --> 01:33:18.350 can't go up a line and down a line and bold and 01:33:18.350 --> 01:33:20.810 select and then you need to press shift and all 01:33:20.810 --> 01:33:23.789 those arrows uh so it's an item so i usually 01:33:23.789 --> 01:33:28.829 just spam messages yeah yeah because i don't 01:33:28.829 --> 01:33:32.529 know i guess it's a cultural thing right there's 01:33:32.529 --> 01:33:34.390 people that just send you a message hello trying 01:33:34.390 --> 01:33:38.420 to be nice but personally to me that's like yeah 01:33:38.420 --> 01:33:42.680 okay you got my attention now and uh now why 01:33:42.680 --> 01:33:45.920 did you send me the message like just hello standalone 01:33:45.920 --> 01:33:48.680 is not it's not okay just hello yeah nothing 01:33:48.680 --> 01:33:53.000 else and yeah 10 minutes 30 minutes after nothing 01:33:53.000 --> 01:33:56.460 else and it's like it just slows down like the 01:33:56.460 --> 01:33:59.979 the thing between you and the person yeah yeah 01:33:59.979 --> 01:34:05.399 okay it's um we've been here for almost two hours 01:34:05.399 --> 01:34:10.000 i'm gonna let you go everybody Is there? Yeah, 01:34:10.119 --> 01:34:13.779 time flies by. Pretty nice conversation, by the 01:34:13.779 --> 01:34:17.399 way. Do you want to talk about any of these that 01:34:17.399 --> 01:34:19.680 I have listed here? Do you want to talk terminal, 01:34:19.920 --> 01:34:23.920 keyboard? Yeah, AI. I guess I can talk about 01:34:23.920 --> 01:34:27.739 AI because I'm on the I'm on the hater side. 01:34:28.899 --> 01:34:33.720 Yeah. Everyone. I guess I can bring my hot take. 01:34:34.020 --> 01:34:40.920 Yeah, go on. Share us what you think of AI. Basically, 01:34:41.699 --> 01:34:46.760 I think it's a really big bubble because I think 01:34:46.760 --> 01:34:51.319 it has its use cases, but the tech community, 01:34:51.619 --> 01:34:55.340 like every other major technology, tries to jump 01:34:55.340 --> 01:34:59.000 on the bandwagon and integrate it even in use 01:34:59.000 --> 01:35:07.829 cases that aren't really suited for AI. And I 01:35:07.829 --> 01:35:11.970 personally don't really use AI. I did try Copilot. 01:35:12.010 --> 01:35:14.189 I used it for a full year because GitHub gives 01:35:14.189 --> 01:35:19.529 maintainers for free. If you have above a certain 01:35:19.529 --> 01:35:21.430 amount of styles, they give you a subscription 01:35:21.430 --> 01:35:26.130 for free, so I used it. And I found that it introduced 01:35:26.130 --> 01:35:31.770 bugs that it was really hard for me to find because 01:35:31.770 --> 01:35:35.229 it's not code I wrote. In a high -level glance, 01:35:35.329 --> 01:35:39.670 it looked okay. But then I'm like, God damn it, 01:35:39.670 --> 01:35:44.630 Copilot, why didn't I see it? It took me two 01:35:44.630 --> 01:35:50.930 hours to debug. And also, I think it robs you 01:35:50.930 --> 01:35:58.090 from learning. You basically are less engaged 01:35:58.090 --> 01:36:03.119 with your code and you're less engaged. You just 01:36:03.119 --> 01:36:09.159 basically, I think it lets you pump out a lot 01:36:09.159 --> 01:36:13.659 of code pretty fast, but you do it without actually 01:36:13.659 --> 01:36:17.319 gaining something from it. Or I think I see coding 01:36:17.319 --> 01:36:22.819 more like a craft. So I guess, yeah, it's my 01:36:22.819 --> 01:36:27.159 personal opinion, but yeah. And do you use AI 01:36:27.159 --> 01:36:32.329 or not at all? No, no, I'm pretty harsh about 01:36:32.329 --> 01:36:37.750 AI. Ask my friends and family. My wife says I'm 01:36:37.750 --> 01:36:41.750 radicalizing her against AI and people at work 01:36:41.750 --> 01:36:45.770 will laugh at her, stuff like that. Because she 01:36:45.770 --> 01:36:50.390 sometimes blurts out my opinions about AI and 01:36:50.390 --> 01:36:55.270 everyone around her are using AI pretty extensively. 01:36:56.189 --> 01:36:59.270 uh so it's kind of uh being a non -conformist 01:36:59.270 --> 01:37:03.390 to say something uh bad about ai but i'm still 01:37:03.390 --> 01:37:08.090 i'm sticking to it yeah oh okay okay and um do 01:37:08.090 --> 01:37:11.729 you think there are use cases when do you think 01:37:11.729 --> 01:37:17.850 um ai could be used by by someone or never people 01:37:17.850 --> 01:37:20.909 should never use ai is that your take like no 01:37:20.909 --> 01:37:26.590 one should use ai ever No, I don't think I can 01:37:26.590 --> 01:37:31.189 say that. I'm not someone who says something 01:37:31.189 --> 01:37:37.949 so black and white. I myself don't see a use 01:37:37.949 --> 01:37:41.770 case for me, but I guess people use the computer 01:37:41.770 --> 01:37:44.609 differently. But yeah, I personally won't use 01:37:44.609 --> 01:37:49.789 it for anything. Maybe, I guess it excels at 01:37:49.789 --> 01:37:52.970 side projects and hobby stuff that you just need 01:37:52.970 --> 01:37:57.239 to pump up. pump out a bunch of code and build 01:37:57.239 --> 01:38:00.720 out an mvp i guess it's really good at that um 01:38:00.720 --> 01:38:06.479 but anything remotely serious is is not or prototyping 01:38:06.479 --> 01:38:09.779 stuff right yeah exactly to come up with something 01:38:09.779 --> 01:38:12.239 quick that you need to show off but you don't 01:38:12.239 --> 01:38:17.220 really care about right um yep and the thing 01:38:17.220 --> 01:38:19.520 is that you cannot trust everything that it says 01:38:19.520 --> 01:38:22.119 right because it's just gonna come up with really 01:38:22.119 --> 01:38:25.119 dumb ideas and it's just gonna think it's right 01:38:25.119 --> 01:38:29.739 and it's just it's it's hard i guess even people 01:38:29.739 --> 01:38:32.180 use it without really understanding how it works 01:38:32.180 --> 01:38:35.779 so like a colleague of mine uh searched for uh 01:38:35.779 --> 01:38:42.260 an issue she had like the containers logs showed 01:38:42.260 --> 01:38:45.060 an error or something like that and she asked 01:38:45.060 --> 01:38:47.979 ChatGPT about it, and then she didn't find anything. 01:38:48.159 --> 01:38:50.739 And I looked at Google and found an issue, a 01:38:50.739 --> 01:38:54.560 GitHub issue, that a human wrote, and that was 01:38:54.560 --> 01:38:57.359 published a couple of months ago. So it's stuff 01:38:57.359 --> 01:39:00.079 you aren't going to find on these algorithms, 01:39:00.239 --> 01:39:03.739 because they're not trained on data that was 01:39:03.739 --> 01:39:08.359 so recently written. And also, there's something 01:39:08.359 --> 01:39:14.189 about having it written by a human. Gives you 01:39:14.189 --> 01:39:18.590 a lot more trust in what it wrote. It's not predicting 01:39:18.590 --> 01:39:22.630 the next world. It's actually understand the 01:39:22.630 --> 01:39:25.430 issue and had the same issue and frustration 01:39:25.430 --> 01:39:28.210 that you had. And he opened an issue about it. 01:39:28.310 --> 01:39:31.430 And went through the whole process and completely 01:39:31.430 --> 01:39:34.369 understands. And yeah, you identify with that. 01:39:34.470 --> 01:39:37.210 You understand the solution. I have found a lot 01:39:37.210 --> 01:39:39.609 of issues that way as well. Because at the beginning, 01:39:39.670 --> 01:39:44.680 I used to ask ChatGPT, right? And a few times 01:39:44.680 --> 01:39:48.819 it just made stuff up. And it made me look like 01:39:48.819 --> 01:39:52.180 a fool. Like the... What is this movie called? 01:39:53.220 --> 01:39:56.119 Nacho Libre. It's... Let me show it to you. Hold 01:39:56.119 --> 01:40:01.300 on. Where's my screen? Nacho Libre? Is that like 01:40:01.300 --> 01:40:06.479 an international movie? Yep, yep. It's with Jack 01:40:06.479 --> 01:40:11.300 Black. Where is it? Okay. I don't know if you've 01:40:11.300 --> 01:40:14.550 seen it or not. Oh, no. I'm going to watch it. 01:40:14.989 --> 01:40:18.609 It's funny. It's really funny. Yeah, it looks 01:40:18.609 --> 01:40:22.970 good. But, yeah, it didn't make me look like 01:40:22.970 --> 01:40:26.069 a fool. But, you know, suggest stuff that if 01:40:26.069 --> 01:40:28.210 you don't know what you're doing, you could suggest 01:40:28.210 --> 01:40:31.869 to someone else, and it's just nonsense. So I 01:40:31.869 --> 01:40:34.170 don't trust it anymore. If I need to search for 01:40:34.170 --> 01:40:36.529 something, I don't use ChatGPT. I just go to 01:40:36.529 --> 01:40:39.109 Google because I usually find the answer in a 01:40:39.109 --> 01:40:41.920 GitHub issue. Or Stack Overflow? I don't know 01:40:41.920 --> 01:40:43.899 what's going to happen with Stack Overflow. Oh 01:40:43.899 --> 01:40:47.300 yeah, GitHub issues are so underrated. I usually 01:40:47.300 --> 01:40:49.979 go straight to GitHub and then search for free 01:40:49.979 --> 01:40:53.060 text and then go to the Issues tab. And I usually 01:40:53.060 --> 01:40:57.859 find a solution there. And I find that ChatGPT 01:40:57.859 --> 01:41:01.680 and stuff like that are good when you know what 01:41:01.680 --> 01:41:03.840 you're talking about so you can verify what the 01:41:03.840 --> 01:41:07.500 LLM is saying. If it's something that you don't 01:41:07.500 --> 01:41:11.279 understand at all, I think it's... You can't 01:41:11.279 --> 01:41:13.779 verify what it's saying, so you probably just 01:41:13.779 --> 01:41:18.960 accept stuff that are wrong. Yep, yep. And one 01:41:18.960 --> 01:41:24.119 question, in GH - can you search for GitHub repos 01:41:24.119 --> 01:41:28.479 and all that stuff? No, you can't search for 01:41:28.479 --> 01:41:32.180 repos, but you can just search for issues, like 01:41:32.180 --> 01:41:41.090 if you just search for... Yep. If you just search 01:41:41.090 --> 01:41:44.409 for Docker error or something like that, it's 01:41:44.409 --> 01:41:49.029 going to search through all the repos, but you 01:41:49.029 --> 01:41:52.909 can always add like Docker, Docker, I think it's 01:41:52.909 --> 01:41:55.329 the repo or something like that. No, but you 01:41:55.329 --> 01:41:58.329 can always write up the repo that you're looking 01:41:58.329 --> 01:42:03.130 for and search for that. So the horrible experience 01:42:03.130 --> 01:42:06.010 that you get when you go to GitHub and try to 01:42:06.010 --> 01:42:09.600 search for something. if i don't want to go to 01:42:09.600 --> 01:42:11.840 the browser i could search for stuff in here 01:42:11.840 --> 01:42:14.060 let's say that i want to just search in forks 01:42:14.060 --> 01:42:17.199 right so i i could as long as i know the query 01:42:17.199 --> 01:42:20.520 i can paste it in here and uh it's gonna find 01:42:20.520 --> 01:42:25.479 it can you save your queries or something yeah 01:42:25.479 --> 01:42:30.439 so these uh uh sections are saved queries uh 01:42:30.439 --> 01:42:33.539 but you can there's like a special tab here uh 01:42:33.539 --> 01:42:38.270 the search tab that keeps your last search. You 01:42:38.270 --> 01:42:40.810 can use it to search, and then it won't affect 01:42:40.810 --> 01:42:46.289 your other tabs, your other search queries. And 01:42:46.289 --> 01:42:48.609 you can always, if you use this query a lot, 01:42:48.689 --> 01:42:51.829 you can always put it in your json -config file, 01:42:52.050 --> 01:42:55.750 and it would be saved. So you can add in your 01:42:55.750 --> 01:43:00.819 config file, your JSON file. Yeah, exactly. Because 01:43:00.819 --> 01:43:04.000 I don't remember, like, to search only in Forex 01:43:04.000 --> 01:43:08.640 is a specific, you know, parameters that you 01:43:08.640 --> 01:43:10.319 need to pass. I don't remember those all the 01:43:10.319 --> 01:43:12.720 time. And it's like, man, I hate this because 01:43:12.720 --> 01:43:14.939 I have to go and search in the documentation. 01:43:15.279 --> 01:43:19.359 So if I could save those in my config file, that 01:43:19.359 --> 01:43:21.760 would be awesome. How do you save them? Yeah, 01:43:21.760 --> 01:43:25.619 exactly. So you basically, for PR, you define 01:43:25.619 --> 01:43:27.880 PR sections and then for each section you define 01:43:27.880 --> 01:43:32.720 a filter. This is my filter because I have one 01:43:32.720 --> 01:43:38.920 ER for VS Code that Microsoft never reviewed. 01:43:39.159 --> 01:43:42.420 So it's just open there forever. So I filter 01:43:42.420 --> 01:43:50.880 it out. But yeah, if I want to look at repos 01:43:50.880 --> 01:43:52.380 that are interesting to me, I don't want to type 01:43:52.380 --> 01:43:55.720 them over and over again. I just save them here 01:43:55.720 --> 01:43:59.619 and then I can take a look. yeah interesting 01:43:59.619 --> 01:44:06.300 okay wonderful okay thanks for sharing that and 01:44:06.300 --> 01:44:11.380 um last question and i'll let you go home lab 01:44:11.380 --> 01:44:14.319 because you like tweaking a lot it seems have 01:44:14.319 --> 01:44:16.180 you played with home labs or are you planning 01:44:16.180 --> 01:44:19.680 to yeah i really want to get into it because 01:44:19.680 --> 01:44:25.100 of all the subscriptions which got crazy So in 01:44:25.100 --> 01:44:28.260 order to watch like some of the more popular 01:44:28.260 --> 01:44:30.880 shows, you need to have like Apple and Disney 01:44:30.880 --> 01:44:34.560 Plus and Amazon. You need to have you need to 01:44:34.560 --> 01:44:38.840 pay for like it's become really aggressive. You 01:44:38.840 --> 01:44:40.840 need to pay a ton of money just to watch your 01:44:40.840 --> 01:44:42.760 favorite shows. If it's one show from Apple, 01:44:42.819 --> 01:44:44.859 you need to do a subscription to Apple. Yeah. 01:44:45.340 --> 01:44:48.680 And it's it's yeah, it's really a money grab. 01:44:49.159 --> 01:44:52.760 So. If I were to start a homelab, it's going 01:44:52.760 --> 01:44:58.739 to be mainly for watching stuff. I know a lot 01:44:58.739 --> 01:45:01.079 of people do crazy things with homelabs, but 01:45:01.079 --> 01:45:05.239 I haven't really dug into it. There are probably 01:45:05.239 --> 01:45:09.380 a lot of great use cases for it. Yeah. Yeah. 01:45:09.880 --> 01:45:15.159 Okay. Interesting. All right. So, Dolev, really 01:45:15.159 --> 01:45:19.000 appreciate your time. It's been two hours. Thanks 01:45:19.000 --> 01:45:22.460 for sharing. all of the stuff you're set up loved 01:45:22.460 --> 01:45:25.819 it was wonderful anything you want to share before 01:45:25.819 --> 01:45:30.199 we wrap it up uh no yeah i really enjoyed the 01:45:30.199 --> 01:45:33.479 conversation as well um i'm gonna steal some 01:45:33.479 --> 01:45:36.020 of your stuff as well now that you've explained 01:45:36.020 --> 01:45:40.880 how those layers work uh looks awesome and yeah 01:45:40.880 --> 01:45:43.989 it was a great time yep and if you ever have 01:45:43.989 --> 01:45:46.210 questions just let me know on discord and we 01:45:46.210 --> 01:45:48.529 can go live or something and i can just show 01:45:48.529 --> 01:45:51.050 you stuff around or we don't even have to go 01:45:51.050 --> 01:45:53.369 live you know we can just have a session and 01:45:53.369 --> 01:45:56.829 uh so yeah the discord community is awesome so 01:45:56.829 --> 01:46:02.109 yeah okay thanks for your time see you cool man 01:46:02.109 --> 01:46:03.449 bye bye