update unentangling, papersHEADmaster

1 files changed, 48 insertions, 33 deletions

diff --git a/2023/captions/emacsconf-2023-unentangling--unentangling-projects-and-repos--alexey-bochkarev--main.vtt b/2023/captions/emacsconf-2023-unentangling--unentangling-projects-and-repos--alexey-bochkarev--main.vtt
index a10fafef..1086b80b 100644
--- a/2023/captions/emacsconf-2023-unentangling--unentangling-projects-and-repos--alexey-bochkarev--main.vtt
+++ b/2023/captions/emacsconf-2023-unentangling--unentangling-projects-and-repos--alexey-bochkarev--main.vtt
@@ -1,8 +1,9 @@
-WEBVTT
+WEBVTT captioned by sachac
 
+NOTE Introduction
 
 00:00:01.220 --> 00:00:03.580
-Hello, I'm Alexey Bychkadov,
+Hello, I'm Alexey Bochkarev,
 
 00:00:03.740 --> 00:00:06.899
 and I'm talking about unentangling projects
@@ -46,8 +47,10 @@ So I prepare papers, presentations,
 00:00:41.260 --> 00:00:43.160
 memos, and so on and so forth.
 
+NOTE The problem
+
 00:00:44.120 --> 00:00:47.940
-And so The workflow problem I had is
+The workflow problem I had is
 
 00:00:49.160 --> 00:00:53.000
 sometimes all this does not really fit into a
@@ -59,19 +62,19 @@ concept of a single repository per project.
 So I might want to have,
 
 00:00:58.180 --> 00:01:01.160
-for example, a source code in 1 repository
+for example, a source code in one repository
 
 00:01:01.320 --> 00:01:03.480
 and then I would like to have a paper in
 
 00:01:03.480 --> 00:01:05.200
-another 1 and then I want to have a
+another one, and then I want to have a
 
 00:01:05.200 --> 00:01:08.620
 collection of notes somewhere unrelated to
 
 00:01:08.620 --> 00:01:12.500
-those 2. Emacs is pretty good at supporting
+those two. Emacs is pretty good at supporting
 
 00:01:12.500 --> 00:01:15.840
 your workflows and I figured I should share
@@ -80,19 +83,19 @@ your workflows and I figured I should share
 what I used and what works for me.
 
 00:01:20.560 --> 00:01:24.900
-So, from the technical perspective,
+From the technical perspective,
 
 00:01:26.479 --> 00:01:27.940
 things are pretty easy.
 
 00:01:27.940 --> 00:01:30.720
-So I use a collection of pretty standard
+I use a collection of pretty standard
 
 00:01:30.720 --> 00:01:33.240
-components of Emacs. So it's a projectile org
+components of Emacs. So it's projectile, org
 
 00:01:33.240 --> 00:01:35.360
-mode with this capture templates and other
+mode with this capture templates, and other
 
 00:01:35.360 --> 00:01:38.100
 things. Then I sustained a collection of
@@ -107,13 +110,13 @@ which is essentially it's a glorified
 collection of org mode files.
 
 00:01:46.100 --> 00:01:48.160
-Then I used directory local variables,
+Then I used directory-local variables,
 
 00:01:48.260 --> 00:01:51.140
-maybe a C text to jump through the source
+maybe a ctags to jump through the source
 
 00:01:51.140 --> 00:01:54.920
-code and very, very little LELisp glue to
+code and very, very little elisp glue to
 
 00:01:54.920 --> 00:01:57.620
 make this all work, but that's not really
@@ -124,6 +127,8 @@ rocket science. So that's the workflow I
 00:02:00.400 --> 00:02:02.180
 would like to talk about today.
 
+NOTE Jumping around
+
 00:02:04.860 --> 00:02:07.120
 So what I mean by all that,
 
@@ -134,7 +139,7 @@ it's pretty straightforward to make Emacs,
 to make it easy to jump around a single
 
 00:02:12.720 --> 00:02:14.980
-repository in Emacs. So if I,
+repository in Emacs. So if I...
 
 00:02:15.060 --> 00:02:16.640
 Now I have Doom Emacs,
@@ -167,7 +172,7 @@ project, right? So if I create a couple of
 custom shortcuts, so if I press a magic
 
 00:02:42.780 --> 00:02:45.280
-button, hyper-OP, don't worry about
+button, Hyper+o p... don't worry about
 
 00:02:45.280 --> 00:02:47.460
 hyper-key. So I want it to have a modifier
@@ -200,7 +205,7 @@ binding. Yeah, essentially an Emacs.
 And if I hit, for example,
 
 00:03:12.540 --> 00:03:15.200
-R, I end up in a readme file within this
+r, I end up in a README file within this
 
 00:03:15.200 --> 00:03:17.320
 specific repository I was sitting in,
@@ -209,11 +214,13 @@ specific repository I was sitting in,
 right? So if I want to document something
 
 00:03:19.000 --> 00:03:21.420
-real quick, I go to the readme file.
+real quick, I go to the README file.
 
 00:03:21.680 --> 00:03:25.280
 Then I could go to a change log file,
 
+NOTE Capturing
+
 00:03:25.280 --> 00:03:27.440
 right? So I have a list of changes and the
 
@@ -269,10 +276,10 @@ entries 1 by 1 and discuss what I haven't
 implemented last time.
 
 00:04:19.540 --> 00:04:22.580
-I could go to project specific,
+I could go to project-specific,
 
 00:04:24.100 --> 00:04:26.320
-sorry, to repo specific to-do list.
+sorry, to repo-specific to-do list.
 
 00:04:26.320 --> 00:04:29.020
 And I have list of to-dos that would leave
@@ -298,8 +305,10 @@ there are very many ways to jump through the
 00:04:45.400 --> 00:04:46.420
 source code conveniently.
 
+NOTE Ctags
+
 00:04:46.560 --> 00:04:49.960
-I ended up not using language servers I use a
+I ended up not using language servers. I use a
 
 00:04:49.960 --> 00:04:53.320
 special program called ctags and so the way
@@ -355,6 +364,8 @@ repository, it makes it really convenient to
 00:05:39.720 --> 00:05:41.780
 jump between all of those.
 
+NOTE Org Roam
+
 00:05:43.080 --> 00:05:46.980
 But I have a few problems here.
 
@@ -476,13 +487,13 @@ so I create a special folder within my
 org-roam storage. So it's a special folder
 
 00:07:38.240 --> 00:07:40.940
-outside of Henry Postories that got backed up
+outside of any repositories that got backed up
 
 00:07:40.940 --> 00:07:43.940
 to my hard drive with certain redundancy,
 
 00:07:44.080 --> 00:07:46.720
-but I don't really need like version control,
+but I don't really need version control,
 
 00:07:46.720 --> 00:07:48.280
 full blown version control for that.
@@ -499,8 +510,13 @@ here. So PKB stands for personal knowledge
 00:07:55.320 --> 00:07:58.020
 base, and I have a folder project notes in
 
-00:07:58.020 --> 00:08:01.520
-there, right? So, and How does it work?
+00:07:58.020 --> 00:07:59.339
+there, right?
+
+NOTE How does it work?
+
+00:07:59.340 --> 00:08:01.520
+How does it work?
 
 00:08:01.680 --> 00:08:04.940
 So I have a folder per project in there,
@@ -557,10 +573,10 @@ that would be open project.
 And then for example, org mode file,
 
 00:08:55.920 --> 00:08:58.260
-right? So this is my personal notes about the
+right? So this is my personal notes about
 
 00:08:58.260 --> 00:09:01.260
-maxconf, not specifically about this very
+EmacsConf, not specifically about this very
 
 00:09:01.260 --> 00:09:02.580
 talk, but I can have, you know,
@@ -578,7 +594,7 @@ And how does that happen?
 If we try to like look at the code,
 
 00:09:13.080 --> 00:09:14.660
-the e-list magic here,
+the elisp magic here,
 
 00:09:15.040 --> 00:09:17.560
 what is happening is it's just a couple of
@@ -634,11 +650,8 @@ And how do I define this variable?
 00:10:09.280 --> 00:10:12.500
 Is essentially there is this magical file in
 
-00:10:12.500 --> 00:10:14.160
-a folder called dear locals,
-
-00:10:14.440 --> 00:10:17.380
-elist. And I just put it there.
+00:10:12.500 --> 00:10:17.380
+a folder called .dir-locals.el. And I just put it there.
 
 00:10:17.440 --> 00:10:20.380
 And then whenever I go into that folder or
@@ -655,6 +668,8 @@ And that's pretty much it.
 00:10:26.280 --> 00:10:28.880
 That's how it works for me.
 
+NOTE Time tracking
+
 00:10:31.860 --> 00:10:34.620
 I guess 1 thing that I wanted to emphasize
 
@@ -713,7 +728,7 @@ there. And that's how it works.
 So again, what comes in handy,
 
 00:11:28.860 --> 00:11:31.500
-if I hit Control O, I just go back to the
+if I hit C-o, I just go back to the
 
 00:11:31.500 --> 00:11:34.240
 file I jumped in into and that's I jumped