WEBVTT

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

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

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

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

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

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

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

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

00:00:23.239 --> 00:00:26.559
everyone, I have my friend here, Joshua Blaze.

00:00:27.230 --> 00:00:31.670
This is the second part of the Emacs video that

00:00:31.670 --> 00:00:35.390
I released a few days ago. How's it going, Josh?

00:00:36.170 --> 00:00:38.649
It's going pretty well, man. How are you? I'm

00:00:38.649 --> 00:00:41.969
doing good. Thanks for showing up, you know.

00:00:42.109 --> 00:00:44.630
Yeah, absolutely, man. You talk about Emacs,

00:00:44.710 --> 00:00:48.170
I'll be there. Yeah, thanks for helping me with

00:00:48.170 --> 00:00:52.070
Emacs, you know. The goal of the videos, the

00:00:52.070 --> 00:00:54.509
Emacs related videos, you know, is just so that

00:00:54.509 --> 00:00:57.799
people get to know it a little bit more. And

00:00:57.799 --> 00:01:00.340
they won't have the same questions that I have.

00:01:00.359 --> 00:01:03.219
So the questions that I will be asking are just

00:01:03.219 --> 00:01:07.920
beginner questions. And hopefully they will help

00:01:07.920 --> 00:01:10.640
people that is trying to get to know Emacs a

00:01:10.640 --> 00:01:14.920
little bit. Absolutely. Yeah. I mean, everybody

00:01:14.920 --> 00:01:17.739
was a beginner at one time. And I wish I had

00:01:17.739 --> 00:01:20.640
the resources that exist today because there's

00:01:20.640 --> 00:01:23.079
so many people that are actually putting out.

00:01:23.469 --> 00:01:25.530
really good content with regard to emacs and

00:01:25.530 --> 00:01:29.409
like when i started in probably 20 2017 2016

00:01:29.409 --> 00:01:31.670
there was almost nothing like you had to like

00:01:31.670 --> 00:01:35.069
freeball it and it was like it it was it was

00:01:35.069 --> 00:01:38.709
a journey to say the least how many hours did

00:01:38.709 --> 00:01:42.909
you spend how many months man i i gave up i also

00:01:42.909 --> 00:01:46.030
gave up so like i put probably i don't know i

00:01:46.030 --> 00:01:47.450
want to say i probably put like three months

00:01:47.450 --> 00:01:50.590
into it really hard and then i was like ah i'm

00:01:50.590 --> 00:01:52.450
just not making enough progress with it and i

00:01:52.450 --> 00:01:56.349
went back to vim and um that was like classic

00:01:56.349 --> 00:01:59.930
vim that wasn't neo vim uh back in the day i'm

00:01:59.930 --> 00:02:04.829
dating myself now i'm old and uh and i stayed

00:02:04.829 --> 00:02:06.909
with him for a couple years and then i went back

00:02:06.909 --> 00:02:10.430
to emacs when doom was kind of the big thing

00:02:10.430 --> 00:02:13.389
in 2020 i think is around when it really started

00:02:13.389 --> 00:02:17.300
to take off and uh there were guys like um uh

00:02:17.300 --> 00:02:20.819
distro tube that were doing stuff covering it

00:02:20.819 --> 00:02:23.639
and that's when i was like okay this makes a

00:02:23.639 --> 00:02:26.120
lot of sense i'm gonna put myself more into it

00:02:26.120 --> 00:02:28.060
and then became a full -time user and probably

00:02:28.060 --> 00:02:32.400
about 2020 2021 um was really when i like really

00:02:32.400 --> 00:02:35.639
gave it my all and have shifted almost all of

00:02:35.639 --> 00:02:40.379
my workflow over to it interesting okay yeah

00:02:40.379 --> 00:02:44.150
and now you're a full -time emacs then Yeah,

00:02:44.150 --> 00:02:47.509
yeah. I had a little bit of a spat with Neovim,

00:02:47.509 --> 00:02:50.750
as you saw with my video. That's how you found

00:02:50.750 --> 00:02:52.090
me, I think, back in the day. That's what caught

00:02:52.090 --> 00:02:55.150
my attention, yeah. About six months ago or so.

00:02:55.969 --> 00:02:58.150
You had an affair. It was a love affair. Exactly.

00:02:58.189 --> 00:03:02.310
It was an affair. And I came back and came back

00:03:02.310 --> 00:03:05.990
to my sweetie Emacs. And I've been loyal ever

00:03:05.990 --> 00:03:10.169
since. It was just a one -time mistake, right?

00:03:10.980 --> 00:03:14.099
Yeah, exactly. No, I still use NeoVim quite extensively

00:03:14.099 --> 00:03:17.259
like on the server and stuff. And like I said,

00:03:17.280 --> 00:03:20.939
I'm an evil mode user. So I know people that

00:03:20.939 --> 00:03:24.400
are like purists with Emacs will be like, this

00:03:24.400 --> 00:03:25.860
guy doesn't know what he's talking about. But

00:03:25.860 --> 00:03:28.599
I really love the Vim movements. It's just so

00:03:28.599 --> 00:03:31.020
ingrained into me from using Vim all that time.

00:03:32.159 --> 00:03:35.139
So yeah, like that's, I still use evil mode.

00:03:35.219 --> 00:03:37.860
I essentially use Vim inside Emacs. It's like

00:03:37.860 --> 00:03:42.280
inception. And what did your audience say when

00:03:42.280 --> 00:03:46.740
you switched to NeoVim? You know what? I had

00:03:46.740 --> 00:03:49.039
only really made like one or two videos about

00:03:49.039 --> 00:03:51.240
Emacs. One of them was about writing a book.

00:03:52.099 --> 00:03:54.900
And I think I had only made, seriously, maybe

00:03:54.900 --> 00:03:57.180
even just one video about Emacs. So I didn't

00:03:57.180 --> 00:04:01.099
have like this big, broad audience that was following

00:04:01.099 --> 00:04:03.659
Emacs. So it wasn't like this huge thing. But

00:04:03.659 --> 00:04:06.319
the comments on that NeoVim video really like,

00:04:06.419 --> 00:04:09.090
they kind of... I don't think I had got Emacs

00:04:09.090 --> 00:04:12.210
to the fullest extent until reading those comments.

00:04:12.409 --> 00:04:15.650
As soon as I saw these comments about like how

00:04:15.650 --> 00:04:18.970
it's this Lisp machine and how you're not really

00:04:18.970 --> 00:04:20.910
comparing apples to oranges when you're comparing,

00:04:21.149 --> 00:04:23.410
sorry, you are comparing apples to oranges when

00:04:23.410 --> 00:04:26.290
you're comparing NeoVim and Emacs. I was like,

00:04:26.329 --> 00:04:28.829
oh, I think I've been using it wrong this entire

00:04:28.829 --> 00:04:32.050
time. And it kind of, it sparked some stuff in

00:04:32.050 --> 00:04:34.089
me and that's kind of why it brought me back.

00:04:34.800 --> 00:04:37.560
Oh, but people didn't get upset or anything?

00:04:37.680 --> 00:04:41.800
I mean, people do their internet spat stuff.

00:04:42.040 --> 00:04:44.620
It's all in good jest, right? It's the holy war

00:04:44.620 --> 00:04:48.060
of Vim versus Emacs. But I don't know. I think

00:04:48.060 --> 00:04:51.240
there's space for both editors and there's a

00:04:51.240 --> 00:04:55.920
space for both methods of doing text manipulation.

00:04:56.579 --> 00:04:59.480
Emacs for me is just the way that I've started

00:04:59.480 --> 00:05:02.879
to use a computer. in whole like the holistic

00:05:02.879 --> 00:05:06.639
sense um in that it has replaced like all of

00:05:06.639 --> 00:05:10.819
my cli tui stuff and it's been centralized into

00:05:10.819 --> 00:05:14.199
emacs where it's actually people are going to

00:05:14.199 --> 00:05:15.779
be like what are you talking about when you say

00:05:15.779 --> 00:05:18.860
this but it's actually simplified things tremendously

00:05:18.860 --> 00:05:21.420
oh my daughter's screaming in the background

00:05:21.420 --> 00:05:24.339
yeah i don't know if you can hear that yeah a

00:05:24.339 --> 00:05:26.959
little bit i had a call with roman a few days

00:05:26.959 --> 00:05:30.790
ago and uh his baby was crying throughout the

00:05:30.790 --> 00:05:34.670
video but nice nice life yeah we all know how

00:05:34.670 --> 00:05:37.209
it is yeah a hundred percent i don't know if

00:05:37.209 --> 00:05:39.970
the audience knows how it is you know probably

00:05:39.970 --> 00:05:44.649
not who knows but they they will they will yeah

00:05:44.649 --> 00:05:49.829
eventually yeah and um all right so um let's

00:05:49.829 --> 00:05:53.389
see we already went through um getting to know

00:05:53.389 --> 00:05:56.110
you let me just share my screen real quick so

00:05:56.110 --> 00:06:02.110
that people can see um the previous video right

00:06:02.110 --> 00:06:05.430
so if you guys don't know josh you can go and

00:06:05.430 --> 00:06:07.790
watch this video we recorded it what two weeks

00:06:07.790 --> 00:06:11.629
ago and we went over yeah you know getting to

00:06:11.629 --> 00:06:13.569
know you a little bit more and all that stuff

00:06:13.569 --> 00:06:17.029
and um installation basically and we didn't do

00:06:17.029 --> 00:06:18.850
anything else in that video because we spent

00:06:18.850 --> 00:06:20.610
a lot of time talking at the beginning right

00:06:20.610 --> 00:06:25.829
so i think i want to skip all that part um right

00:06:25.829 --> 00:06:29.230
now and just jump right into it is there anything

00:06:29.230 --> 00:06:32.750
you want to discuss that is listed here before

00:06:32.750 --> 00:06:36.610
we jump right into emacs um i think we were going

00:06:36.610 --> 00:06:39.170
to do mostly org mode today so kind of like the

00:06:39.170 --> 00:06:42.050
what i would refer to as like the killer app

00:06:42.050 --> 00:06:43.949
of emacs and actually what had brought me to

00:06:43.949 --> 00:06:47.170
emacs in the first place um it's it's like a

00:06:47.170 --> 00:06:50.529
life organization system um is what you can use

00:06:50.529 --> 00:06:53.670
org mode for and it's something that has kind

00:06:53.670 --> 00:06:56.980
of brought a lot of people to emacs and keeps

00:06:56.980 --> 00:06:59.040
them there because it's like this it's like the

00:06:59.040 --> 00:07:02.879
apple walled garden of emacs where you like it's

00:07:02.879 --> 00:07:05.560
it's like the killer app and like you have to

00:07:05.560 --> 00:07:08.339
be there to use it if that makes sense yeah so

00:07:08.339 --> 00:07:11.300
yeah we'll we'll chat mostly about org mode today

00:07:11.300 --> 00:07:15.300
if that's cool i think all right all right so

00:07:15.300 --> 00:07:18.819
yeah arg mode um i'm i'm gonna skip all of the

00:07:18.819 --> 00:07:20.500
questions that i have here i don't know if you're

00:07:20.500 --> 00:07:23.899
able to see that on the screen but um Since we

00:07:23.899 --> 00:07:27.259
already covered this in the previous video, we

00:07:27.259 --> 00:07:29.220
didn't cover all of them because I added a few

00:07:29.220 --> 00:07:32.639
new questions, you know, but I'm not going to

00:07:32.639 --> 00:07:37.279
cover any of this. So let's jump right into it.

00:07:37.339 --> 00:07:39.779
You want to share my screen or you want to share

00:07:39.779 --> 00:07:42.439
yours to begin with? Do you want to start with

00:07:42.439 --> 00:07:45.360
mine and I'll kind of go over, I guess I'll kind

00:07:45.360 --> 00:07:48.139
of go over like what org mode is and then go

00:07:48.139 --> 00:07:51.819
from there? Yep, that's fine. Okay, is that zoomed

00:07:51.819 --> 00:07:54.019
in enough, would you say? It looks even one more

00:07:54.019 --> 00:07:56.720
at will. There you go. Okay. Yeah. So org mode

00:07:56.720 --> 00:08:01.379
is kind of, it's this markdown on steroids. I

00:08:01.379 --> 00:08:03.800
kind of mentioned in the previous video. And

00:08:03.800 --> 00:08:07.680
what you can really do with it is create a life

00:08:07.680 --> 00:08:09.519
organization system. And I think that's what

00:08:09.519 --> 00:08:12.699
a lot of people do with it. Not only that though,

00:08:12.759 --> 00:08:14.899
like you can use it for project management. You

00:08:14.899 --> 00:08:18.480
can use it for accounting. You can use it for

00:08:18.480 --> 00:08:20.860
pretty much anything. People even use it for

00:08:20.860 --> 00:08:24.529
writing code. in something called literate programming.

00:08:24.750 --> 00:08:28.050
It's kind of fallen out of style in recent decades,

00:08:28.250 --> 00:08:31.209
but back in the 80s and 90s, it was this huge

00:08:31.209 --> 00:08:33.169
thing where you essentially write your documentation

00:08:33.169 --> 00:08:38.009
inside your code and your code blocks live with

00:08:38.009 --> 00:08:40.070
that documentation and it's all like essentially

00:08:40.070 --> 00:08:45.259
amalgamated into a file together. Does that make

00:08:45.259 --> 00:08:47.899
sense? Yeah. Something similar to what you showed

00:08:47.899 --> 00:08:51.659
me in your blog post that that is your blog post

00:08:51.659 --> 00:08:54.620
is basically your Emacs configuration file. Right.

00:08:54.700 --> 00:08:56.539
So you don't have to keep stuff in two separate

00:08:56.539 --> 00:08:59.820
places. You got it. So if you actually I'll send

00:08:59.820 --> 00:09:01.740
you the link for that blog post if you want to

00:09:01.740 --> 00:09:03.460
put in this video. But like what it is, is my

00:09:03.460 --> 00:09:09.200
what we call literate config. So that is essentially

00:09:09.200 --> 00:09:13.820
my documentation as well as my. lisp code that

00:09:13.820 --> 00:09:18.220
makes my emacs work and run the way that it does

00:09:18.220 --> 00:09:22.279
so that's just one file and it's tangled into

00:09:22.279 --> 00:09:27.600
a it's essentially a org file so a dot org file

00:09:27.600 --> 00:09:31.600
and it's tangled into a dot el file which is

00:09:31.600 --> 00:09:37.220
lisp in In Emacs, Lisp is what is used for configuration

00:09:37.220 --> 00:09:39.639
and programming the editor. It's kind of like

00:09:39.639 --> 00:09:43.980
Lua for NeoVim. Yeah, you're familiar with Lua.

00:09:44.120 --> 00:09:46.279
I'm sure you are because you have quite the extensive

00:09:46.279 --> 00:09:50.080
configuration for NeoVim. So you know a little

00:09:50.080 --> 00:09:53.879
bit of Lua. A little bit, yeah. Yeah, so that's

00:09:53.879 --> 00:09:56.840
kind of the big killer feature of it. I'll kind

00:09:56.840 --> 00:10:01.090
of get into why it's so cool because... There's

00:10:01.090 --> 00:10:03.450
something called Org Agenda and Orgrom. There's

00:10:03.450 --> 00:10:06.549
a multitude of extensions that you can add on

00:10:06.549 --> 00:10:11.370
top of it that essentially allow you to do note

00:10:11.370 --> 00:10:14.830
-taking in a way that you can integrate PDFs

00:10:14.830 --> 00:10:19.409
or your eBooks. take notes directly in those

00:10:19.409 --> 00:10:23.649
files so it actually like links to the page where

00:10:23.649 --> 00:10:26.870
you took the file the uh note rather and it puts

00:10:26.870 --> 00:10:29.590
it into a org file so when you're like taking

00:10:29.590 --> 00:10:31.389
notes on a book for example you can have the

00:10:31.389 --> 00:10:33.409
book on one side you can have your notes on another

00:10:33.409 --> 00:10:36.029
and when you're writing notes they actually link

00:10:36.029 --> 00:10:38.669
to directly where you are in that book which

00:10:38.669 --> 00:10:42.889
is uh it's pretty pretty handy um if you if you're

00:10:42.889 --> 00:10:47.190
inclined to that direction but uh yeah like let's

00:10:47.190 --> 00:10:49.049
get into just kind of like some of the basics

00:10:49.049 --> 00:10:53.090
of org mode so like as we had spoke about previously

00:10:53.090 --> 00:10:57.110
like you're a markdown guy so you have asterisks

00:10:57.110 --> 00:11:02.029
instead of the uh hashes as your uh kind of your

00:11:02.029 --> 00:11:07.309
uh nested lists so that's List number one or

00:11:07.309 --> 00:11:09.850
level number one, level number two would be like

00:11:09.850 --> 00:11:12.389
a second asterisk. And you can essentially take

00:11:12.389 --> 00:11:15.970
these and go all the way down if you wanted to,

00:11:15.970 --> 00:11:18.889
to have nested, nested, nested, nested, nested

00:11:18.889 --> 00:11:21.710
lists, right? So that's like bullet points, right?

00:11:22.549 --> 00:11:24.850
Precisely. Yeah, they're like bullet points.

00:11:25.210 --> 00:11:27.230
Actually, not really like bullet points. They're

00:11:27.230 --> 00:11:28.850
actually more like headings. They're more like

00:11:28.850 --> 00:11:30.830
the hash headings. Oh, sorry, the markdown headings.

00:11:31.549 --> 00:11:34.860
Yes. Yeah, that's... That would be more akin

00:11:34.860 --> 00:11:36.740
to what these are. So these are essentially your

00:11:36.740 --> 00:11:38.879
headings, right? Because you can actually have

00:11:38.879 --> 00:11:41.840
bullet points within them, but we'll get into

00:11:41.840 --> 00:11:45.200
that. So I kind of wrote an example org file

00:11:45.200 --> 00:11:47.039
for us and I'll just kind of go through it. So

00:11:47.039 --> 00:11:51.279
this is kind of a to -do and you can see that

00:11:51.279 --> 00:11:54.980
it was wrapped when I opened it and closed it.

00:11:55.039 --> 00:11:58.000
And there are a list of things to do within that

00:11:58.000 --> 00:12:00.960
to -do, right? So you can almost think of it

00:12:00.960 --> 00:12:03.639
like a project. You have like a main project

00:12:03.639 --> 00:12:05.460
and then you have the things that you need to

00:12:05.460 --> 00:12:08.659
do underneath it that are potentially. And you

00:12:08.659 --> 00:12:11.940
can see like you can get quite nested with these

00:12:11.940 --> 00:12:17.940
different to do's and points. You see what I'm

00:12:17.940 --> 00:12:22.840
saying? Yeah, I get it. So so, for example, you

00:12:22.840 --> 00:12:26.940
have a main to do and then you have a thing that

00:12:26.940 --> 00:12:29.340
you need to do on top of that to do. And you

00:12:29.340 --> 00:12:32.389
have list within that. that you need to accomplish

00:12:32.389 --> 00:12:37.830
before that to do can be done. Right. So it's

00:12:37.830 --> 00:12:40.350
kind of like inception. You, you go down the

00:12:40.350 --> 00:12:42.830
list of like things that you potentially need

00:12:42.830 --> 00:12:46.490
to do in a day and you check them off and then

00:12:46.490 --> 00:12:49.629
you actually can proceed with the next task,

00:12:49.809 --> 00:12:54.889
whatever. Right. Um, but I have a question. I

00:12:54.889 --> 00:12:57.970
have a question there. Stop me anytime. Stop

00:12:57.970 --> 00:13:01.720
me. I'll ask the questions that, Someone you

00:13:01.720 --> 00:13:04.379
will ask so I think people are gonna find this

00:13:04.379 --> 00:13:07.159
really is really useful Let me let me show you

00:13:07.159 --> 00:13:10.659
my screen real quick. Right? So, um, if I jump

00:13:10.659 --> 00:13:17.379
here to where to here and It's gonna open about

00:13:17.379 --> 00:13:23.639
This file right what I have here are just headings.

00:13:23.700 --> 00:13:26.419
So what we're looking at is headings right now,

00:13:26.480 --> 00:13:29.740
right? I have a number that helps me just identify

00:13:29.740 --> 00:13:33.220
the heading, this is level two. And for example,

00:13:33.460 --> 00:13:40.059
I can open them. And this is a level. Let me

00:13:40.059 --> 00:13:46.059
see where, where I have a code block. Yeah, so

00:13:46.059 --> 00:13:49.419
this is level two heading. And these, these are

00:13:49.419 --> 00:13:51.659
level three, I have them indented, and I have

00:13:51.659 --> 00:13:55.700
a little number. That helps me see what level

00:13:55.700 --> 00:14:00.840
each one of them is. Is that what we're looking

00:14:00.840 --> 00:14:03.500
at right now? Yes, this would be essentially

00:14:03.500 --> 00:14:07.480
that sort of your heading and then your subheading

00:14:07.480 --> 00:14:10.039
all the way down if you want it to be. So people

00:14:10.039 --> 00:14:12.840
like use org mode pretty extensively for writing.

00:14:13.919 --> 00:14:16.860
And we'll even talk about exporting to Markdown.

00:14:16.899 --> 00:14:20.679
It pretty much exports one -to -one org to Markdown.

00:14:22.159 --> 00:14:25.519
so like this would essentially export to a pretty

00:14:25.519 --> 00:14:29.179
similar markdown file were you to post this to

00:14:29.179 --> 00:14:32.399
uh your you use jekyll for your blog i believe

00:14:32.399 --> 00:14:35.220
you said yep yep yeah so if you wanted to use

00:14:35.220 --> 00:14:37.340
this as for example a blog post you could actually

00:14:37.340 --> 00:14:39.879
export this directly to markdown and pretty much

00:14:39.879 --> 00:14:44.419
have to do zero editing uh to have it in the

00:14:44.419 --> 00:14:47.820
markdown format for that blog okay and i see

00:14:47.820 --> 00:14:51.059
you have a to do there on the um on the heading

00:14:51.480 --> 00:14:55.480
Does that to do make a difference? No. So essentially,

00:14:55.600 --> 00:14:58.159
I just have that as a to do here. And what I

00:14:58.159 --> 00:15:01.700
was going to talk about is the different we'll

00:15:01.700 --> 00:15:06.120
call them states, I guess we'll call them. So,

00:15:06.179 --> 00:15:08.279
for example, you can see at the very bottom,

00:15:08.340 --> 00:15:09.720
I don't know if you can see this in my screen,

00:15:09.779 --> 00:15:11.980
but it says to do state change from to do to

00:15:11.980 --> 00:15:15.620
done blocked by to do call with you. Right. So

00:15:15.620 --> 00:15:20.279
you'll see that you actually have. uh in order

00:15:20.279 --> 00:15:24.259
for this main to do to be done to be marked as

00:15:24.259 --> 00:15:26.259
done i have to actually accomplish the things

00:15:26.259 --> 00:15:29.700
that are underneath it so that it kind of makes

00:15:29.700 --> 00:15:33.559
sense right yeah um so like let's say i'm i'm

00:15:33.559 --> 00:15:36.120
done the call with you then i can finally i can

00:15:36.120 --> 00:15:38.539
mark this as done right there's different states

00:15:38.539 --> 00:15:42.299
that you can do let's say there's mt uh start

00:15:42.299 --> 00:15:46.559
or mt start there we go so like i've actually

00:15:46.559 --> 00:15:49.169
started the call with you And you'll notice that

00:15:49.169 --> 00:15:52.269
this little log book thing came up here and that

00:15:52.269 --> 00:15:55.289
actually shows the clock for the time that, so

00:15:55.289 --> 00:15:57.350
you can like clock in and clock out. So people

00:15:57.350 --> 00:16:01.710
that are employees or contractors can say, I

00:16:01.710 --> 00:16:05.470
have a task to do today and I need to track my

00:16:05.470 --> 00:16:09.009
time on it to show my employer or my, the person

00:16:09.009 --> 00:16:12.250
I'm doing the contract for. There you go. You

00:16:12.250 --> 00:16:15.169
have a clock that's within that task and it actually

00:16:15.169 --> 00:16:18.000
will. You can see in the bottom right of my screen

00:16:18.000 --> 00:16:21.200
there, there's that 0 .00. That will be continually

00:16:21.200 --> 00:16:25.179
counting up as we go through this call and time

00:16:25.179 --> 00:16:27.500
this call, for example. So you'll get an invoice

00:16:27.500 --> 00:16:33.360
at the end of this call. Can I pay with that

00:16:33.360 --> 00:16:37.519
crypto? absolutely i only accept crypto no but

00:16:37.519 --> 00:16:40.799
you can you can kind of see how like org mode

00:16:40.799 --> 00:16:43.399
is like is like emax in and of itself it is like

00:16:43.399 --> 00:16:46.779
a rabbit hole that you could go down for at at

00:16:46.779 --> 00:16:51.159
perpetuity is the word i'm looking for oh you

00:16:51.159 --> 00:16:55.059
it is it is like it's very deep it's there's

00:16:55.059 --> 00:16:58.360
a lot of depth to it so people use it for you

00:16:58.360 --> 00:17:00.929
know just surface level writing when they start

00:17:00.929 --> 00:17:03.090
out and then they're like oh i can do task management

00:17:03.090 --> 00:17:04.869
with it okay we're gonna go a little bit deeper

00:17:04.869 --> 00:17:08.690
oh i can do my my my clocking for my work oh

00:17:08.690 --> 00:17:10.990
okay we'll go a little bit deeper i can write

00:17:10.990 --> 00:17:12.869
code in it oh we'll go a little bit deeper and

00:17:12.869 --> 00:17:15.029
it kind of goes all the way down to which you

00:17:15.029 --> 00:17:18.450
can essentially use org mode for i don't want

00:17:18.450 --> 00:17:20.930
to say everything in your life but a lot of things

00:17:20.930 --> 00:17:23.430
in your life and i think that's what draws a

00:17:23.430 --> 00:17:25.630
lot of people to it is they see the the ultimate

00:17:25.630 --> 00:17:28.369
potential of it and they're like wow like this

00:17:28.839 --> 00:17:30.980
this is pretty cool you'll also note that i have

00:17:30.980 --> 00:17:33.640
like a schedule so like i scheduled this call

00:17:33.640 --> 00:17:39.220
for today at 9 00 a .m our time uh you i could

00:17:39.220 --> 00:17:42.059
change that very simply to tomorrow at 9 00 a

00:17:42.059 --> 00:17:46.640
.m or tomorrow at i don't know uh 1 30 right

00:17:46.640 --> 00:17:50.680
like it you can change these uh schedulings very

00:17:50.680 --> 00:17:55.519
easily and what i use this for pretty um pretty

00:17:56.240 --> 00:18:00.039
consistently is my deadlines so like uh as we

00:18:00.039 --> 00:18:02.619
had mentioned in the previous uh stream i'm self

00:18:02.619 --> 00:18:04.759
-employed so i have to set deadlines for myself

00:18:04.759 --> 00:18:07.440
otherwise nothing ever gets done yeah i know

00:18:07.440 --> 00:18:11.779
how it is so so i i put deadlines into my calendar

00:18:11.779 --> 00:18:15.599
and i actually like pull them up um interesting

00:18:15.599 --> 00:18:18.700
yeah so so one of the cool things about org mode

00:18:18.700 --> 00:18:20.460
2 is you have something called org agenda so

00:18:20.460 --> 00:18:22.460
i'm going to show you something uh my calendar

00:18:22.460 --> 00:18:25.839
so okay but then I want to go over this and I

00:18:25.839 --> 00:18:29.079
want to type it myself. So because let's do it.

00:18:29.119 --> 00:18:31.859
Absolutely. Yeah. You can show me that. And then

00:18:31.859 --> 00:18:34.880
I just want to type it and create the file and

00:18:34.880 --> 00:18:36.779
open Emacs and all that because I don't remember

00:18:36.779 --> 00:18:40.160
quite well how all that was done. Yep. That sounds

00:18:40.160 --> 00:18:41.640
like a plan. So the last thing I'll show you

00:18:41.640 --> 00:18:44.920
then, because this is a scheduled task, is I'm

00:18:44.920 --> 00:18:47.279
going to add this to my org agenda. Sorry, that

00:18:47.279 --> 00:18:50.390
was remove. I'm going to add it to my work agenda

00:18:50.390 --> 00:18:52.369
and I'm going to open my calendar. And you can

00:18:52.369 --> 00:18:55.829
see right here in my calendar is that call with

00:18:55.829 --> 00:18:58.769
you. And when I click on it or when I hit enter

00:18:58.769 --> 00:19:01.650
on it, it actually just links right back to that

00:19:01.650 --> 00:19:05.710
task. So you can kind of imagine having dozens

00:19:05.710 --> 00:19:08.849
of these different files of to -dos and these

00:19:08.849 --> 00:19:12.430
schedules or whatever. And you have a calendar

00:19:12.430 --> 00:19:15.250
that amalgamates all of those tasks into one

00:19:15.250 --> 00:19:19.680
place. You see where I'm going? It's pretty cool.

00:19:19.980 --> 00:19:23.259
Now, I have a question. What if I want, let's

00:19:23.259 --> 00:19:25.640
say that for this meeting, right? I added it

00:19:25.640 --> 00:19:28.359
in my calendar application, the macOS calendar

00:19:28.359 --> 00:19:31.500
application. I added your email. You got an invite,

00:19:31.799 --> 00:19:37.440
right? And I do that from Emacs. Yes. I can.

00:19:38.039 --> 00:19:41.460
The answer with Emacs is essentially always yes.

00:19:41.680 --> 00:19:44.240
But you would get the invite, right? I invite

00:19:44.240 --> 00:19:47.220
you from Emacs and you get the invite and you

00:19:47.220 --> 00:19:49.710
accept it. And I don't have to go to the calendar

00:19:49.710 --> 00:19:56.190
app on macOS? So depending on what you use for

00:19:56.190 --> 00:19:58.869
the invite, so if you use Google Calendar or

00:19:58.869 --> 00:20:01.789
something like that, I believe it is possible.

00:20:03.069 --> 00:20:05.130
There's been some debate in the Emacs community

00:20:05.130 --> 00:20:09.750
of how great it is to integrate Google Calendar

00:20:09.750 --> 00:20:13.289
or not. Because I integrate Google Calendar to

00:20:13.289 --> 00:20:17.150
the extent that I will put an event into my Emacs.

00:20:17.660 --> 00:20:21.539
and push it out to my google calendar where it

00:20:21.539 --> 00:20:24.880
lives doing the doing the invite i'm not 100

00:20:24.880 --> 00:20:27.359
sure about i'm not going to speak on that but

00:20:27.359 --> 00:20:31.859
uh i'm guessing it's probably possible if you

00:20:31.859 --> 00:20:35.180
uh if you're a lisp wizard which i am not so

00:20:35.180 --> 00:20:39.299
okay but it could be could be probably what what

00:20:39.299 --> 00:20:42.319
you do is that you had a an event in emacs and

00:20:42.319 --> 00:20:46.140
it adds it in your google calendar for example

00:20:46.140 --> 00:20:50.680
right Yes. Yeah. So I have like a, um, let me

00:20:50.680 --> 00:20:53.519
see here if I can, it's something, it's a addition

00:20:53.519 --> 00:20:59.559
to org mode called org G Cal. Uh, and the command

00:20:59.559 --> 00:21:02.680
I want is post that point. So whenever I'm, let's

00:21:02.680 --> 00:21:05.440
say I'm on this line, I can actually post that

00:21:05.440 --> 00:21:09.980
to do with the time to Google calendar and it

00:21:09.980 --> 00:21:14.210
will show up in my calendar and. be there for

00:21:14.210 --> 00:21:16.549
like my, my phone, for example, cause like I

00:21:16.549 --> 00:21:19.789
get my notifications on my phone for, you know,

00:21:19.789 --> 00:21:22.329
10 minutes to this event and I get the notification

00:21:22.329 --> 00:21:25.670
on my phone and that's all driven by, uh, Emacs

00:21:25.670 --> 00:21:28.869
making the event and pushing it out to the calendar

00:21:28.869 --> 00:21:32.250
with regard to invites. It uses the Google calendar

00:21:32.250 --> 00:21:37.049
API. I don't know how deep that goes, but I would

00:21:37.049 --> 00:21:38.910
assume that they probably have functions that

00:21:38.910 --> 00:21:42.430
you can, uh, create invites and such. I have

00:21:42.430 --> 00:21:44.690
not done that. That's going to actually be something

00:21:44.690 --> 00:21:47.369
I'm going to try to do. Yeah. The reason I'm

00:21:47.369 --> 00:21:49.710
asking is, for example, right. I have a few meetings

00:21:49.710 --> 00:21:53.589
scheduled, you know, for this week. And what

00:21:53.589 --> 00:21:55.710
do I have to do? I have to go to the Mac OS app.

00:21:57.670 --> 00:22:02.170
Create the event there. And just basically add

00:22:02.170 --> 00:22:04.369
the email of the person that I want to invite.

00:22:04.630 --> 00:22:06.930
That's it. You know, I just add your email. You

00:22:06.930 --> 00:22:10.609
will get that and you can confirm and all that

00:22:10.609 --> 00:22:14.000
stuff. I don't enjoy leaving my terminal and

00:22:14.000 --> 00:22:16.599
going to the macOS Calendar app. I have to grab

00:22:16.599 --> 00:22:19.140
my mouse. Where's my mouse? I have to go. How

00:22:19.140 --> 00:22:21.359
do I add an event here? I have to double click

00:22:21.359 --> 00:22:24.160
on the time slot that I want. I don't enjoy it,

00:22:24.180 --> 00:22:26.859
right? So if I could stay in the terminal, I

00:22:26.859 --> 00:22:30.259
would definitely do it. That was the reason why

00:22:30.259 --> 00:22:33.240
I was asking. Well, what happens with Emacs is

00:22:33.240 --> 00:22:36.039
people are like, exactly like you, they're like,

00:22:36.160 --> 00:22:38.980
I don't want to grab my mouse. That dirty thing.

00:22:39.059 --> 00:22:41.319
I don't want to touch that thing. So they literally

00:22:41.319 --> 00:22:44.019
will write list functions within Emacs to do

00:22:44.019 --> 00:22:45.700
these different things so that they can stay

00:22:45.700 --> 00:22:49.119
in Emacs. And essentially, the goal is to live

00:22:49.119 --> 00:22:52.279
in Emacs. The rest of your life can be, you know,

00:22:52.299 --> 00:22:54.839
spent elsewhere. But when you're on a computer,

00:22:55.039 --> 00:22:57.220
it's to live in Emacs. That's the whole goal.

00:22:57.700 --> 00:23:00.259
Yeah, because I spend all of the day, basically,

00:23:00.259 --> 00:23:03.000
almost all of the day in the terminal in Neogam,

00:23:03.000 --> 00:23:05.140
you know, in different projects. And sometimes,

00:23:05.220 --> 00:23:07.740
well, I do use other apps, of course, like YouTube,

00:23:07.779 --> 00:23:11.019
and I have to schedule events. And I'm like,

00:23:11.059 --> 00:23:14.920
it feels too different. You know, the workflow

00:23:14.920 --> 00:23:18.039
is completely different. It kills the vibe. And

00:23:18.039 --> 00:23:21.480
it's like, no, I don't know. The big thing about

00:23:21.480 --> 00:23:23.299
Emacs is something that I didn't mention in the

00:23:23.299 --> 00:23:27.180
previous video. But what Emacs does is it stops

00:23:27.180 --> 00:23:30.960
the contact switch, which is for people that

00:23:30.960 --> 00:23:34.049
work on a computer. is tremendously expensive

00:23:34.049 --> 00:23:38.650
cognitively yeah right so if i can live in a

00:23:38.650 --> 00:23:42.269
place that everything is unified all of my keybinds

00:23:42.269 --> 00:23:45.789
are linked uh everything is self -documenting

00:23:45.789 --> 00:23:48.269
i can literally search if i can't remember a

00:23:48.269 --> 00:23:51.309
keybind i can literally just search um using

00:23:51.309 --> 00:23:56.000
meta x all of a sudden you're like It's a different

00:23:56.000 --> 00:23:58.119
philosophy, right? Like it's you're staying in

00:23:58.119 --> 00:24:01.140
one place as long as you possibly can so that

00:24:01.140 --> 00:24:02.940
you're not switching context between browser,

00:24:03.039 --> 00:24:07.380
between terminal, between TUI one versus CLI

00:24:07.380 --> 00:24:10.480
two. You get what I'm saying? Yeah. And this

00:24:10.480 --> 00:24:13.779
is and this is kind of the mental shift that

00:24:13.779 --> 00:24:15.519
happens because there's really essentially two.

00:24:16.269 --> 00:24:20.230
ultimate developer workflows and one is the tui

00:24:20.230 --> 00:24:24.130
cli centric workflow where everything is you

00:24:24.130 --> 00:24:27.390
know you use your um you use your program for

00:24:27.390 --> 00:24:29.609
this and your program for this and you pipe between

00:24:29.609 --> 00:24:33.730
them or there's emacs which is essentially the

00:24:33.730 --> 00:24:36.630
unified version of all of that and that's the

00:24:36.630 --> 00:24:39.680
different the different philosophy, I would say.

00:24:39.779 --> 00:24:42.779
And both workflows are absolutely valid. And

00:24:42.779 --> 00:24:45.500
you said that I can run NeoVim within Emacs,

00:24:45.700 --> 00:24:49.440
right? Well, you can run Vim controls within

00:24:49.440 --> 00:24:54.880
Emacs. Yeah. So like your key binds that you

00:24:54.880 --> 00:24:57.920
have in your muscle memory, you can literally

00:24:57.920 --> 00:25:02.220
just transfer that into Emacs and you'd feel

00:25:02.220 --> 00:25:06.079
like at home. We'll put it that way. All right.

00:25:07.000 --> 00:25:09.319
All right. I'm trying to sell it to them, guys.

00:25:09.440 --> 00:25:13.279
I'm trying to sell it to them. Yeah, it seems

00:25:13.279 --> 00:25:15.640
I'm just going to ask questions that I'm interested

00:25:15.640 --> 00:25:17.599
in. You know, I'm not going to be asking stuff

00:25:17.599 --> 00:25:19.579
that I won't use because you know how it is,

00:25:19.579 --> 00:25:22.000
right? Sometimes you get a tutorial and there's

00:25:22.000 --> 00:25:23.640
a lot of stuff that you're not interested in.

00:25:23.680 --> 00:25:27.980
And it's like, no, but yeah, I just want to see

00:25:27.980 --> 00:25:30.839
the power of Emacs and see how I could integrate

00:25:30.839 --> 00:25:34.579
it into my. life, that calendar thing seems quite

00:25:34.579 --> 00:25:36.859
interesting, you know, because of what we discussed

00:25:36.859 --> 00:25:39.799
right now, staying in the terminal or at least

00:25:39.799 --> 00:25:42.240
a terminal based application if possible. Right.

00:25:42.319 --> 00:25:45.920
So, um, all right. Is there something else you

00:25:45.920 --> 00:25:49.420
wanted to show here before I type stuff in? No,

00:25:49.500 --> 00:25:51.859
not really. Like I was going to discuss writing

00:25:51.859 --> 00:25:54.119
a little bit for you because you're marked down,

00:25:54.180 --> 00:25:56.259
like you, you write a blog and all that sort

00:25:56.259 --> 00:25:59.299
of thing. So I guess what, one thing I'll do

00:25:59.299 --> 00:26:00.980
right now is I'll show you the export. Like you

00:26:00.980 --> 00:26:07.069
can actually, export this to markdown uh right

00:26:07.069 --> 00:26:09.829
here and you can actually see right there that's

00:26:09.829 --> 00:26:13.049
my exported markdown completely like this would

00:26:13.049 --> 00:26:16.670
be valid for throwing onto your blog right then

00:26:16.670 --> 00:26:21.410
and there okay it's just wrong yeah 100 and then

00:26:21.410 --> 00:26:23.430
you can even like if you wanted to preview it

00:26:23.430 --> 00:26:27.650
uh in html for example uh let's see if this works

00:26:27.650 --> 00:26:31.779
for me it opens your browser okay Yeah, there

00:26:31.779 --> 00:26:35.660
you go. So like this is a fully HTML compliant.

00:26:36.980 --> 00:26:39.400
You see what I'm saying? Yep, yep. And is this,

00:26:39.440 --> 00:26:41.440
because there's a plugin in Neovim that does

00:26:41.440 --> 00:26:43.779
this. What is this? Markdown Preview, that Envim

00:26:43.779 --> 00:26:47.460
I think it's called. Is this like baked into

00:26:47.460 --> 00:26:49.740
Emacs or is this something you installed additionally?

00:26:50.839 --> 00:26:54.460
That's a good question. This is a export org,

00:26:54.559 --> 00:26:58.460
export. I want to say it's related to org mode.

00:26:58.579 --> 00:27:02.099
Like I think that if you download, the org package

00:27:02.099 --> 00:27:05.519
within emacs okay you get the export i want to

00:27:05.519 --> 00:27:08.160
say i could be yeah i could be wrong with that

00:27:08.160 --> 00:27:11.640
and if i am wrong post the comments uh because

00:27:11.640 --> 00:27:15.240
i this is something that's baked into doom emacs

00:27:15.240 --> 00:27:17.519
this is why i really am an advocate for doom

00:27:17.519 --> 00:27:20.019
emacs is that it comes with all these like sane

00:27:20.019 --> 00:27:24.380
useful defaults um that i've never had to like

00:27:24.380 --> 00:27:27.240
add to my base emacs configuration so i'm not

00:27:27.240 --> 00:27:30.380
100 sure about that if somebody is a vinyl emacs

00:27:30.380 --> 00:27:32.559
user and is watching this video comment below

00:27:32.559 --> 00:27:35.720
and tell me how wrong i am but it is baked into

00:27:35.720 --> 00:27:39.079
dumia emacs from like the get -go so all right

00:27:39.079 --> 00:27:42.920
interesting okay thanks for thanks for that so

00:27:42.920 --> 00:27:45.519
let me switch to my screen then let's do it okay

00:27:45.519 --> 00:27:50.180
and we can get started let me switch here I haven't

00:27:50.180 --> 00:27:52.180
even, well, I did open Emacs. I'm not going to

00:27:52.180 --> 00:27:54.880
lie. I opened Emacs today because I wanted to

00:27:54.880 --> 00:27:57.539
check the KJ. You remember I had an issue with

00:27:57.539 --> 00:28:00.559
KJ? It works now. Yes. It probably was my computer.

00:28:00.819 --> 00:28:03.359
Yeah, I just needed a reboot or something. I

00:28:03.359 --> 00:28:05.700
don't know what's going on, but it's working.

00:28:05.779 --> 00:28:09.099
Sometimes closing Emacs and reopening it is what

00:28:09.099 --> 00:28:12.740
you need to do. If we make changes to that main

00:28:12.740 --> 00:28:15.480
configuration file, generally just restarting,

00:28:15.480 --> 00:28:17.799
like the way that we were doing it, space HRR,

00:28:17.839 --> 00:28:20.319
doom reload or whatever, usually that works.

00:28:20.519 --> 00:28:22.940
But sometimes you just got to close it and reopen

00:28:22.940 --> 00:28:26.019
it. So the computer's for you, right? Yeah, yeah,

00:28:26.059 --> 00:28:30.180
yeah. This is the command, right? Yep, you got

00:28:30.180 --> 00:28:32.160
it. Emacs, yeah. This is the one that we were

00:28:32.160 --> 00:28:36.660
typing the last time. So let me do something.

00:28:39.079 --> 00:28:42.660
I'm going to create an alias for this. That's

00:28:42.660 --> 00:28:45.359
a good idea. Even just emacs as the alias is

00:28:45.359 --> 00:28:50.200
a good idea. Hold on. What's happening here?

00:28:52.700 --> 00:28:58.279
As an aside, while you do that, one of the things

00:28:58.279 --> 00:29:06.369
that is in Linux is the X11 system. versus wayland

00:29:06.369 --> 00:29:09.190
i i'm probably talking gibberish to your audience

00:29:09.190 --> 00:29:13.009
right now but the x11 ecosystem is far more mature

00:29:13.009 --> 00:29:16.250
than the wayland ecosystem so i actually launch

00:29:16.250 --> 00:29:22.950
emacs in a wayland uh gnome system but the i

00:29:22.950 --> 00:29:25.769
run emacs in an x11 window because it's much

00:29:25.769 --> 00:29:29.009
faster much more responsive uh i may be speaking

00:29:29.009 --> 00:29:32.349
complete gibberish oh and x11 is like the old

00:29:32.349 --> 00:29:35.960
the old way of doing things It is. And I mean,

00:29:36.000 --> 00:29:39.299
it's it's just more mature. It's just like they've

00:29:39.299 --> 00:29:42.420
done optimizations for it. And so like when I

00:29:42.420 --> 00:29:44.500
start up Emacs, I actually run it with an alias

00:29:44.500 --> 00:29:48.339
to run it in X11 mode as opposed to Wayland.

00:29:48.640 --> 00:29:52.380
OK, interesting. OK, so it's faster that way.

00:29:52.440 --> 00:29:54.779
It's more performance. It's much more performance.

00:29:54.819 --> 00:29:57.779
It's actually like almost equivalent to NeoVim.

00:29:57.779 --> 00:30:00.079
Like I've actually. put Emacs on one side and

00:30:00.079 --> 00:30:01.640
Neovim on the other and tried to like scroll

00:30:01.640 --> 00:30:06.000
through and do LSPs and stuff. And it is just

00:30:06.000 --> 00:30:09.259
as fast as Neovim, at least for me. Interesting.

00:30:09.519 --> 00:30:12.579
That's a nice tip. A nice tip. You know what?

00:30:12.660 --> 00:30:16.059
I just want to quickly do something, Josh. I

00:30:16.059 --> 00:30:20.039
want to just write down the commands that I'm

00:30:20.039 --> 00:30:23.279
going to be using here. If that's okay with you

00:30:23.279 --> 00:30:26.880
in a file. Absolutely. This is my blog post.

00:30:28.430 --> 00:30:31.289
Look how important this is. I'm even going to

00:30:31.289 --> 00:30:37.630
create a file here. Oh my goodness. It's happening,

00:30:37.710 --> 00:30:45.029
guys. It's happening. He's switching. It's 2025.

00:30:47.789 --> 00:30:52.430
What is it? Four. Man, I hate typing the numbers

00:30:52.430 --> 00:30:56.490
in this keyboard. Do you use a number layer?

00:30:57.279 --> 00:31:02.319
No, I don't. And the reason I don't is because

00:31:02.319 --> 00:31:07.680
when I switch to the laptop, I want to type fast

00:31:07.680 --> 00:31:11.279
as well. So I type slow in both of them. Do you

00:31:11.279 --> 00:31:14.559
use layers on your keyboard? I have to because

00:31:14.559 --> 00:31:19.420
I use a 36 keyer. So I like have to use I essentially

00:31:19.420 --> 00:31:23.299
set my third layer to a numpad. So like under

00:31:23.299 --> 00:31:28.740
my right hand is the. It would be a 10 -key numpad.

00:31:29.400 --> 00:31:34.400
And in my laptop, I run something called Kmonad.

00:31:35.819 --> 00:31:40.839
And it is a way to create layers on essentially

00:31:40.839 --> 00:31:45.700
any keyboard. So I actually have a numpad under

00:31:45.700 --> 00:31:49.519
my right hand when I hit a layer on my laptop.

00:31:50.039 --> 00:31:53.859
Okay, a numpad. I could do that in Karabiner.

00:31:54.329 --> 00:31:56.809
It's another tool, you know, a keyboard mapper

00:31:56.809 --> 00:31:59.289
for macOS. I'm familiar. I'm familiar because

00:31:59.289 --> 00:32:02.170
I use my girlfriend's Mac sometimes. Oh, so you're

00:32:02.170 --> 00:32:04.650
familiar with Carabiner. Okay. But I'm just too

00:32:04.650 --> 00:32:07.130
lazy and I just use the numbers. But I don't

00:32:07.130 --> 00:32:08.730
like that I have to be looking where the numbers

00:32:08.730 --> 00:32:10.730
are. I'm not used to them. And I've been typing

00:32:10.730 --> 00:32:13.970
numbers for years on computer keyboards. You

00:32:13.970 --> 00:32:16.750
know, I got used to the keypad so much that.

00:32:17.130 --> 00:32:23.319
Yeah. Let's see. I'm just going to put this here,

00:32:23.500 --> 00:32:29.240
and I'm going to upload this later. So create

00:32:29.240 --> 00:32:37.339
the alias. And just going to leave that for the

00:32:37.339 --> 00:32:42.180
folks that need that there. Nice. And how do

00:32:42.180 --> 00:32:44.119
you run it? Do you usually run it just Emacs?

00:32:44.319 --> 00:32:48.059
Is that what you type? I mean, I have a hotkey

00:32:48.059 --> 00:32:52.069
bound to it, so I just... we can even talk about

00:32:52.069 --> 00:32:55.369
like the, there's an Emacs Damon that essentially

00:32:55.369 --> 00:32:58.950
you open. So one of the big, I actually was going

00:32:58.950 --> 00:33:01.009
to make a video about this, uh, either today

00:33:01.009 --> 00:33:03.069
or tomorrow, but there was a guy that wrote a

00:33:03.069 --> 00:33:06.289
blog post about how Emacs startup time doesn't

00:33:06.289 --> 00:33:10.049
matter. And the reason is because when you, you

00:33:10.049 --> 00:33:13.009
essentially open Emacs once in your life cycle

00:33:13.009 --> 00:33:15.569
of your computer. So you, you essentially start

00:33:15.569 --> 00:33:18.190
your computer, Emacs starts up and then that's

00:33:18.190 --> 00:33:20.329
the only time you have to open up Emacs. Oh,

00:33:20.329 --> 00:33:23.569
yeah. So what you can do is you can actually

00:33:23.569 --> 00:33:26.369
access Emacs through a daemon. So when you start

00:33:26.369 --> 00:33:29.029
Emacs, the daemon starts and every single subsequent

00:33:29.029 --> 00:33:31.849
window that you open, well, I guess it would

00:33:31.849 --> 00:33:34.589
be called a frame in Emacs lingo, but every subsequent

00:33:34.589 --> 00:33:39.089
window you open is essentially instantaneous

00:33:39.089 --> 00:33:41.210
because it's just running off the daemon. You're

00:33:41.210 --> 00:33:47.219
running a client to that original Emacs. Word

00:33:47.219 --> 00:33:50.259
I'm looking for here. But like the original Emacs

00:33:50.259 --> 00:33:53.039
instance that you opened, there's a daemon that

00:33:53.039 --> 00:33:55.480
comes in and essentially just uses that as its

00:33:55.480 --> 00:33:58.559
startup. So you'll see like at the bottom, your

00:33:58.559 --> 00:34:05.099
startup time is like 0 .6 seconds, which is super

00:34:05.099 --> 00:34:08.500
fast. That's actually like tremendously fast.

00:34:08.599 --> 00:34:10.480
Generally, like mine takes about four seconds

00:34:10.480 --> 00:34:12.579
to start up. Because you have a lot of stuff

00:34:12.579 --> 00:34:15.170
added, I guess. I do. Yeah, I have essentially,

00:34:15.369 --> 00:34:20.730
I think I have 330 packages. You have 120, 120

00:34:20.730 --> 00:34:25.170
or 126? I can't read that. 128. 128, okay. There

00:34:25.170 --> 00:34:33.530
you go. Testing my vision. All right. So now

00:34:33.530 --> 00:34:35.929
that I'm here, what was it that I needed to,

00:34:35.969 --> 00:34:40.130
well, how do I create a file, basically? Space

00:34:40.130 --> 00:34:45.590
period. Space period, okay. That opens. So that's

00:34:45.590 --> 00:34:48.829
your file system. Okay. Hold on. Hold on. Hold

00:34:48.829 --> 00:34:58.610
on. Hold on. Space is file navigate file exploder,

00:34:58.650 --> 00:35:05.570
right? Yeah. Okay. There we go. Yep. And then

00:35:05.570 --> 00:35:09.289
if you wanted to create it in whatever directory

00:35:09.289 --> 00:35:15.440
you can create there. Yeah, and then if you hit

00:35:15.440 --> 00:35:17.320
backspace, it should actually go back like a

00:35:17.320 --> 00:35:18.800
whole directory. You shouldn't have to like,

00:35:18.900 --> 00:35:21.699
yeah, exactly. So you can like find whatever

00:35:21.699 --> 00:35:24.039
directory you wanted to create the file and create

00:35:24.039 --> 00:35:30.079
the file with a .org extension. Okay, and does

00:35:30.079 --> 00:35:35.260
Emacs open in a certain directory? When I opened

00:35:35.260 --> 00:35:38.300
it right now, did it open? Well, I guess it opened

00:35:38.300 --> 00:35:41.820
where I was at and I was here in the .files latest,

00:35:42.019 --> 00:35:44.989
right? yes yeah so wherever you open it from

00:35:44.989 --> 00:35:47.570
in your terminal is where it will open in the

00:35:47.570 --> 00:35:50.710
file system okay okay i'm gonna use this dot

00:35:50.710 --> 00:35:56.690
files latest and um i'm going to create here

00:35:56.690 --> 00:36:02.710
uh how do i create a directory here can i create

00:36:02.710 --> 00:36:06.250
it yeah create another say emacs or whatever

00:36:06.250 --> 00:36:08.429
you want to create the directory just add a trailing

00:36:08.429 --> 00:36:11.460
slash to it yeah and that's your directory and

00:36:11.460 --> 00:36:13.440
then whatever file you want to do within it so

00:36:13.440 --> 00:36:20.139
okay uh yeah so example .org or whatever example

00:36:20.139 --> 00:36:24.099
.org okay and then i hit enter yep so that is

00:36:24.099 --> 00:36:26.639
going to create the file and the directory okay

00:36:26.639 --> 00:36:28.679
yeah and it'll ask if you want to create it then

00:36:28.679 --> 00:36:32.840
it'll say yes okay yep there you go and then

00:36:32.840 --> 00:36:34.900
you're actually in editing mode so you can literally

00:36:34.900 --> 00:36:37.719
name the file from get go if you want to just

00:36:37.719 --> 00:36:41.119
leave it as example leave as example okay you

00:36:41.119 --> 00:36:45.400
can hit escape and you can use vim okay i can

00:36:45.400 --> 00:36:48.619
use my okay got it i i can leave the title there

00:36:48.619 --> 00:36:52.360
at the top right does something happen if i remove

00:36:52.360 --> 00:36:56.210
this title No, the file will still have the same

00:36:56.210 --> 00:36:58.289
name and everything. It's just like that is a

00:36:58.289 --> 00:37:02.429
org mode specific tag. So there's a multitude

00:37:02.429 --> 00:37:04.389
of tags you could add to an org file. That's

00:37:04.389 --> 00:37:06.610
just like your title. It's kind of like your

00:37:06.610 --> 00:37:09.429
front matter. Front matter or metadata or something

00:37:09.429 --> 00:37:13.650
like. Okay. Yes. Okay. Okay. Great. Okay. So

00:37:13.650 --> 00:37:16.829
you said that headings. Then if I want to start

00:37:16.829 --> 00:37:21.599
with the heading here. It's an asterisk. I want

00:37:21.599 --> 00:37:24.119
to have I'm just used to any of them. You know,

00:37:24.139 --> 00:37:28.980
I follow some markdown guidelines and I just

00:37:28.980 --> 00:37:32.440
keep one single H1 per file. So I'm just going

00:37:32.440 --> 00:37:34.679
to do the same thing. It's usually the name of

00:37:34.679 --> 00:37:37.960
the name of the file. Right. I'm just going to

00:37:37.960 --> 00:37:40.800
leave that there. If I want to do a level two

00:37:40.800 --> 00:37:44.800
heading is two asterisks. Right. Correct. Then

00:37:44.800 --> 00:37:48.369
I leave a space. Yep. And then you could write

00:37:48.369 --> 00:37:50.329
whatever, like, let's say it's a to -do. You

00:37:50.329 --> 00:37:53.530
could capitalize T -O -T -D -O, like to -do.

00:37:54.010 --> 00:37:56.409
There you go. And it will format it as such.

00:37:56.550 --> 00:37:58.909
And then you could say, I don't know, finish

00:37:58.909 --> 00:38:03.710
this video, right? Okay. So it detects that this

00:38:03.710 --> 00:38:07.690
is a to -do, right? Yes. And then if you hit

00:38:07.690 --> 00:38:11.489
enter, you actually can mark it as done on that

00:38:11.489 --> 00:38:14.150
line. Okay, okay. With enter, you cycle through

00:38:14.150 --> 00:38:18.739
the states. Yes. So there's a multitude of states

00:38:18.739 --> 00:38:21.599
you can do in do me max. I don't know how deep

00:38:21.599 --> 00:38:22.860
you want to get into this, but you could have

00:38:22.860 --> 00:38:25.159
like a starting or a waiting. If you're like

00:38:25.159 --> 00:38:27.780
bottlenecked for something, like let's say you

00:38:27.780 --> 00:38:29.760
send something off to somebody else and you're

00:38:29.760 --> 00:38:32.000
waiting for it to come back. Wait would be a

00:38:32.000 --> 00:38:36.440
good tag to add to it. In addition to that, if

00:38:36.440 --> 00:38:39.860
you go to the end of that line, you can add a

00:38:39.860 --> 00:38:44.659
colon. with space right i leave a space before

00:38:44.659 --> 00:38:47.940
yeah leave a space and then a colon uh right

00:38:47.940 --> 00:38:51.079
beside the space uh let's say you want to tag

00:38:51.079 --> 00:38:55.340
it as video so capital v -i -d -e -o and then

00:38:55.340 --> 00:39:00.000
a closing colon yeah okay uh colon not semicolon

00:39:00.000 --> 00:39:04.679
oh both of them are colon right yeah colon video

00:39:04.679 --> 00:39:08.389
okay that's a tag Okay. That's a tag. So that

00:39:08.389 --> 00:39:11.150
you can use that as a tag to, let's say this

00:39:11.150 --> 00:39:14.630
is like your only org file you ever create and

00:39:14.630 --> 00:39:17.969
it's 10 ,000 lines long. You can traverse it

00:39:17.969 --> 00:39:20.889
based on the tag. So let's say this is your video

00:39:20.889 --> 00:39:23.610
to do, or there's a home to do, or there's a

00:39:23.610 --> 00:39:25.949
work to do or whatever. You can just tag it as

00:39:25.949 --> 00:39:28.710
such and you would be able to traverse the file

00:39:28.710 --> 00:39:34.269
just going through the tags. Okay. Okay. I generally

00:39:34.269 --> 00:39:36.869
don't do that with an org file. The only big

00:39:36.869 --> 00:39:40.510
org file I have is my projects. But some people,

00:39:40.610 --> 00:39:42.570
there's different methods for doing it. Same

00:39:42.570 --> 00:39:44.030
thing with Markdown, right? Yeah, yeah, yeah.

00:39:45.010 --> 00:39:47.630
I know you like your daily. You like your daily

00:39:47.630 --> 00:39:49.010
file. Yeah, yeah. So you can do that. I remember

00:39:49.010 --> 00:39:53.489
using tags in the past when I was a huge fan

00:39:53.489 --> 00:39:57.329
of Obsidian. And I used Obsidian, man, a lot.

00:39:57.409 --> 00:39:59.590
And I learned a lot of stuff about Obsidian.

00:39:59.650 --> 00:40:02.719
I remember that I created tags, you know. A lot

00:40:02.719 --> 00:40:06.179
of times I never use them. So tags for me don't

00:40:06.179 --> 00:40:09.659
exist. I don't. And some people don't use it

00:40:09.659 --> 00:40:12.659
at all. They exist, but they don't exist. I'm

00:40:12.659 --> 00:40:15.440
with you on that one. I only use it for very

00:40:15.440 --> 00:40:19.000
specific projects, but. but some people use it

00:40:19.000 --> 00:40:21.139
for everything. Like if they create a to -do,

00:40:21.219 --> 00:40:23.659
it has to have a tag on it. Oh, yeah, yeah, yeah.

00:40:23.760 --> 00:40:25.960
They're that meticulous about it. Yeah, I did

00:40:25.960 --> 00:40:28.719
go through that. You know, I spent hours, you

00:40:28.719 --> 00:40:31.099
know, and days, probably even months, you know,

00:40:31.119 --> 00:40:34.800
playing with tags. And now they just don't exist

00:40:34.800 --> 00:40:37.239
for me anymore. But it's good for people that

00:40:37.239 --> 00:40:39.739
do like using tags to know that this is an option,

00:40:39.840 --> 00:40:43.780
right? Can you have nested tags? I believe so.

00:40:43.800 --> 00:40:45.719
So you could essentially just add infinite tags

00:40:45.719 --> 00:40:47.820
to that. Like you just at the end of that video,

00:40:47.920 --> 00:40:50.460
you could tag another work and then another you

00:40:50.460 --> 00:40:52.980
could essentially tag infinitely on top of it.

00:40:53.719 --> 00:40:55.940
No space between the two colons. You can actually

00:40:55.940 --> 00:40:58.179
just use the previous. Yeah, exactly. So you

00:40:58.179 --> 00:41:01.820
just have to be a ton of uppercase or no. I don't

00:41:01.820 --> 00:41:03.699
believe so. I think you use lowercase as well.

00:41:03.800 --> 00:41:07.099
And as an aside, if you liked Obsidian or Grom

00:41:07.099 --> 00:41:11.610
or Grom is a package that kind of like. It replicates

00:41:11.610 --> 00:41:14.570
Obsidian in the best of ways in that it like

00:41:14.570 --> 00:41:17.949
you get your links to your different files and

00:41:17.949 --> 00:41:19.530
stuff. I'll show you that in the next video.

00:41:19.690 --> 00:41:22.250
In the next one. Yeah, it's going to be too much.

00:41:22.690 --> 00:41:25.510
All right. All right. So I have a heading to

00:41:25.510 --> 00:41:28.730
here. Right. And what if I want to have tasks

00:41:28.730 --> 00:41:33.590
inside? If I go to the next line. Yep. How do

00:41:33.590 --> 00:41:37.469
I add bullet points? Is it just a dash? You could

00:41:37.469 --> 00:41:40.559
do a dash. And then you could do, let's say you

00:41:40.559 --> 00:41:42.900
want to do like a checkbox. You can do just your

00:41:42.900 --> 00:41:45.880
opening and closing bracket. And that would be

00:41:45.880 --> 00:41:48.340
a checkbox. Or you can use this as a note. And

00:41:48.340 --> 00:41:50.679
as you're like, I would say that would be a note.

00:41:50.820 --> 00:41:52.980
You could have a bullet point underneath it as

00:41:52.980 --> 00:41:56.860
a note to do for the to do rather. And then you

00:41:56.860 --> 00:41:58.820
could have like additional to do's if you want.

00:41:59.440 --> 00:42:04.940
How do I make this line like a task? So if you

00:42:04.940 --> 00:42:06.900
want it to do, you can either add to do. I don't.

00:42:07.159 --> 00:42:08.559
Actually, for bullets, I don't think you can

00:42:08.559 --> 00:42:10.980
do todo. Maybe you can. Try adding todo to the

00:42:10.980 --> 00:42:14.739
very front of it. Oh, no, right below. Oh, and

00:42:14.739 --> 00:42:17.619
I have a question before we continue. I use bullet

00:42:17.619 --> 00:42:21.039
points a lot, right? So I have a plugin in Neovim.

00:42:21.039 --> 00:42:27.039
When I hit enter here, I just want to have another...

00:42:27.039 --> 00:42:30.159
Let me show you. i think it's easier i know exactly

00:42:30.159 --> 00:42:31.900
what you're saying you want to add a bullet point

00:42:31.900 --> 00:42:35.280
yeah below it yep so go to the line with the

00:42:35.280 --> 00:42:38.440
bullet point and hit control enter here control

00:42:38.440 --> 00:42:43.059
enter okay there you go so you have to use control

00:42:43.059 --> 00:42:45.860
enter all the time yeah but you can change that

00:42:45.860 --> 00:42:49.380
behavior anything is changeable okay let me just

00:42:49.380 --> 00:43:01.710
uh control enter control enter You know what?

00:43:01.809 --> 00:43:04.449
I should open this with Emacs and edit this.

00:43:04.550 --> 00:43:08.650
The only problem is that this is in a network

00:43:08.650 --> 00:43:11.130
drive. So probably Emacs is going to be a little

00:43:11.130 --> 00:43:13.570
bit slower. So if I want to open Emacs in this

00:43:13.570 --> 00:43:18.190
directory, I can, right? Yes. So I just run Emacs.

00:43:18.289 --> 00:43:20.429
What happens with the instance that I have running

00:43:20.429 --> 00:43:23.269
already? It should stay alive and you should

00:43:23.269 --> 00:43:24.829
actually have another instance that pops up.

00:43:25.110 --> 00:43:29.610
So I can have two instances there? Yes. And that's

00:43:29.610 --> 00:43:32.449
why you would run it with Emacs client. So when

00:43:32.449 --> 00:43:33.929
you start Emacs, you can actually run it with

00:43:33.929 --> 00:43:36.469
a command Emacs client and it will actually create

00:43:36.469 --> 00:43:39.829
that client for you so that you the next startup

00:43:39.829 --> 00:43:42.150
would be very quick. Yeah. So you should be within

00:43:42.150 --> 00:43:44.230
your. Yeah, there you go. You're within your

00:43:44.230 --> 00:43:47.670
data volume and everything. Yeah. Yeah. And I

00:43:47.670 --> 00:43:54.190
it was space that. And here I can look through

00:43:54.190 --> 00:44:00.019
the. I can look. Is there. Like a file picker.

00:44:00.039 --> 00:44:02.619
Like, can I bring up something that allows me

00:44:02.619 --> 00:44:06.840
to search for the file? Just hit enter right

00:44:06.840 --> 00:44:10.800
now. Enter. Okay. That is kind of your file picker.

00:44:10.840 --> 00:44:15.360
That's Durhead. And I can type here like the

00:44:15.360 --> 00:44:17.519
name of the other file that I had, what that

00:44:17.519 --> 00:44:20.099
was. I don't remember what name I gave it, but

00:44:20.099 --> 00:44:24.900
can I search for something here? Emacs? No. Yes,

00:44:24.940 --> 00:44:28.519
you can. Are you in the same directory? Yeah,

00:44:28.599 --> 00:44:32.019
I typed something, and I don't know what I did.

00:44:32.199 --> 00:44:36.119
How can I exit out of this? It's essentially

00:44:36.119 --> 00:44:39.380
Vim, so it's like Ranger. You can just hit H

00:44:39.380 --> 00:44:42.900
-A -K -L -L. Yeah, yeah, yeah. Here I'm in the

00:44:42.900 --> 00:44:47.159
directory. It's inside posts, but is there a

00:44:47.159 --> 00:44:49.179
way for me just to bring up something that I

00:44:49.179 --> 00:44:53.019
can type and search? For the post, yeah. Space

00:44:53.019 --> 00:44:58.000
F. So when I'm in here, right? yeah space space

00:44:58.000 --> 00:45:02.519
f and then capital f after that okay correct

00:45:02.519 --> 00:45:04.699
and then just search emacs or whatever your name

00:45:04.699 --> 00:45:07.340
there you go okay okay and let's say that i'm

00:45:07.340 --> 00:45:11.800
in in emacs how do i quit out of this menu with

00:45:11.800 --> 00:45:16.599
uh uh you can hit q q okay or yeah or you could

00:45:16.599 --> 00:45:19.280
even just kill the buffer too because we'll talk

00:45:19.280 --> 00:45:22.010
about buffers and stuff because Later, another

00:45:22.010 --> 00:45:25.389
video. But the way that Emacs works is instead

00:45:25.389 --> 00:45:28.869
of using Tmux, you're using buffers inside of

00:45:28.869 --> 00:45:32.969
a workspace. So like every single window or that

00:45:32.969 --> 00:45:36.929
you open is a buffer and that buffer lives forever

00:45:36.929 --> 00:45:41.250
until you kill it. Okay. Okay. Yeah. Makes sense.

00:45:41.429 --> 00:45:44.530
So if I type, when I open Emacs, if I type here

00:45:44.530 --> 00:45:49.809
later, F, capital F again, I can search for,

00:45:49.929 --> 00:45:53.309
okay. find file from here right there you go

00:45:53.309 --> 00:45:57.710
okay it's kind of like you're uh not harpoon

00:45:57.710 --> 00:46:00.590
but telescope as somebody in the comments of

00:46:00.590 --> 00:46:04.170
the previous video had mentioned exactly that

00:46:04.170 --> 00:46:10.630
was my bad all right so this where am i um here

00:46:10.630 --> 00:46:23.059
so it's um theater f Capital F to find files.

00:46:23.420 --> 00:46:28.860
Okay, great. All right. So control enter for

00:46:28.860 --> 00:46:31.360
the bullet points. This is to find files. Okay.

00:46:31.440 --> 00:46:33.800
I have the headings here. How can I fold the

00:46:33.800 --> 00:46:35.920
headings? What was the key that you mentioned

00:46:35.920 --> 00:46:38.599
that is to fold? I believe it's tab. I'm not

00:46:38.599 --> 00:46:40.880
sure for markdown. I don't use markdown, but

00:46:40.880 --> 00:46:44.539
there you go. Okay. Oh yeah, but this is markdown

00:46:44.539 --> 00:46:47.670
and we're interested in org mode. Okay. let me

00:46:47.670 --> 00:46:51.110
switch to the other one okay or an org here okay

00:46:51.110 --> 00:46:53.869
but it it still opens the markdown files and

00:46:53.869 --> 00:46:58.230
i can see yeah everything is i believe uh doom

00:46:58.230 --> 00:47:01.170
emacs this may even be native emacs used uses

00:47:01.170 --> 00:47:04.550
tree sitter so whenever you open a file of a

00:47:04.550 --> 00:47:07.670
certain extension it'll give you the syntax highlighting

00:47:07.670 --> 00:47:10.989
um within it so you see your syntax highlighting

00:47:10.989 --> 00:47:15.139
which is works looks nice yep yep yeah Okay,

00:47:15.139 --> 00:47:18.280
so I can add a task. How can I, a bullet point,

00:47:18.420 --> 00:47:20.480
I'm sorry, with control enter. And how can I

00:47:20.480 --> 00:47:22.699
add a task here? Let's say that I want this to

00:47:22.699 --> 00:47:25.420
be a task. Let's say it's a checkbox, for example.

00:47:25.800 --> 00:47:29.119
Yeah, a checkbox. Yep, open space, close, or

00:47:29.119 --> 00:47:31.659
sorry, open bracket space, close bracket. Yeah,

00:47:31.679 --> 00:47:35.659
exactly. And is there a way to type that with

00:47:35.659 --> 00:47:38.420
a single key or something with a shortcut? Or

00:47:38.420 --> 00:47:41.260
you do it that way? I almost never use them,

00:47:41.300 --> 00:47:46.250
so. Okay. But yeah, let's say that's the task.

00:47:46.250 --> 00:47:48.730
And then you could hit enter on it. It will mark

00:47:48.730 --> 00:47:50.969
it as done. Or it will check the checkbox for

00:47:50.969 --> 00:47:53.650
you. And if I want a task below, control enter.

00:47:53.789 --> 00:47:57.150
Okay. Control enter creates another tasks. Okay.

00:47:57.230 --> 00:48:02.570
Yes. And with enter, I can mark it as done. Okay.

00:48:02.650 --> 00:48:06.530
Yes. And if I mark this one as done, is the main

00:48:06.530 --> 00:48:09.239
one marked as done? Like the heading? No, because

00:48:09.239 --> 00:48:12.820
it's the subtask of the main task, right? So

00:48:12.820 --> 00:48:18.460
let's say, I believe it's the to -do heading

00:48:18.460 --> 00:48:24.619
that actually dictates that. But you can actually

00:48:24.619 --> 00:48:29.940
have a tracker of how many tasks within that

00:48:29.940 --> 00:48:32.579
to -do you need to do. It gets kind of involved.

00:48:33.159 --> 00:48:37.239
It gets pretty involved. You can do a lot with

00:48:37.239 --> 00:48:41.289
it. Okay. Yeah. Okay. But I know how to do this,

00:48:41.369 --> 00:48:46.489
which I use quite often. So I can mark this heading

00:48:46.489 --> 00:48:51.250
as done, right? Yes. And what happens if, for

00:48:51.250 --> 00:48:53.670
example, let's say that I'm here, right? And

00:48:53.670 --> 00:49:00.829
I go to a bullet point below. Okay. So if I hit

00:49:00.829 --> 00:49:04.849
enter here, the indentation is going to be shifted

00:49:04.849 --> 00:49:08.130
to the right, correct? right so you could add

00:49:08.130 --> 00:49:11.289
a subtask of that subtask of that subtask that

00:49:11.289 --> 00:49:15.630
you see where it's going oh okay so i can indents

00:49:15.630 --> 00:49:18.630
with ctrl d and ctrl t just like any of them

00:49:18.630 --> 00:49:21.989
okay that was going to be my question so this

00:49:21.989 --> 00:49:25.849
is a bullet point and um how do you create tasks

00:49:25.849 --> 00:49:29.250
then do you create here like a to do do you do

00:49:29.250 --> 00:49:33.949
to do here and do it that way or is that to do

00:49:33.949 --> 00:49:37.869
that to do only works in in headings it only

00:49:37.869 --> 00:49:40.030
works in headings i believe i'm not sure if you

00:49:40.030 --> 00:49:43.590
can do different settings for that um but it

00:49:43.590 --> 00:49:48.690
generally only works in headings as the uh formatting

00:49:48.690 --> 00:49:50.730
like the formatting will only show in headings

00:49:50.730 --> 00:49:54.710
oh so it's all plain text right like it's all

00:49:54.710 --> 00:49:56.750
plain text you could always use it as it to do

00:49:56.750 --> 00:49:59.070
but the formatting and the syntax highlighting

00:49:59.070 --> 00:50:01.969
for org mode is like it's based on the heading

00:50:02.510 --> 00:50:04.750
So the idea, I guess, that you create a heading

00:50:04.750 --> 00:50:07.889
and you just put all of the details for that

00:50:07.889 --> 00:50:10.289
to do inside that heading. Is that like correct?

00:50:10.869 --> 00:50:13.090
And then you have another to do with another

00:50:13.090 --> 00:50:15.869
heading and you keep going down the list for

00:50:15.869 --> 00:50:19.010
more to do's. So let's say you have a to do with

00:50:19.010 --> 00:50:21.610
like, you know, 50 lines of notes underneath

00:50:21.610 --> 00:50:25.929
it. Then those all apply to that heading and

00:50:25.929 --> 00:50:30.409
then you create another one. Oh, OK. OK. Got

00:50:30.409 --> 00:50:33.539
it. Got it. So. I've marked this to do as done

00:50:33.539 --> 00:50:35.679
then. Okay. That's what you were showing up on

00:50:35.679 --> 00:50:38.320
your screen, correct? That's the first thing

00:50:38.320 --> 00:50:43.139
that we went over, right? Yep. Yep. Okay. Got

00:50:43.139 --> 00:50:46.539
it. Okay. Is there something else you want to

00:50:46.539 --> 00:50:48.940
show regarding that? Okay. So I noticed that

00:50:48.940 --> 00:50:51.579
you have in your example, I'm looking at your

00:50:51.579 --> 00:50:54.639
screen right now, you have the main to do, and

00:50:54.639 --> 00:50:58.980
then you have two headings inside that to do,

00:50:59.059 --> 00:51:04.039
right? Yep. is that something that you usually

00:51:04.039 --> 00:51:07.360
do like you can do it however you really want

00:51:07.360 --> 00:51:09.539
to generally that's how i would do it i usually

00:51:09.539 --> 00:51:11.719
would say like uh because you're recording my

00:51:11.719 --> 00:51:15.420
screen here one sec uh like generally what i

00:51:15.420 --> 00:51:18.900
would do it is yes like i would have like my

00:51:18.900 --> 00:51:22.280
project generally and then within that project

00:51:22.280 --> 00:51:24.739
i would have the tasks that i need to do within

00:51:24.739 --> 00:51:29.079
that project so like for here for example you

00:51:29.079 --> 00:51:31.900
know there's there's my project there's my subheading

00:51:31.900 --> 00:51:35.320
of that project there's my other subheading of

00:51:35.320 --> 00:51:37.980
that project and the information that's within

00:51:37.980 --> 00:51:41.119
that etc that's generally how i do it you can

00:51:41.119 --> 00:51:43.940
again it's plain text so like you can do it however

00:51:43.940 --> 00:51:48.739
you want to but um i know that org syntax it

00:51:48.739 --> 00:51:50.400
does the highlighting and everything generally

00:51:50.400 --> 00:51:53.179
when you do the subheadings so i was like okay

00:51:53.179 --> 00:51:55.219
well i'm just going to adapt that into my workflow

00:51:55.219 --> 00:51:58.139
and that's how i've always done it okay okay

00:51:58.139 --> 00:52:00.739
so for example right let me switch back to my

00:52:00.739 --> 00:52:06.900
screen and um let's say that i wanna add another

00:52:06.900 --> 00:52:11.500
one here uh this would be level three right so

00:52:11.500 --> 00:52:14.900
it has to be three asterisks right correct and

00:52:14.900 --> 00:52:17.559
and and again you can do control enter on that

00:52:17.559 --> 00:52:20.780
previous heading to very quickly do another heading

00:52:22.539 --> 00:52:24.199
Yeah, and it will actually take it underneath,

00:52:24.460 --> 00:52:27.679
and that's your to -do. Or then you can hit Alt

00:52:27.679 --> 00:52:33.760
-J or Alt -H, and that will change the depth

00:52:33.760 --> 00:52:37.940
of it. Oh, Alt -J. Yeah, if you hit Alt -J right

00:52:37.940 --> 00:52:43.360
now, it'll take it to 3 asterisk. Alt -J? Yeah,

00:52:43.460 --> 00:52:46.420
Alt -J. Oh, that's what I'm typing. Hold on,

00:52:46.440 --> 00:52:50.920
my Alt is not configured. Command -J. Command

00:52:50.920 --> 00:52:54.440
-J. Sorry. No command. Hold on. Hold on. Hold

00:52:54.440 --> 00:52:58.099
on. Command. What's the word? Command L. Sorry.

00:52:58.860 --> 00:53:03.599
Command L. No. Or Alt L. No. That doesn't work.

00:53:04.039 --> 00:53:06.739
It must be something with my keyboard, I guess.

00:53:06.980 --> 00:53:09.940
Or control. Yeah. I can do it the knee open way,

00:53:10.059 --> 00:53:14.099
which is control. Hold on. Oh, no. I opened another

00:53:14.099 --> 00:53:16.760
tab. God damn it. And how do I switch back to

00:53:16.760 --> 00:53:21.280
the other tab? Just hit space. B, K, that will

00:53:21.280 --> 00:53:25.000
kill the previous. Oh, is that a new tab? Yeah,

00:53:25.059 --> 00:53:31.300
I opened the new tab, I think. Space tab D. Space

00:53:31.300 --> 00:53:37.239
tab? D. D, okay. Yeah, that kills, like D is

00:53:37.239 --> 00:53:47.480
delete, it kills the tab. Space. Space tab. Oh,

00:53:47.579 --> 00:53:52.969
tab D. kill the tab just gonna write those down

00:53:52.969 --> 00:53:55.710
yeah so that would essentially be like your tmux

00:53:55.710 --> 00:54:00.590
workspace right so every tab would be a tmux

00:54:00.590 --> 00:54:04.610
okay correct and then you would essentially be

00:54:04.610 --> 00:54:07.210
killing the session with that um if you just

00:54:07.210 --> 00:54:08.650
go to my screen really quick i'll just show you

00:54:08.650 --> 00:54:12.909
what i mean yep yep so for example like what

00:54:12.909 --> 00:54:16.110
is saying alt this is alt l like it takes it

00:54:16.110 --> 00:54:18.980
down you see what i'm saying Oh, yeah, it increases

00:54:18.980 --> 00:54:22.179
the indentation. Correct. Or you could go back,

00:54:22.199 --> 00:54:25.400
back or forward, whichever. Right. For me, that's

00:54:25.400 --> 00:54:30.539
Alt L and Alt H. Sorry, I use Colmax, so I always

00:54:30.539 --> 00:54:33.880
have to think about what keys I'm hitting. OK,

00:54:34.059 --> 00:54:36.739
I don't know. OK, look, so the way that I do

00:54:36.739 --> 00:54:39.760
it in NeoVim is if I'm in insert mode and I type

00:54:39.760 --> 00:54:43.960
Control D goes back and Control T goes. That

00:54:43.960 --> 00:54:46.940
works for you. OK, awesome. Awesome. Yeah. And

00:54:46.940 --> 00:54:49.019
in normal mode, you should do it with shift,

00:54:49.239 --> 00:54:53.440
square brackets. No, it's not square bracket.

00:54:53.519 --> 00:54:58.039
It's the symbol, this one. You cannot see it

00:54:58.039 --> 00:55:02.519
there. This. Yeah, greater than. Yep. Yeah. Greater

00:55:02.519 --> 00:55:05.400
than two times or lesser than two times to go

00:55:05.400 --> 00:55:08.760
back. Oh, there you go. Normal mode. So it seems

00:55:08.760 --> 00:55:10.360
that it works. That works. There are actually

00:55:10.360 --> 00:55:12.980
multiple methods of doing it. I'm just testing

00:55:12.980 --> 00:55:14.400
all those right now, and they all work for me

00:55:14.400 --> 00:55:16.909
as well. Oh. Wonderful. That's all default. That's

00:55:16.909 --> 00:55:20.289
all default behavior then. Okay. Okay. So it

00:55:20.289 --> 00:55:22.929
works. It translates from NeoVim quite well from

00:55:22.929 --> 00:55:26.650
Vim, I think. Okay. So this is another to do

00:55:26.650 --> 00:55:33.230
here. Record video, right? So, and I just put

00:55:33.230 --> 00:55:42.679
text inside this to do, right? So, okay. And

00:55:42.679 --> 00:55:46.940
it automatically fixes the indentation of the

00:55:46.940 --> 00:55:49.780
text, right? So I can know that this belongs

00:55:49.780 --> 00:55:52.599
to this to do, right? Yeah. And if you hit tab

00:55:52.599 --> 00:55:54.800
on that to do, it'll actually wrap all of that

00:55:54.800 --> 00:55:58.119
as well. So it's going to fold it. Okay. Correct.

00:55:58.280 --> 00:56:02.860
Yeah. Okay. And I can mark that as not done.

00:56:03.039 --> 00:56:08.239
What if I want to create inside this to do level

00:56:08.239 --> 00:56:15.349
three heading, right? Like I want to separate

00:56:15.349 --> 00:56:19.489
this in in two to do's of level three, right?

00:56:19.570 --> 00:56:21.610
Everything is inside this level two heading.

00:56:21.750 --> 00:56:25.010
I want to have two level three headings inside.

00:56:25.190 --> 00:56:28.289
If I hit control enter here at the end, it's

00:56:28.289 --> 00:56:30.230
going to create a level two. How would you do

00:56:30.230 --> 00:56:34.010
it? Just manually, right? Yeah, you could like

00:56:34.010 --> 00:56:36.210
I probably there's probably a way to do it. I

00:56:36.210 --> 00:56:39.610
usually just like do control enter and then take

00:56:39.610 --> 00:56:43.230
that and move it. uh over so like that and then

00:56:43.230 --> 00:56:45.489
i'll hit either control t or whatever exactly

00:56:45.489 --> 00:56:49.170
okay okay okay that's generally how i do it task

00:56:49.170 --> 00:56:53.949
one control enter task pass two and i can move

00:56:53.949 --> 00:56:58.110
stuff from here if i hit p okay and i can move

00:56:58.110 --> 00:57:01.769
these two to the other one okay and if i fold

00:57:01.769 --> 00:57:06.670
this gonna fold everything nice and this unfolds

00:57:06.670 --> 00:57:09.860
only that specific task yeah and if you hit shift

00:57:09.860 --> 00:57:13.559
tab the whole file will unfold or fold so shift

00:57:13.559 --> 00:57:17.679
tab will like yeah and then again and again and

00:57:17.679 --> 00:57:19.940
the whole thing will unfold there you go so like

00:57:19.940 --> 00:57:21.780
if you have like a gazillion tasks you might

00:57:21.780 --> 00:57:24.519
have to i always fold everything up and then

00:57:24.519 --> 00:57:26.739
i like focus really only on the thing that i'm

00:57:26.739 --> 00:57:33.039
doing you know without knowing i replicated whatever

00:57:33.039 --> 00:57:37.019
this folding and all that is in the event i just

00:57:37.019 --> 00:57:39.980
need it because i use the outline a lot right

00:57:39.980 --> 00:57:44.159
so if i switch here to um let me see to this

00:57:44.159 --> 00:57:46.880
right this is the file without knowing i kind

00:57:46.880 --> 00:57:49.579
of did the same thing in the oven yeah because

00:57:49.579 --> 00:57:52.739
i like to fold everything level one level two

00:57:52.739 --> 00:57:55.079
if i want to see level two and level three i

00:57:55.079 --> 00:57:58.539
have another key map right so because it allows

00:57:58.539 --> 00:58:02.719
me to navigate faster so oh totally so so i don't

00:58:02.719 --> 00:58:06.420
have to There's no configuration you'd have.

00:58:06.500 --> 00:58:10.460
No configuration, yeah. They've thought of a

00:58:10.460 --> 00:58:12.820
lot of things. They've thought of everything

00:58:12.820 --> 00:58:17.119
with org mode. Honestly, I was thinking about

00:58:17.119 --> 00:58:21.159
creating a system with Task Warrior and all that

00:58:21.159 --> 00:58:25.159
stuff to try to replicate it. There's no replicating

00:58:25.159 --> 00:58:29.590
it. They've thought of everything. It was like

00:58:29.590 --> 00:58:32.889
hubris on my part to even think that I was capable

00:58:32.889 --> 00:58:35.550
of doing something along those lines. That you

00:58:35.550 --> 00:58:37.909
were going to invent the wheel in Emacs, right?

00:58:37.949 --> 00:58:39.650
Yeah, I was going to reinvent the wheel that

00:58:39.650 --> 00:58:43.489
had already been rolling things for 5 ,000 years.

00:58:43.730 --> 00:58:47.989
Yeah, because my granddad, my grandfather probably

00:58:47.989 --> 00:58:53.170
uses Emacs. Just old people. People are going

00:58:53.170 --> 00:58:56.250
to hate me. Dude, no, like Emacs has been around

00:58:56.250 --> 00:58:59.989
for almost 50 years. Yeah. That's staying power,

00:59:00.110 --> 00:59:03.309
man. They thought about everything already, right?

00:59:03.690 --> 00:59:07.349
Guys with much bigger beards than I have thought

00:59:07.349 --> 00:59:10.309
of everything. For sure. And wider beards. Exactly.

00:59:11.010 --> 00:59:16.400
All right. So this is good. I don't think I have

00:59:16.400 --> 00:59:19.260
questions. Let's schedule something. Let's do

00:59:19.260 --> 00:59:21.519
that for kind of like the final thing. Oh, yeah,

00:59:21.519 --> 00:59:23.960
yeah. Let's do it. So you want to record that

00:59:23.960 --> 00:59:28.500
video. Let's say Control -C. Where? Here? Where

00:59:28.500 --> 00:59:31.420
I'm at right now? Control -C? Yeah, Control -C,

00:59:31.440 --> 00:59:39.719
Control -S. Control -C, Control -S. Boom. I didn't

00:59:39.719 --> 00:59:44.599
like those key maps. Hold on. Control -C. that's

00:59:44.599 --> 00:59:47.139
a that's an emacs control because so control

00:59:47.139 --> 00:59:50.900
is like the uh there's a adage in the emac community

00:59:50.900 --> 00:59:54.599
called emacs pinky yeah control is like right

00:59:54.599 --> 00:59:57.300
under your pinky and like you actually like go

00:59:57.300 --> 00:59:59.199
to break your pinky because you keep hitting

00:59:59.199 --> 01:00:01.860
you have to control so much right yeah so um

01:00:01.860 --> 01:00:03.880
because you have a because you have a glove 80

01:00:03.880 --> 01:00:07.000
look into home row mods dude control is literally

01:00:07.000 --> 01:00:10.760
under my middle finger now oh yeah i have thought

01:00:10.760 --> 01:00:13.239
about home row mods as well you know but it's

01:00:13.239 --> 01:00:16.480
dude they are game changing they are game yeah

01:00:16.480 --> 01:00:19.780
i have to implement them but but again i want

01:00:19.780 --> 01:00:23.260
to type the same way on my laptop keyboard the

01:00:23.260 --> 01:00:25.760
exact same way that i do it in the club 80 so

01:00:25.760 --> 01:00:27.960
that's why i have not implemented them already

01:00:27.960 --> 01:00:31.619
but i'll see what i what i what i come up with

01:00:31.619 --> 01:00:35.280
i'm too far gone i'm too far gone like i use

01:00:35.280 --> 01:00:39.179
colmac dh with home row mods and i've Like I

01:00:39.179 --> 01:00:42.039
can't even type in QWERTY anymore. That's the

01:00:42.039 --> 01:00:44.139
other thing, you know, imagine I am teaching

01:00:44.139 --> 01:00:47.119
stuff to my daughter, right? I know, I know.

01:00:47.420 --> 01:00:49.579
I've thought about it too. I'm like, oh, I have

01:00:49.579 --> 01:00:52.000
to teach my daughter how to type. Oh my goodness.

01:00:52.119 --> 01:00:54.920
What am I going to do? Let's both learn to type.

01:00:55.059 --> 01:00:57.480
How did it go with the Comac switch? When did

01:00:57.480 --> 01:01:00.820
you switch to Comac? A year ago. A year ago in

01:01:00.820 --> 01:01:05.000
January. So yeah, I've been using it for about

01:01:05.000 --> 01:01:08.019
14 months. And you wanted to be one of them cool

01:01:08.019 --> 01:01:12.000
kids or was there a reason? No, so I wrote a

01:01:12.000 --> 01:01:16.099
book and I wrote essentially about 100 ,000 words

01:01:16.099 --> 01:01:19.219
for that book. By the end of it, my fingers were

01:01:19.219 --> 01:01:24.860
dying. So what I did was, it was actually pragmatic,

01:01:24.980 --> 01:01:27.840
was I was like, how do I continue to type this

01:01:27.840 --> 01:01:30.920
much all the time? And Colmax seems to be the

01:01:30.920 --> 01:01:33.199
answer for me because I've... I've probably typed

01:01:33.199 --> 01:01:35.559
probably over a million words using Colmac. I

01:01:35.559 --> 01:01:39.400
have never experienced that hand pain ever again.

01:01:40.119 --> 01:01:42.440
Oh, man, you know what? Because I have been feeling

01:01:42.440 --> 01:01:45.059
pain lately. Let's say that I'm creating an article,

01:01:45.219 --> 01:01:47.760
right? A blog post article. I usually type a

01:01:47.760 --> 01:01:50.260
lot of stuff in those, right? By the end of typing

01:01:50.260 --> 01:01:51.960
an article, let's say that I'm typing it for

01:01:51.960 --> 01:01:54.460
two hours, right? Because when I start, I just

01:01:54.460 --> 01:01:57.559
finish it, right? Let's say it's two hours. By

01:01:57.559 --> 01:02:00.280
the end of it, my hands, my fingers hurt, right?

01:02:00.940 --> 01:02:04.820
Or if I type a lot of stuff, they start hurting.

01:02:06.780 --> 01:02:12.460
It sucks to switch over because you're a baby

01:02:12.460 --> 01:02:15.340
again, right? Yeah. And even worse than a baby,

01:02:15.400 --> 01:02:18.019
man. Oh, yeah. No, but I threw myself into it

01:02:18.019 --> 01:02:19.539
and I was like, I'm just going to do it. And

01:02:19.539 --> 01:02:23.539
it took me probably about a month to get up to

01:02:23.539 --> 01:02:26.480
about 70 words a minute. But I would say that

01:02:26.480 --> 01:02:28.880
I'm... i'm faster now than i was in query i'm

01:02:28.880 --> 01:02:31.760
typing like probably about 100 105 words a minute

01:02:31.760 --> 01:02:34.539
with it and it is comfortable you do a lot of

01:02:34.539 --> 01:02:38.739
like rolling so like it it feels really cool

01:02:38.739 --> 01:02:41.039
to type because you're like rolling over the

01:02:41.039 --> 01:02:44.619
keys as opposed to like hitting individual you

01:02:44.619 --> 01:02:46.539
see what i'm saying it's like more like rolling

01:02:46.539 --> 01:02:48.760
yeah yeah because they're in a more natural position

01:02:48.760 --> 01:02:51.960
for the english language i guess right yes yeah

01:02:52.489 --> 01:02:56.050
So it's I mean, it's esoteric and like I don't

01:02:56.050 --> 01:02:58.769
recommend everybody do it. But for me, that spends

01:02:58.769 --> 01:03:00.869
way too much time on a computer. It was like

01:03:00.869 --> 01:03:03.869
it was well worth the investment in time and

01:03:03.869 --> 01:03:08.110
energy to do it. I don't think about it. I just

01:03:08.110 --> 01:03:09.909
want to go through the pain because I know it's

01:03:09.909 --> 01:03:12.389
going to be really painful to learn. I'm laughing

01:03:12.389 --> 01:03:17.800
and I'm shaking my desk. Yeah, me too. But yeah,

01:03:17.800 --> 01:03:20.539
so now you're able to literally schedule it to

01:03:20.539 --> 01:03:22.440
whatever date you want. You can just type in

01:03:22.440 --> 01:03:26.579
a time, like 10 a .m. or whatever. So how do

01:03:26.579 --> 01:03:29.860
I select a date? Do I use Vim keybinds? Can I

01:03:29.860 --> 01:03:32.519
switch? I believe I've changed this behavior

01:03:32.519 --> 01:03:35.380
for me, but I think it is literally control and

01:03:35.380 --> 01:03:38.239
then your Vim keys. So it's control and then

01:03:38.239 --> 01:03:41.780
whatever. Oh, yeah, yeah, yeah. Control. Okay,

01:03:41.880 --> 01:03:44.940
so I can select a date that way. Let's say that.

01:03:45.400 --> 01:03:50.480
can i go to today oh with the dot right uh just

01:03:50.480 --> 01:03:52.619
you can even just hover over today which is the

01:03:52.619 --> 01:03:55.179
eighth i want to say there's the ninth it's the

01:03:55.179 --> 01:03:57.019
eighth oh no but let's say that i'm i'm lost

01:03:57.019 --> 01:04:02.440
i'm here how can i go to today's day oh uh that's

01:04:02.440 --> 01:04:05.159
a good question it says there at the bottom dot

01:04:05.159 --> 01:04:07.699
today but i don't know what happens if i press

01:04:07.699 --> 01:04:12.980
it if it's just gonna try it hit dot okay so

01:04:12.980 --> 01:04:16.159
it just moves me there wow they've literally

01:04:16.159 --> 01:04:19.940
thought of everything yeah definitely so let's

01:04:19.940 --> 01:04:22.039
say that i want to schedule this record video

01:04:22.039 --> 01:04:25.539
for tomorrow i just go over here and what now

01:04:25.539 --> 01:04:28.820
type of time like let's say it's 10 a .m just

01:04:28.820 --> 01:04:33.360
type in 10 i always yeah i always do 10 colon

01:04:33.880 --> 01:04:36.519
zero zero um i think it has natural language

01:04:36.519 --> 01:04:41.219
like you could do 10 a .m like just 10 1 0 a

01:04:41.219 --> 01:04:43.239
.m i think it actually will work as well oh yeah

01:04:43.239 --> 01:04:47.340
it works that's quite nice you know yes yeah

01:04:47.340 --> 01:04:50.820
yes there you go so like you could you could

01:04:50.820 --> 01:04:54.659
just and then you hit enter and then you have

01:04:54.659 --> 01:05:00.239
a scheduled tag now for that And yeah, so let's

01:05:00.239 --> 01:05:02.360
do one final thing and add this to your org agenda.

01:05:02.599 --> 01:05:08.019
So hit control C. Control C. Open bracket. Open

01:05:08.019 --> 01:05:11.119
bracket. Which one is open bracket? This one.

01:05:11.420 --> 01:05:15.000
The... No, I don't think I... No, no, no, no.

01:05:15.480 --> 01:05:19.920
Formula debugging has been turned on. I did open

01:05:19.920 --> 01:05:23.340
squiggly bracket instead. Okay, no, no. Open

01:05:23.340 --> 01:05:26.219
like a square bracket. Sorry. So what did you

01:05:26.219 --> 01:05:29.500
say? Control C. Control C, open square bracket.

01:05:29.719 --> 01:05:32.760
Open square brackets. That file is added to the

01:05:32.760 --> 01:05:37.500
front of your file list. And now hit space O.

01:05:37.820 --> 01:05:40.380
Hold on. Wait, wait, wait, wait, wait, wait,

01:05:40.380 --> 01:05:44.980
wait. Before I forget this. There's so many keybinds,

01:05:44.980 --> 01:05:47.599
man. It is like literally the biggest rabbit

01:05:47.599 --> 01:05:51.949
hole ever. Control C. And what was the last one

01:05:51.949 --> 01:05:54.789
that you said? Open square bracket. Open square

01:05:54.789 --> 01:05:57.969
bracket. Open square bracket. Okay. This is two.

01:05:58.889 --> 01:06:02.050
That will add a file to your org agenda. And

01:06:02.050 --> 01:06:04.750
then the same thing with a closed square bracket

01:06:04.750 --> 01:06:14.010
will delete it from your agenda. Control C. Delete

01:06:14.010 --> 01:06:18.519
file from org. I'm not going to work on this

01:06:18.519 --> 01:06:20.480
file too much. I'm just going to upload it so

01:06:20.480 --> 01:06:23.400
people following the video will understand what's

01:06:23.400 --> 01:06:25.880
going on. Other people going to my blog will

01:06:25.880 --> 01:06:27.840
be like, what is he talking about? Yeah, they're

01:06:27.840 --> 01:06:30.579
not going to get it. So it's all good to move

01:06:30.579 --> 01:06:34.460
between dates. It was control. And then your

01:06:34.460 --> 01:06:41.440
Vim keys. To move between dates in calendar.

01:06:42.059 --> 01:06:44.559
Yeah. And then to get into the calendar is control

01:06:44.559 --> 01:06:50.860
C, control F. Oh, that one. Yeah. Control. C.

01:06:51.039 --> 01:06:59.480
Control. S. S. Open the calendar? Yes. That's

01:06:59.480 --> 01:07:02.530
to bring it up, right? Yes. If you want to go

01:07:02.530 --> 01:07:03.969
to my screen really quickly, I'm going to show

01:07:03.969 --> 01:07:06.050
you something. Oh, I had it written down already

01:07:06.050 --> 01:07:08.329
here. Control C, control S. Let me switch to

01:07:08.329 --> 01:07:11.789
your screen there. Yeah. So, so like, cause there's

01:07:11.789 --> 01:07:14.230
so many, like there's a gazillion key binds,

01:07:14.349 --> 01:07:18.269
right? If you're lost on a Mac, you can hit command

01:07:18.269 --> 01:07:20.949
X, which is meta X, right? And let's say I want

01:07:20.949 --> 01:07:26.030
to calendar add or calendar. What's the word

01:07:26.030 --> 01:07:29.739
I'm looking for? You can see how many commands

01:07:29.739 --> 01:07:33.119
are related to the calendar in Emacs here. I

01:07:33.119 --> 01:07:37.960
guess it would actually be schedule. Schedule.

01:07:38.500 --> 01:07:47.119
There you go. Org schedule. You see this? I know

01:07:47.119 --> 01:07:50.000
there's a command to do this, but I can't remember

01:07:50.000 --> 01:07:55.679
what it is. uh hit m meta x or alt x on linux

01:07:55.679 --> 01:07:58.619
and windows or command x on mac and start just

01:07:58.619 --> 01:08:01.139
typing things and you'll eventually find the

01:08:01.139 --> 01:08:03.719
command because it's all self -documented right

01:08:03.719 --> 01:08:08.159
okay i'm writing here so this helps there's something

01:08:08.159 --> 01:08:12.199
in neovim for this as well i do command k and

01:08:12.199 --> 01:08:15.000
uh i can search for my key maps basically right

01:08:15.000 --> 01:08:18.579
so i'm just gonna type in here find the key maps

01:08:18.579 --> 01:08:23.029
basically right Yeah, so it's also not only your

01:08:23.029 --> 01:08:25.529
key maps, but literally every command that Emacs

01:08:25.529 --> 01:08:29.590
has available to it. So you could write a list

01:08:29.590 --> 01:08:32.130
function and call that in your configuration.

01:08:32.510 --> 01:08:34.930
That function will be available in this list.

01:08:35.090 --> 01:08:37.130
Literally everything that Emacs has available

01:08:37.130 --> 01:08:41.250
to it is in this list. Okay, so it's not just

01:08:41.250 --> 01:08:44.930
key maps. It's everything. It's like the whole

01:08:44.930 --> 01:08:49.329
shebang, the whole system. find every command

01:08:49.329 --> 01:08:53.789
basically right yes every command every function

01:08:53.789 --> 01:08:58.229
every everything just everything it's it's the

01:08:58.229 --> 01:09:00.489
most powerful command in emacs i would say because

01:09:00.489 --> 01:09:03.710
you literally can just search for anything that

01:09:03.710 --> 01:09:06.550
you need to do wonderful all right all right

01:09:06.550 --> 01:09:10.510
so what what now then okay so now that you've

01:09:10.510 --> 01:09:12.470
scheduled it and you've added it to your org

01:09:12.470 --> 01:09:16.609
agenda you can hit uh space oc So Leader OC,

01:09:16.850 --> 01:09:18.710
and that should open a calendar, I want to say.

01:09:19.409 --> 01:09:22.489
You don't have the calendar package. We'll have

01:09:22.489 --> 01:09:26.090
to add that at a later date. Yep, I think this

01:09:26.090 --> 01:09:29.210
is enough for now. We can go over that other

01:09:29.210 --> 01:09:31.670
package that you mentioned, the calendar one,

01:09:31.810 --> 01:09:35.010
and do the other things in the video. Of course,

01:09:35.010 --> 01:09:37.649
if you have the time and if you want to help

01:09:37.649 --> 01:09:42.159
out. Absolutely. yeah but we can uh this is fun

01:09:42.159 --> 01:09:44.600
man this is like it's also jogging my brain to

01:09:44.600 --> 01:09:46.020
like remember everything because everything is

01:09:46.020 --> 01:09:50.079
like essentially it's like muscle memory at this

01:09:50.079 --> 01:09:51.960
point so like i have to like go through and like

01:09:51.960 --> 01:09:54.840
think about is is it that command or is it that

01:09:54.840 --> 01:09:57.960
command yeah so it's it it helps me even to remember

01:09:57.960 --> 01:10:00.539
things so yeah and the thing is that you're probably

01:10:00.539 --> 01:10:04.680
not using vanilla doom emacs you configured it

01:10:04.680 --> 01:10:09.409
for yourself so if i would go to I was just going

01:10:09.409 --> 01:10:10.670
to say, there's a lot of things that I've added

01:10:10.670 --> 01:10:15.909
to it too. Yeah. So if I go to the vanilla LazyVim

01:10:15.909 --> 01:10:18.930
distribution, right? I wouldn't know a lot of

01:10:18.930 --> 01:10:20.989
things because I already configured mine to my

01:10:20.989 --> 01:10:23.350
needs. So yeah, that makes it a little bit more

01:10:23.350 --> 01:10:25.649
difficult. And what if I want to use your own

01:10:25.649 --> 01:10:28.050
config? Is that possible? Like get your packages

01:10:28.050 --> 01:10:30.189
and all that so that I don't have to go through

01:10:30.189 --> 01:10:35.819
all? Yeah. So my .files, I actually have. a lot

01:10:35.819 --> 01:10:38.760
of my emacs configuration up there um there's

01:10:38.760 --> 01:10:41.560
a folder in it called you want to show your your

01:10:41.560 --> 01:10:44.579
files sure sure i'll show my dot files all right

01:10:44.579 --> 01:10:47.340
uh yeah you can go to my screen i'll show it

01:10:47.340 --> 01:10:51.020
here so this is like my base doom dot file does

01:10:51.020 --> 01:10:53.640
that show up good for you yep yep a little bit

01:10:53.640 --> 01:10:56.399
yeah so with it it's good oh here i'll bump it

01:10:56.399 --> 01:10:58.880
up a little bit so there's um i have a private

01:10:58.880 --> 01:11:00.539
config so there's a couple things that i have

01:11:00.539 --> 01:11:02.939
like my org calendar credentials and everything

01:11:02.939 --> 01:11:05.460
are within my private i don't i don't uh source

01:11:05.460 --> 01:11:08.840
control that but within my lisp within my lisp

01:11:08.840 --> 01:11:12.520
uh directory there are various functions that

01:11:12.520 --> 01:11:15.520
i've written to like create a daily file because

01:11:15.520 --> 01:11:17.239
we were talking about you like your daily stuff

01:11:17.239 --> 01:11:20.560
yep um i i create a daily file with this so like

01:11:20.560 --> 01:11:24.720
i literally hit meta x create daily file and

01:11:24.720 --> 01:11:28.239
there's my daily file right here uh for april

01:11:28.239 --> 01:11:30.659
8th that's literally just been created by that

01:11:30.659 --> 01:11:35.039
uh command okay um So there's various things

01:11:35.039 --> 01:11:37.300
that I've done in here. Done refile, like I refiled

01:11:37.300 --> 01:11:41.460
my to -dos into a singular done file with the

01:11:41.460 --> 01:11:44.220
date. So it literally just shows like everything

01:11:44.220 --> 01:11:48.680
that I've ever done in date format. So I could

01:11:48.680 --> 01:11:50.880
like go back and be like, I did this on this

01:11:50.880 --> 01:11:53.659
date or whatever. And it's searchable all in

01:11:53.659 --> 01:11:57.539
one file. Okay. this meeting assistant thing

01:11:57.539 --> 01:11:59.880
is I don't have it working just perfectly yet,

01:11:59.920 --> 01:12:02.539
but like you send me a meeting link and I add

01:12:02.539 --> 01:12:06.279
it to my agenda. It actually will give me a notification

01:12:06.279 --> 01:12:09.779
two minutes before the meeting starts to go to

01:12:09.779 --> 01:12:13.899
the link in zoom or Jitsi or whatever. Um, I'm

01:12:13.899 --> 01:12:16.460
not sure if it's, I don't think it's fully working

01:12:16.460 --> 01:12:18.140
yet. I have to, there's a couple of things I

01:12:18.140 --> 01:12:19.680
need to do here, but you can literally like,

01:12:19.739 --> 01:12:21.500
you'll see like there's the links and everything

01:12:21.500 --> 01:12:26.140
that are defined and no, there we go. yeah it's

01:12:26.140 --> 01:12:29.859
i i'm not a i'm not a lisp wizard at all uh and

01:12:29.859 --> 01:12:33.180
i use uh i use quad a lot to write some of these

01:12:33.180 --> 01:12:36.199
functions me too with neobim stuff i'm not a

01:12:36.199 --> 01:12:40.220
lua expert so i use ai a lot yeah i and i mean

01:12:40.220 --> 01:12:43.079
it's pretty good with lisp stuff but i want to

01:12:43.079 --> 01:12:45.100
get to the point where i'm like fully understanding

01:12:45.100 --> 01:12:47.800
it and using it like when i write a function

01:12:47.800 --> 01:12:49.979
i'm like i generally am not like just write me

01:12:49.979 --> 01:12:52.420
this function i'm like explain every step of

01:12:52.420 --> 01:12:57.569
it so that i can understand A couple other things

01:12:57.569 --> 01:12:59.390
in here, like you can start a Pomodoro timer.

01:12:59.989 --> 01:13:02.729
This pop -up Dervish browser is literally like

01:13:02.729 --> 01:13:06.630
something that I use to, oh, it's on my other

01:13:06.630 --> 01:13:08.930
screen sec. It's literally like a file browser

01:13:08.930 --> 01:13:13.789
that I use for everything in Emacs. What else?

01:13:14.050 --> 01:13:17.050
Yeah, there's like a gazillion different things

01:13:17.050 --> 01:13:19.329
that I have, but they're all within my .files.

01:13:19.390 --> 01:13:21.310
I can send you my repo and you can post it in

01:13:21.310 --> 01:13:23.880
the comments if you want. yep i will i will you

01:13:23.880 --> 01:13:26.800
want to open your dot files in the browser real

01:13:26.800 --> 01:13:30.579
quick before these are public too so like any

01:13:30.579 --> 01:13:33.699
actually people are yeah people are following

01:13:33.699 --> 01:13:37.720
it and such um yeah so here's my my dot file

01:13:37.720 --> 01:13:41.399
repo i uh i try to keep everything private out

01:13:41.399 --> 01:13:44.560
of it so it's okay everything that's essentially

01:13:44.560 --> 01:13:48.260
functional for making my emacs configuration

01:13:48.260 --> 01:13:52.720
work is is in here so okay and i even I even

01:13:52.720 --> 01:13:54.520
have a couple of configurations to like change

01:13:54.520 --> 01:13:57.899
some of the base emac stuff. Like you can, most

01:13:57.899 --> 01:14:00.020
people can just completely ignore that. But,

01:14:00.020 --> 01:14:03.520
uh, yeah, there's snippets. Like you can go pretty

01:14:03.520 --> 01:14:06.619
in depth with it. Like if you wanted to write

01:14:06.619 --> 01:14:08.979
snippets for stuff that you always write all

01:14:08.979 --> 01:14:13.039
of the time, for example. Yeah. Like literally

01:14:13.039 --> 01:14:15.680
for ending my blog posts, I have a snippet to

01:14:15.680 --> 01:14:21.100
just. oh and my blog post for example or um you

01:14:21.100 --> 01:14:23.199
know create the front matter for a blog post

01:14:23.199 --> 01:14:25.300
or any of that sort of thing those are pretty

01:14:25.300 --> 01:14:27.640
powerful too but i mean we're just we're getting

01:14:27.640 --> 01:14:30.560
into the yeah we're just getting so much yeah

01:14:30.560 --> 01:14:33.399
there's just so much you can do so i'll leave

01:14:33.399 --> 01:14:36.760
it at that yeah i'd like to if you have time

01:14:36.760 --> 01:14:38.560
and if you're willing to do it you know i'd like

01:14:38.560 --> 01:14:40.840
to continue like this series because i don't

01:14:40.840 --> 01:14:43.810
want to touch the emacs configuration I just

01:14:43.810 --> 01:14:46.369
want to leave it where it is, the same way that

01:14:46.369 --> 01:14:48.609
I did it with the last video, right? Oh, that

01:14:48.609 --> 01:14:50.510
sounds like a plan, man. Yeah, so that people

01:14:50.510 --> 01:14:54.210
following the video can just continue where I

01:14:54.210 --> 01:14:57.350
left off. That sounds like a plan. I mean, if

01:14:57.350 --> 01:15:01.229
I can get one more person to use Emacs, I will

01:15:01.229 --> 01:15:04.689
have evangelized properly. You want to quickly

01:15:04.689 --> 01:15:06.909
show your YouTube channel, Josh, if you have

01:15:06.909 --> 01:15:12.210
it there? So people can go and subscribe to your

01:15:12.210 --> 01:15:15.220
channel. It's on my screen. There's my YouTube

01:15:15.220 --> 01:15:18.659
channel if you want to come by and hang out with

01:15:18.659 --> 01:15:23.739
me. I do stuff, technology, theology, kind of

01:15:23.739 --> 01:15:26.140
first principle stuff. I don't know. I just ramble

01:15:26.140 --> 01:15:29.880
on my YouTube channel and it's kind of fun. And

01:15:29.880 --> 01:15:32.899
what content are you going to be? working on

01:15:32.899 --> 01:15:36.399
in the future like um is it going to be max or

01:15:36.399 --> 01:15:40.100
more emacs related stuff um kind of from this

01:15:40.100 --> 01:15:44.420
point on has been mostly emacs related and uh

01:15:44.420 --> 01:15:46.779
i'm going to continue with that pretty drastically

01:15:46.779 --> 01:15:50.359
um and yeah just some like talking head stuff

01:15:50.359 --> 01:15:53.720
what's on my mind all of that essentially the

01:15:53.720 --> 01:15:57.779
the whole jest of the channel is truth and technology

01:15:57.779 --> 01:16:00.439
so that's uh that's what i cover in my channel

01:16:00.720 --> 01:16:03.260
Yeah, but not niche down only to Emacs, right?

01:16:03.340 --> 01:16:06.960
So it could be basically anything. Yeah. Mostly,

01:16:07.039 --> 01:16:09.979
like, I am a huge advocate for free and open

01:16:09.979 --> 01:16:13.119
systems. So it's, you know, Unix -based stuff.

01:16:14.399 --> 01:16:17.520
Everything that is kind of going to set you free

01:16:17.520 --> 01:16:19.840
when you use a computer, as they were originally

01:16:19.840 --> 01:16:23.319
intended to do. Like Stallman said, right? So

01:16:23.319 --> 01:16:27.210
you're just like a fanboy. I'm a modern Richard

01:16:27.210 --> 01:16:30.850
Stallman. No, that's way too much. No, because

01:16:30.850 --> 01:16:35.310
he used the Internet, man. And you're using Google.

01:16:35.449 --> 01:16:38.170
I guess he doesn't agree to that. How would he

01:16:38.170 --> 01:16:41.050
feel? I mean, I have a YouTube channel. So, I

01:16:41.050 --> 01:16:44.949
mean, in and of itself, that is already absolutely

01:16:44.949 --> 01:16:50.729
proprietary, as Richard Stallman would say. All

01:16:50.729 --> 01:16:54.239
right, Josh, was fun. I really appreciate your

01:16:54.239 --> 01:16:57.039
time and helping me with all this. Any final

01:16:57.039 --> 01:17:00.100
words before we wrap it up? No, man, I'm excited

01:17:00.100 --> 01:17:03.979
to keep going with this. And I really, you can

01:17:03.979 --> 01:17:06.079
see I'm passionate about it. So you can see that

01:17:06.079 --> 01:17:08.460
it's something that I think a lot of people would,

01:17:08.560 --> 01:17:10.880
you can see what the potential of a computer

01:17:10.880 --> 01:17:13.439
is. And you start to like, you start to have

01:17:13.439 --> 01:17:15.560
like this thing that just unlocks in your mind.

01:17:15.560 --> 01:17:17.939
You're like. I've been using a computer wrong

01:17:17.939 --> 01:17:20.079
my entire life. That is correct. And there's

01:17:20.079 --> 01:17:23.199
that different way to use my computer, not just

01:17:23.199 --> 01:17:25.800
clicking around, navigating through apps and

01:17:25.800 --> 01:17:29.300
being slow. No, there's an efficient way of doing

01:17:29.300 --> 01:17:32.840
things, right? Yeah, man. And I mean, the limitations

01:17:32.840 --> 01:17:36.199
are almost non -existent when you start to see

01:17:36.199 --> 01:17:38.340
like what a computer can possibly be. And that's

01:17:38.340 --> 01:17:40.260
kind of what I guess I'm trying to convey with

01:17:40.260 --> 01:17:44.439
my channel. Yeah, great. All right, Josh. Appreciate

01:17:44.439 --> 01:17:47.619
it, man. i'll see you later then thanks for having

01:17:47.619 --> 01:17:49.159
me man take care bye