The first question, @@ -31,16 +33,16 @@ and I don't think we really need it. Um, I think as it is, uh, Emacs
-with doc view needs new tool, which is something you need +with docview needs mutool, which is something you need
-to install from new PDF anyways. +to install from MuPDF anyways.
So, um, I think it is almost expected
-that you install new PDF from system package manager. +that you install MuPDF from system package manager.
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.
-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?
-the dynamic module some great, +the dynamic modules sound great,
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.
-Actually, I think 1 of the reasons is that. +Actually, I think one of the reasons is that
-Most of the time, I think people love Emacs +most of the time, I think people love Emacs
because they can do so much with Elisp. @@ -168,26 +172,28 @@ out of this super cool dynamic module feature.
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. +
-How how? How difficult is our PDF tools to install? +How difficult is PDF-tools to install?
The questioner is installing it
-using the built-in package manager +using the built-in package manager.
-looking at the Emacs reader installation instructions +Looking at the Emacs reader installation instructions,
-It doesn't necessarily cover +it doesn't necessarily cover
-how how to install that easily +how to install that easily.
-person is not using use package or straight and Okay. +Person is not using use-package or straight. Okay.
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,
-the reason I said PDF tools is difficult +the reason I said pdf-tools is difficult
-is PDF tools has a huge list of dependencies. +is pdf-tools has a huge list of dependencies.
-The only thing Emacs Vita depends +The only thing Emacs Reader depends
-on is new PDF, nothing else. There's a single dependency. +on is MuPDF, nothing else. There's a single dependency.
-PDF tools depends on a lot of things +pdf-tools depends on a lot of things
and they have their own server, @@ -229,7 +235,7 @@ which is packaged as a system package, which you don't really find everywhere.
-And there's like systems, the new Linux systems +And there's like systems, the GNU/Linux systems
where the package is very difficult to build @@ -244,22 +250,25 @@ So my goal was to sort of reduce the number of dependencies.
-And then right now it's very, it's sort of a key +And then right now it's sort of a key
to install Emacs Reader.
-Once we go to GNU Elpa, it's just +Once we go to GNU ELPA, it's just
-going to be Emacs package install, just that. +going to be Emacs package-install, just that.
-Right now you have to do package VC +Right now you have to do package :vc
-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
Emacs users. Everything just gets so easy @@ -267,8 +276,13 @@ Emacs users. Everything just gets so easy
for us. It's like an IDE for our
-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
memory usage between the three packages? @@ -286,25 +300,25 @@ purposes Valgrind. So Valgrind is a a set of suite of debugging tools.
-And one of the tools that it has is Massive. +And one of the tools that it has is Massif.
It's a heap analyzer, heap profiler.
-So Valgrind plus Massive, +So Valgrind plus Massif,
and then there's a KDE package
-called Massive Visualizer. +called Massif-Visualizer.
-So I first get the Massive output using Valgrind, +So I first get the Massif output using Valgrind,
-and then put that output into Massive Visualizer. +and then put that output into Massif Visualizer.
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
-which do something with Massive, +which do something with Massif,
but I don't think like they're maintained. @@ -333,6 +347,8 @@ Yeah. Gotcha. Cool. Awesome opportunity
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? +
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
-into a share library like SO. +into a share library like .so,
shared object, and then that shared object @@ -444,28 +460,30 @@ I'm basically loading that shared object,
and that shared object already has
+00:08:00.517 --> 00:08:03.879 the compiled dynamic module functions and so on.
+00:08:03.880 --> 00:08:07.079 But my blog will explain that better.
+00:08:07.080 --> 00:08:09.999 Gotcha. I thought that was pretty clear.
+00:08:10.000 --> 00:08:12.199 I'm looking forward to seeing that blog post
+00:08:12.200 --> 00:08:13.919 and understanding what I glossed over
+00:08:13.920 --> 00:08:15.879 trying to understand from that explanation.
+00:08:15.880 --> 00:08:17.279 That was great.
+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?
@@ -517,19 +535,21 @@ down in an efficient manner. Gotcha. Um. Comment or questioner says,
-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?
How can I associate ODT files to open with Emacs Reader?
+00:09:34.880 --> 00:09:37.939 You don't really need to do anything.
+00:09:37.940 --> 00:09:40.599 You should be just able to do find file,
-Control X, Control F, and open. +C-x C-f and open.
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,
-you should open Embug report. +you should open a bug report.
And I'll just mention @@ -579,6 +599,8 @@ Jump in and we can take questions
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? +
If a PDF file is open in Emacs Reader @@ -660,20 +682,25 @@ and feeding of the exact timing
if we have more of a continuous behind the curtains, so to speak.
-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
-with integrating synctex and AucTex? +with integrating SyncTeX and AucTeX?
-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.
-or PDF tools handles as well. Yeah, yeah. +00:12:01.460 --> 00:12:02.319 +Yeah, yeah.
-So, we have Synctex and Auctex planned. +So, we have SyncTeX and AucTeX planned.
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
-than PDF Tools does. +than pdf-tools does.
The only reason we haven't done it yet is because, again, @@ -699,13 +726,21 @@ and text selection and those features planned,
but it's anticipated. Yeah. All right. This next question
-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
-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: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
@@ -720,8 +755,13 @@ and I would be very happy to go deep into this.
I'm looking forward to catching that myself.
-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,
something like isearch and occur? @@ -742,7 +782,7 @@ So once we have text selection, once we're able to select the text,
-then we can have iSearch so that it can highlight the text. +then we can have isearch so that it can highlight the text.
Yeah. Um, all right. And then, um, there's, I'm just gonna, @@ -753,14 +793,16 @@ I'll read out this question
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). +
-Um, does the dynamic module, uh, prevent customization +Does the dynamic module prevent customization
that Emacs usually provides advice, hooks, et cetera,
-or does everything just kind of +or does everything just kind of...
No, if you have a dynamic module, @@ -793,13 +835,13 @@ from the dynamic module itself, that's a bit tricky because something like
-Calling a macro or doing macros and dynamic modules +calling a macro or doing macros and dynamic modules
-is not really that nice You have to pretty much manually +is not really that nice. You have to pretty much manually
-expand the macro yourself in the dynamic module +expand the macro yourself in the dynamic module,
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
-without touching the dynamic module. Got it +without touching the dynamic module. Got it.
So those are the questions that I see. @@ -864,6 +906,8 @@ So here comes one more question,
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? +
Following up on dynamic modules, @@ -937,10 +981,12 @@ that elisp shim is preferred. Yeah. Makes sense. Um.
-Uh, so question question here +Uh, so question here + +NOTE Q: Is searching on the roadmap? Or is it already available as a feature?
-is searching for the person is searching for a roadmap. +is searching... The person is searching for a roadmap.
Is that already available as a feature? @@ -996,6 +1042,8 @@ a next up type of feature as things,
as the current iteration stabilizes. +NOTE Q: Will there be occur-like searching? +
Question was, you know, occur like, how would you? @@ -1035,6 +1083,8 @@ into Emacs ecosystem as possible.
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? +
Do you have a timing expectation for ELPA? -- cgit v1.2.3