updatesHEADmaster

1 files changed, 122 insertions, 72 deletions

diff --git a/2025/captions/emacsconf-2025-reader--an-introduction-to-the-emacs-reader--divy--answers.vtt b/2025/captions/emacsconf-2025-reader--an-introduction-to-the-emacs-reader--divy--answers.vtt
index b9dae5b5..81066917 100644
--- a/2025/captions/emacsconf-2025-reader--an-introduction-to-the-emacs-reader--divy--answers.vtt
+++ b/2025/captions/emacsconf-2025-reader--an-introduction-to-the-emacs-reader--divy--answers.vtt
@@ -1,5 +1,7 @@
 WEBVTT
 
+NOTE Q: Is there scope for integrating the C library into Emacs itself with muPDF becoming an optional dependency?
+
 00:00:00.000 --> 00:00:01.479
 The first question,
 
@@ -31,16 +33,16 @@ and I don't think we really need it.
 Um, I think as it is, uh, Emacs
 
 00:00:33.040 --> 00:00:36.439
-with doc view needs new tool, which is something you need
+with docview needs mutool, which is something you need
 
 00:00:36.440 --> 00:00:38.919
-to install from new PDF anyways.
+to install from MuPDF anyways.
 
 00:00:38.920 --> 00:00:42.599
 So, um, I think it is almost expected
 
 00:00:42.600 --> 00:00:46.279
-that you install new PDF from system package manager.
+that you install MuPDF from system package manager.
 
 00:00:46.280 --> 00:00:49.119
 Um, and I think that as it is, is better
@@ -52,10 +54,12 @@ because we don't really need to have
 a whole PDF engine inside Emacs.
 
 00:00:53.440 --> 00:00:59.879
-Um, Next question also from the pad,
+Next question also from the pad,
+
+NOTE Q: The dynamic modules sound great, and it's amazing they're there since 2017. Why is it so slow to take off, do you think? Is there prior art with them?
 
 00:00:59.880 --> 00:01:01.759
-the dynamic module some great,
+the dynamic modules sound great,
 
 00:01:01.760 --> 00:01:06.639
 and it's amazing that they've been there since 2017.
@@ -73,10 +77,10 @@ Is there a prior art with them? Right?
 That's a good question.
 
 00:01:16.360 --> 00:01:22.119
-Actually, I think 1 of the reasons is that.
+Actually, I think one of the reasons is that
 
 00:01:22.120 --> 00:01:24.919
-Most of the time, I think people love Emacs
+most of the time, I think people love Emacs
 
 00:01:24.920 --> 00:01:27.519
 because they can do so much with Elisp.
@@ -168,26 +172,28 @@ out of this super cool dynamic module feature.
 00:02:57.800 --> 00:03:02.159
 Yeah. Cool I'll take I'll bring in the next question.
 
+NOTE Q: How is pdf-tools difficult to install? I install it using the built in package manager.
+
 00:03:02.160 --> 00:03:07.399
-How how? How difficult is our PDF tools to install?
+How difficult is PDF-tools to install?
 
 00:03:07.400 --> 00:03:10.439
 The questioner is installing it
 
 00:03:10.440 --> 00:03:12.519
-using the built-in package manager
+using the built-in package manager.
 
 00:03:12.520 --> 00:03:16.679
-looking at the Emacs reader installation instructions
+Looking at the Emacs reader installation instructions,
 
 00:03:16.680 --> 00:03:18.479
-It doesn't necessarily cover
+it doesn't necessarily cover
 
 00:03:18.480 --> 00:03:20.399
-how how to install that easily
+how to install that easily.
 
 00:03:20.400 --> 00:03:25.679
-person is not using use package or straight and Okay.
+Person is not using use-package or straight. Okay.
 
 00:03:25.680 --> 00:03:27.959
 Oh, and they say that you didn't
@@ -205,19 +211,19 @@ It's your choice. If you would like to say more.
 Yeah, I think just as a thing,
 
 00:03:40.520 --> 00:03:43.319
-the reason I said PDF tools is difficult
+the reason I said pdf-tools is difficult
 
 00:03:43.320 --> 00:03:45.839
-is PDF tools has a huge list of dependencies.
+is pdf-tools has a huge list of dependencies.
 
 00:03:45.840 --> 00:03:47.639
-The only thing Emacs Vita depends
+The only thing Emacs Reader depends
 
 00:03:47.640 --> 00:03:50.599
-on is new PDF, nothing else. There's a single dependency.
+on is MuPDF, nothing else. There's a single dependency.
 
 00:03:50.600 --> 00:03:54.479
-PDF tools depends on a lot of things
+pdf-tools depends on a lot of things
 
 00:03:54.480 --> 00:03:57.759
 and they have their own server,
@@ -229,7 +235,7 @@ which is packaged as a system package,
 which you don't really find everywhere.
 
 00:04:02.360 --> 00:04:05.039
-And there's like systems, the new Linux systems
+And there's like systems, the GNU/Linux systems
 
 00:04:05.040 --> 00:04:07.359
 where the package is very difficult to build
@@ -244,22 +250,25 @@ So my goal was to sort of reduce
 the number of dependencies.
 
 00:04:14.840 --> 00:04:19.559
-And then right now it's very, it's sort of a key
+And then right now it's sort of a key
 
 00:04:19.560 --> 00:04:21.119
 to install Emacs Reader.
 
 00:04:21.120 --> 00:04:23.319
-Once we go to GNU Elpa, it's just
+Once we go to GNU ELPA, it's just
 
 00:04:23.320 --> 00:04:25.999
-going to be Emacs package install, just that.
+going to be Emacs package-install, just that.
 
 00:04:26.000 --> 00:04:27.919
-Right now you have to do package VC
+Right now you have to do package :vc
 
-00:04:27.920 --> 00:04:32.359
-a bit. Boy, we get spoiled as
+00:04:27.920 --> 00:04:30.223
+a bit.
+
+00:04:30.224 --> 00:04:32.359
+Boy, we get spoiled as
 
 00:04:32.360 --> 00:04:35.359
 Emacs users. Everything just gets so easy
@@ -267,8 +276,13 @@ Emacs users. Everything just gets so easy
 00:04:35.360 --> 00:04:37.959
 for us. It's like an IDE for our
 
-00:04:37.960 --> 00:04:44.839
-whole machine. What tools did you use to measure the
+00:04:37.960 --> 00:04:41.200
+whole machine.
+
+NOTE Q: What tool(s) did you use to measure the memory usage between the three packages?
+
+00:04:41.201 --> 00:04:44.839
+What tools did you use to measure the
 
 00:04:44.840 --> 00:04:48.879
 memory usage between the three packages?
@@ -286,25 +300,25 @@ purposes Valgrind. So Valgrind is a a set of suite
 of debugging tools.
 
 00:05:01.560 --> 00:05:03.799
-And one of the tools that it has is Massive.
+And one of the tools that it has is Massif.
 
 00:05:03.800 --> 00:05:08.919
 It's a heap analyzer, heap profiler.
 
 00:05:08.920 --> 00:05:10.839
-So Valgrind plus Massive,
+So Valgrind plus Massif,
 
 00:05:10.840 --> 00:05:14.119
 and then there's a KDE package
 
 00:05:14.120 --> 00:05:15.759
-called Massive Visualizer.
+called Massif-Visualizer.
 
 00:05:15.760 --> 00:05:19.839
-So I first get the Massive output using Valgrind,
+So I first get the Massif output using Valgrind,
 
 00:05:19.840 --> 00:05:23.159
-and then put that output into Massive Visualizer.
+and then put that output into Massif Visualizer.
 
 00:05:23.160 --> 00:05:24.519
 That gives me the grasp.
@@ -322,7 +336,7 @@ I don't think so. I don't think so.
 There's, yeah, there's I think a few packages
 
 00:05:37.320 --> 00:05:38.879
-which do something with Massive,
+which do something with Massif,
 
 00:05:38.880 --> 00:05:42.159
 but I don't think like they're maintained.
@@ -333,6 +347,8 @@ Yeah. Gotcha. Cool. Awesome opportunity
 00:05:47.760 --> 00:05:49.399
 there for someone spunky.
 
+NOTE Q: How is the conversion between ELisp and the foreign language type system done? For example when interfacing with a C++ library that makes heavy use of C++ object system and templates?
+
 00:05:49.400 --> 00:05:55.399
 How is conversion between Elisp and foreign language types?
 
@@ -424,7 +440,7 @@ that is C++ or C or Rust.
 And then that is going to be compiled
 
 00:07:40.760 --> 00:07:43.279
-into a share library like SO.
+into a share library like .so,
 
 00:07:43.280 --> 00:07:46.439
 shared object, and then that shared object
@@ -444,28 +460,30 @@ I'm basically loading that shared object,
 00:07:58.440 --> 00:08:00.516
 and that shared object already has
 
-00:08:00.517 --> 00:08:03.891
+00:08:00.517 --> 00:08:03.879
 the compiled dynamic module functions and so on.
 
-00:08:03.892 --> 00:08:06.308
+00:08:03.880 --> 00:08:07.079
 But my blog will explain that better.
 
-00:08:06.309 --> 00:08:10.016
+00:08:07.080 --> 00:08:09.999
 Gotcha. I thought that was pretty clear.
 
-00:08:10.017 --> 00:08:12.016
+00:08:10.000 --> 00:08:12.199
 I'm looking forward to seeing that blog post
 
-00:08:12.017 --> 00:08:13.641
+00:08:12.200 --> 00:08:13.919
 and understanding what I glossed over
 
-00:08:13.642 --> 00:08:15.860
+00:08:13.920 --> 00:08:15.879
 trying to understand from that explanation.
 
-00:08:15.861 --> 00:08:18.420
+00:08:15.880 --> 00:08:17.279
 That was great.
 
-00:08:18.421 --> 00:08:22.879
+NOTE Q: Can one look at pdf metadata with emacs-reader? Can annotations be added? Does it understand forms? Can it handle encrypted pdfs?
+
+00:08:17.280 --> 00:08:22.840
 Can one look at PDF metadata with Emacs Reader?
 
 00:08:22.880 --> 00:08:26.199
@@ -517,19 +535,21 @@ down in an efficient manner. Gotcha. Um.
 Comment or questioner says,
 
 00:09:24.120 --> 00:09:28.799
-I installed Emacs Reader already as promised. Great job.
+I installed Emacs Reader already. It is as promised. Great job.
+
+NOTE Q: How can I associate ODT files to open with emacs-reader?
 
 00:09:28.800 --> 00:09:34.879
 How can I associate ODT files to open with Emacs Reader?
 
-00:09:34.880 --> 00:09:38.479
+00:09:34.880 --> 00:09:37.939
 You don't really need to do anything.
 
-00:09:38.480 --> 00:09:40.599
+00:09:37.940 --> 00:09:40.599
 You should be just able to do find file,
 
 00:09:40.600 --> 00:09:42.959
-Control X, Control F, and open.
+C-x C-f and open.
 
 00:09:42.960 --> 00:09:45.319
 And it should open with Emacs Reader
@@ -550,7 +570,7 @@ So you should just be able to do find file.
 If you're not able to do that,
 
 00:09:56.880 --> 00:09:58.199
-you should open Embug report.
+you should open a bug report.
 
 00:09:58.200 --> 00:10:00.759
 And I'll just mention
@@ -579,6 +599,8 @@ Jump in and we can take questions
 00:10:21.560 --> 00:10:25.999
 as long as Divya has steam for that.
 
+NOTE Q: If a pdf file is open in emacs-reader and I regenerate the pdf with some changes, does emacs-reader actually refresh the pdf on its own or do I have to reload the pdf?
+
 00:10:26.000 --> 00:10:30.439
 If a PDF file is open in Emacs Reader
 
@@ -660,20 +682,25 @@ and feeding of the exact timing
 00:11:41.320 --> 00:11:46.879
 if we have more of a continuous behind the curtains, so to speak.
 
-00:11:46.880 --> 00:11:50.959
-That makes a lot of sense to me. What are the challenges
+00:11:46.880 --> 00:11:49.752
+That makes a lot of sense to me.
+
+NOTE Q: What are the challenges with integrating with SyncTeX and AucTeX? This would be great to see as pdf-tools handles this well.
+
+00:11:49.753 --> 00:11:50.959
+What are the challenges
 
 00:11:50.960 --> 00:11:55.719
-with integrating synctex and AucTex?
+with integrating SyncTeX and AucTeX?
 
-00:11:55.720 --> 00:11:58.919
-This would be great to see as PDF handles as well,
+00:11:55.720 --> 00:12:01.459
+This would be great to see as pdf-tools handles this well.
 
-00:11:58.920 --> 00:12:02.319
-or PDF tools handles as well. Yeah, yeah.
+00:12:01.460 --> 00:12:02.319
+Yeah, yeah.
 
 00:12:02.320 --> 00:12:04.399
-So, we have Synctex and Auctex planned.
+So, we have SyncTeX and AucTeX planned.
 
 00:12:04.400 --> 00:12:06.839
 I don't really see any major obstacles
@@ -685,7 +712,7 @@ for doing that, to be very honest.
 I think we can do it in a much simpler way
 
 00:12:11.520 --> 00:12:12.479
-than PDF Tools does.
+than pdf-tools does.
 
 00:12:12.480 --> 00:12:17.479
 The only reason we haven't done it yet is because, again,
@@ -699,13 +726,21 @@ and text selection and those features planned,
 00:12:24.400 --> 00:12:32.919
 but it's anticipated. Yeah. All right. This next question
 
-00:12:32.920 --> 00:12:36.439
-I love your presentation. Will you be giving another talk
+00:12:32.920 --> 00:12:35.008
+I love your presentation.
+
+NOTE Q: Will you be giving another talk on the architecture you went over? A deep-dive there would be awesome.
+
+00:12:35.009 --> 00:12:36.439
+Will you be giving another talk
 
-00:12:36.440 --> 00:12:39.399
-on the architecture you went over a deep dive on?
+00:12:36.440 --> 00:12:38.193
+on the architecture you went over?
 
-00:12:39.400 --> 00:12:44.919
+00:12:38.194 --> 00:12:40.424
+A deep dive on that would be awesome.
+
+00:12:40.425 --> 00:12:44.919
 That would be awesome. I'm not sure if an EmacsConf talk
 
 00:12:44.920 --> 00:12:48.479
@@ -720,8 +755,13 @@ and I would be very happy to go deep into this.
 00:12:55.360 --> 00:12:58.119
 I'm looking forward to catching that myself.
 
-00:12:58.120 --> 00:13:02.639
-Thank you for the shout. Is there search functionality,
+00:12:58.120 --> 00:12:59.764
+Thank you for the shout.
+
+NOTE Q: Is there search functionality? Something like isearch and occur?
+
+00:12:59.765 --> 00:13:02.639
+Is there search functionality,
 
 00:13:02.640 --> 00:13:05.319
 something like isearch and occur?
@@ -742,7 +782,7 @@ So once we have text selection,
 once we're able to select the text,
 
 00:13:14.360 --> 00:13:17.679
-then we can have iSearch so that it can highlight the text.
+then we can have isearch so that it can highlight the text.
 
 00:13:17.680 --> 00:13:26.679
 Yeah. Um, all right. And then, um, there's, I'm just gonna,
@@ -753,14 +793,16 @@ I'll read out this question
 00:13:28.800 --> 00:13:30.639
 and then I have to do a little bookkeeping on the pad.
 
+NOTE Q: Does dynamic module prevent customization that Elisp usually provide? (Advices, Hooks, etc).
+
 00:13:30.640 --> 00:13:35.639
-Um, does the dynamic module, uh, prevent customization
+Does the dynamic module prevent customization
 
 00:13:35.640 --> 00:13:39.999
 that Emacs usually provides advice, hooks, et cetera,
 
 00:13:40.000 --> 00:13:44.359
-or does everything just kind of
+or does everything just kind of...
 
 00:13:44.360 --> 00:13:46.559
 No, if you have a dynamic module,
@@ -793,13 +835,13 @@ from the dynamic module itself,
 that's a bit tricky because something like
 
 00:14:09.720 --> 00:14:13.999
-Calling a macro or doing macros and dynamic modules
+calling a macro or doing macros and dynamic modules
 
 00:14:14.000 --> 00:14:18.119
-is not really that nice You have to pretty much manually
+is not really that nice. You have to pretty much manually
 
 00:14:18.120 --> 00:14:21.359
-expand the macro yourself in the dynamic module
+expand the macro yourself in the dynamic module,
 
 00:14:21.360 --> 00:14:23.839
 so if you want to do it from the dynamic module,
@@ -811,7 +853,7 @@ there's not much support right now,
 but you can do everything on the elisp side
 
 00:14:29.480 --> 00:14:33.399
-without touching the dynamic module. Got it
+without touching the dynamic module. Got it.
 
 00:14:33.400 --> 00:14:38.279
 So those are the questions that I see.
@@ -864,6 +906,8 @@ So here comes one more question,
 00:15:28.880 --> 00:15:31.959
 or actually a couple more questions coming in.
 
+NOTE Q: Do you usually create an Elisp shim from the FFI and then use them with Elisp code?
+
 00:15:31.960 --> 00:15:34.239
 Following up on dynamic modules,
 
@@ -937,10 +981,12 @@ that elisp shim is preferred.
 Yeah. Makes sense. Um.
 
 00:16:38.960 --> 00:16:44.639
-Uh, so question question here
+Uh, so question here
+
+NOTE Q: Is searching on the roadmap? Or is it already available as a feature?
 
 00:16:44.640 --> 00:16:47.439
-is searching for the person is searching for a roadmap.
+is searching... The person is searching for a roadmap.
 
 00:16:47.440 --> 00:16:49.279
 Is that already available as a feature?
@@ -996,6 +1042,8 @@ a next up type of feature as things,
 00:17:44.720 --> 00:17:48.159
 as the current iteration stabilizes.
 
+NOTE Q: Will there be occur-like searching?
+
 00:17:48.160 --> 00:17:52.239
 Question was, you know, occur like, how would you?
 
@@ -1035,6 +1083,8 @@ into Emacs ecosystem as possible.
 00:18:24.960 --> 00:18:28.159
 Okay. We'll see if we can get in this last question here.
 
+NOTE Q: What is your timing expectation for it to appear on ELPA?
+
 00:18:28.160 --> 00:18:30.319
 Do you have a timing expectation for ELPA?