This is the Q&A for the talk at .
00:00 Q: Is there scope for integrating the C library into Emacs itself with muPDF becoming an optional dependency?
00:59 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?
03:02 Q: How is pdf-tools difficult to install? I install it using the built in package manager.
04:41 Q: What tool(s) did you use to measure the memory usage between the three packages?
05:49 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?
08:17 Q: Can one look at pdf metadata with emacs-reader? Can annotations be added? Does it understand forms? Can it handle encrypted pdfs?
09:28 Q: How can I associate ODT files to open with emacs-reader?
10:26 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?
11:49 Q: What are the challenges with integrating with SyncTeX and AucTeX? This would be great to see as pdf-tools handles this well.
12:35 Q: Will you be giving another talk on the architecture you went over? A deep-dive there would be awesome.
12:59 Q: Is there search functionality? Something like isearch and occur?
13:30 Q: Does dynamic module prevent customization that Elisp usually provide? (Advices, Hooks, etc).
15:31 Q: Do you usually create an Elisp shim from the FFI and then use them with Elisp code?
16:44 Q: Is searching on the roadmap? Or is it already available as a feature?
17:48 Q: Will there be occur-like searching?
18:28 Q: What is your timing expectation for it to appear on ELPA?
You can view this and other resources using free/libre software at https://emacsconf.org/2025/talks/reader .
This video is available under the terms of the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.