From 436f702956aad327f9039ae842d7c524ec4cbf72 Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Tue, 24 Dec 2024 10:31:26 -0500 Subject: add YouTube URLs, Q&A video URLs --- ...colour-your-emacs-with-ease--ryota--answers.vtt | 493 +++++++++++---------- ...sp-written-in-scheme--ramin-honary--answers.vtt | 474 ++++++++++---------- ...-julia-and-emacs--gabriele-bozzola--answers.vtt | 222 +++++----- ...ocessing-for-emacs--colin-woodbury--answers.vtt | 2 +- 2024/info/blee-before.md | 4 +- 2024/info/casual-before.md | 4 +- 2024/info/color-after.md | 478 ++++++++++---------- 2024/info/color-before.md | 12 +- 2024/info/emacs30-before.md | 4 +- 2024/info/guile-before.md | 4 +- 2024/info/gypsum-after.md | 472 ++++++++++---------- 2024/info/gypsum-before.md | 22 +- 2024/info/hyperbole-before.md | 4 +- 2024/info/hyperdrive-before.md | 26 +- 2024/info/julia-after.md | 216 ++++----- 2024/info/julia-before.md | 18 +- 2024/info/learning-before.md | 4 +- 2024/info/links-before.md | 2 +- 2024/info/literate-before.md | 4 +- 2024/info/maxima-before.md | 2 +- 2024/info/mcclim-before.md | 4 +- 2024/info/org-update-before.md | 4 +- 2024/info/p-search-before.md | 4 +- 2024/info/papers-before.md | 4 +- 2024/info/pgmacs-before.md | 4 +- 2024/info/project-before.md | 4 +- 2024/info/regex-before.md | 2 +- 2024/info/rust-before.md | 4 +- 2024/info/sat-open-before.md | 2 +- 2024/info/sharing-before.md | 2 +- 2024/info/shell-before.md | 2 +- 2024/info/students-before.md | 4 +- 2024/info/sun-open-before.md | 2 +- 2024/info/theme-before.md | 4 +- 2024/info/transducers-after.md | 2 +- 2024/info/transducers-before.md | 8 +- 2024/info/water-before.md | 2 +- 2024/info/writing-before.md | 2 +- 2024/schedule-details.md | 2 +- 39 files changed, 1257 insertions(+), 1272 deletions(-) diff --git a/2024/captions/emacsconf-2024-color--colour-your-emacs-with-ease--ryota--answers.vtt b/2024/captions/emacsconf-2024-color--colour-your-emacs-with-ease--ryota--answers.vtt index b27008a3..3266d254 100644 --- a/2024/captions/emacsconf-2024-color--colour-your-emacs-with-ease--ryota--answers.vtt +++ b/2024/captions/emacsconf-2024-color--colour-your-emacs-with-ease--ryota--answers.vtt @@ -1,747 +1,748 @@ WEBVTT -00:00.169 --> 00:01.830 +00:00:00.000 --> 00:00:06.039 ... Org mode and kind of note taking. And that meant that it wasn't -00:02.810 --> 00:08.532 +00:00:06.040 --> 00:00:10.679 too difficult to get started with. But when I started more on -00:08.972 --> 00:15.474 +00:00:10.680 --> 00:00:14.959 the coding side, because I'm a software engineer, you know, -00:08.972 --> 00:15.474 +00:00:14.960 --> 00:00:20.679 on the day job. That kind of got me to think that the colors and -00:16.366 --> 00:24.790 +00:00:20.680 --> 00:00:26.479 how themes look, how Emacs looks, was affecting. And that's -00:25.331 --> 00:28.973 +00:00:26.480 --> 00:00:30.719 how it kind of came to picture. So I could have kind of gone -00:29.073 --> 00:36.917 +00:00:30.720 --> 00:00:34.919 into a little bit more coding side of things, but I didn't -00:29.073 --> 00:36.917 +00:00:34.920 --> 00:00:38.319 want to stress too much on the talk. So that's why I kind of -00:36.957 --> 00:41.919 +00:00:38.320 --> 00:00:43.439 stuck to a very small bits of Org Mode and Elisp. And yeah, I -00:42.319 --> 00:45.321 +00:00:43.440 --> 00:00:48.159 think that's how it came about. Yeah, but that's perfectly -00:46.536 --> 00:48.577 +00:00:48.160 --> 00:00:52.119 fine. That's one of the chief reasons why we have two tracks -00:49.437 --> 00:52.778 +00:00:52.120 --> 00:00:54.799 for Emacs content. We've had those for the last four years, I -00:52.798 --> 00:55.059 +00:00:54.800 --> 00:00:57.279 think. It's because we have a general track, which is more -00:55.119 --> 01:05.442 +00:00:57.280 --> 00:00:59.239 geared towards people who want a general... well, -00:55.119 --> 01:05.442 +00:00:59.240 --> 00:01:01.799 generally people who are highly interested into org mode -00:55.119 --> 01:05.442 +00:01:01.800 --> 00:01:03.999 and not necessarily into coding, but just to whet their -00:55.119 --> 01:05.442 +00:01:04.000 --> 00:01:08.399 appetite to what can be done. And on the DevTrack, we have, -01:06.082 --> 01:12.986 +00:01:08.400 --> 00:01:11.519 well, this year we have talked about Rust and about other -01:06.082 --> 01:12.986 +00:01:11.520 --> 00:01:13.559 fancy things that people can do with Emacs. But, you know, -01:13.006 --> 01:15.768 +00:01:13.560 --> 00:01:15.559 I'm also a software engineer, you know, we do this all the -01:13.006 --> 01:15.768 +00:01:15.560 --> 00:01:18.079 time. Sometimes it's just fine to just chat about colors and -01:15.808 --> 01:21.751 +00:01:18.080 --> 00:01:20.959 just the results of what we develop rather than how the -01:15.808 --> 01:21.751 +00:01:20.960 --> 00:01:24.839 sausage is made. So that's completely fine too. I'm not sure NOTE Why colour? -01:23.733 --> 01:32.618 +00:01:24.840 --> 00:01:28.879 if you mentioned it in your presentation, but why color, out -01:23.733 --> 01:32.618 +00:01:28.880 --> 00:01:31.479 of all the things you could be ricing on your setup, why were -01:23.733 --> 01:32.618 +00:01:31.480 --> 00:01:37.559 you so interested about colors? I think it was just that -01:34.870 --> 01:41.176 +00:01:37.560 --> 00:01:40.239 mainly that I had to do a lot of context switch between -01:34.870 --> 01:41.176 +00:01:40.240 --> 00:01:44.119 different languages. Elisp is not the one because Elisp is -01:41.576 --> 01:46.600 +00:01:44.120 --> 00:01:48.079 something that I would do for Emacs editing. But for day job, -01:47.061 --> 01:52.385 +00:01:48.080 --> 00:01:52.999 I had to use mainly Go as I work with Kubernetes quite a bit. So -01:52.525 --> 01:57.109 +00:01:53.000 --> 00:01:58.119 Go and also web languages like TypeScript, JavaScript, you -01:58.090 --> 02:13.642 +00:01:58.120 --> 00:02:01.519 know, those languages, where I felt that whenever I was -01:58.090 --> 02:13.642 +00:02:01.520 --> 00:02:05.359 switching context to a different language, I felt that it's -01:58.090 --> 02:13.642 +00:02:05.360 --> 00:02:08.839 kind of annoying to see all the different colors in -01:58.090 --> 02:13.642 +00:02:08.840 --> 00:02:11.999 languages like TypeScript, where, you know, VS Code way -01:58.090 --> 02:13.642 +00:02:12.000 --> 00:02:15.799 would be very full of colors. which I felt that, okay, like, -02:14.262 --> 02:23.569 +00:02:15.800 --> 00:02:18.759 why do I have to have that many different colors on let and -02:14.262 --> 02:23.569 +00:02:18.760 --> 00:02:23.759 constant or the keywords where it could be just a white text? -02:23.789 --> 02:25.170 +00:02:23.760 --> 00:02:27.679 It didn't have to be that colorful. So that was the bit, the -02:25.890 --> 02:30.373 +00:02:27.680 --> 00:02:31.399 most annoying bit when it came to context switching. And I -02:30.974 --> 02:35.197 +00:02:31.400 --> 00:02:34.759 felt that that just didn't happen in the Org Mode or writing -02:30.974 --> 02:35.197 +00:02:34.760 --> 00:02:40.799 in general. So I had to find a way to make it work, make more -02:36.017 --> 02:41.481 +00:02:40.800 --> 00:02:46.199 coding make my coding more kind of friendly to me and that's -02:42.173 --> 02:59.576 +00:02:46.200 --> 00:02:50.039 when I thought maybe just the colors are something that's -02:42.173 --> 02:59.576 +00:02:50.040 --> 00:02:54.039 bothering me and it actually was the case and that's how I got -02:42.173 --> 02:59.576 +00:02:54.040 --> 00:02:59.359 to more into the color kind of journey and got too much into it -02:42.173 --> 02:59.576 +00:02:59.360 --> 00:03:04.039 I guess. Right, and was it what eventually motivated you to NOTE What motivated you to learn Elisp and get into the Emacs core? -03:00.535 --> 03:05.778 +00:03:04.040 --> 00:03:06.999 learn Elisp and to get into the Emacs core? Because it's -03:05.798 --> 03:22.406 +00:03:07.000 --> 00:03:09.399 funny how you find plenty of people using Emacs in Org Mode -03:05.798 --> 03:22.406 +00:03:09.400 --> 00:03:11.399 and then they find something that they take particular -03:05.798 --> 03:22.406 +00:03:11.400 --> 00:03:15.039 issue with, for you it's the color, and then they just go all -03:05.798 --> 03:22.406 +00:03:15.040 --> 00:03:18.039 in trying to pull the rope as far as they can to try to -03:05.798 --> 03:22.406 +00:03:18.040 --> 00:03:21.359 understand as much as possible about what code is managing -03:05.798 --> 03:22.406 +00:03:21.360 --> 00:03:23.879 this part of the application. Like for you it was color, for -03:22.786 --> 03:25.047 +00:03:23.880 --> 00:03:27.999 me it was the org agenda, I desperately wanted to make Org -03:25.367 --> 03:30.692 +00:03:28.000 --> 00:03:32.439 Agenda do something that it wasn't able to do. And five -03:31.433 --> 03:36.318 +00:03:32.440 --> 00:03:35.199 years, well, actually, no, 10 years later, I find myself -03:31.433 --> 03:36.318 +00:03:35.200 --> 00:03:38.199 hosting Emacs Cons. So, you never know just how far you're -03:36.598 --> 03:39.201 +00:03:38.200 --> 00:03:40.399 going to be pulling this rope. So, it's really interesting -03:39.561 --> 03:42.224 +00:03:40.400 --> 00:03:44.679 for me that my call was this. But back to the question, is this -03:42.464 --> 03:48.150 +00:03:44.680 --> 00:03:47.759 what eventually motivated you to get into Elisp and the core -03:42.464 --> 03:48.150 +00:03:47.760 --> 00:03:53.439 of Emacs? I think that the original journey to move to Emacs -03:49.798 --> 04:02.250 +00:03:53.440 --> 00:03:56.959 was around keybindings that I got annoyed with with other -03:49.798 --> 04:02.250 +00:03:56.960 --> 00:03:59.839 solutions, not just, you know, not speaking of Emacs -03:49.798 --> 04:02.250 +00:03:59.840 --> 00:04:02.879 keybinding or anything, like anything in general. The main -04:02.870 --> 04:09.797 +00:04:02.880 --> 00:04:07.519 reason was that I used Dovrak keyboard layout, and that -04:02.870 --> 04:09.797 +00:04:07.520 --> 00:04:10.799 meant that all the C-c, C-v, C-p, whatever, It just is -04:10.257 --> 04:11.417 +00:04:10.800 --> 00:04:13.919 all over the place. So I had to find something that could work -04:11.577 --> 04:14.298 +00:04:13.920 --> 00:04:17.039 for me. And Emacs was a solution that allowed me to do -04:14.898 --> 04:17.499 +00:04:17.040 --> 00:04:20.479 anything. And that's the kind of the journey that it -04:18.019 --> 04:21.519 +00:04:20.480 --> 00:04:24.039 originally started. And from there, started tweaking org -04:21.599 --> 04:28.421 +00:04:24.040 --> 00:04:28.439 mode and writing experience to be tuned to my liking. Color -04:29.101 --> 04:33.682 +00:04:28.440 --> 00:04:32.559 was another thing that I thought, OK, maybe I could do it -04:29.101 --> 04:33.682 +00:04:32.560 --> 00:04:36.239 easily with org mode. And when I started to use more of the -04:34.262 --> 04:37.983 +00:04:36.240 --> 00:04:40.799 coding side of things on Emacs, I felt that, okay, that was -04:39.355 --> 04:41.697 +00:04:40.800 --> 00:04:45.159 something I needed to solve. So Elisp was always kind of -04:41.877 --> 04:48.022 +00:04:45.160 --> 00:04:48.439 just a toolkit that, you know, I knew that it was available. I -04:48.322 --> 04:52.105 +00:04:48.440 --> 00:04:52.199 knew that it would be something that I want to be able to use. -04:52.646 --> 04:58.090 +00:04:52.200 --> 00:04:57.159 So I think in a way color was a good segue to understand how I -04:52.646 --> 04:58.090 +00:04:57.160 --> 00:05:03.359 can kind of work out more of a complex logic with the editor -04:59.136 --> 05:07.220 +00:05:03.360 --> 00:05:06.359 without having to write JavaScript or things that I don't -04:59.136 --> 05:07.220 +00:05:06.360 --> 00:05:09.399 particularly like. So yeah, I think the journey around the -05:07.440 --> 05:13.583 +00:05:09.400 --> 00:05:11.879 functional languages, functional kind of programming was -05:07.440 --> 05:13.583 +00:05:11.880 --> 00:05:15.439 always something that I was keen about. And yeah, the whole -05:13.943 --> 05:16.644 +00:05:15.440 --> 00:05:18.479 journey kind of made sense for me. And then moving on to the -05:16.984 --> 05:21.246 +00:05:18.480 --> 00:05:21.999 color was just one way to get more involved in. So I can -05:21.406 --> 05:27.069 +00:05:22.000 --> 00:05:26.279 totally see that this journey kind of making to a little bit -05:21.406 --> 05:27.069 +00:05:26.280 --> 00:05:30.759 different angle But yeah, we shall see how that really turns -05:27.669 --> 05:30.972 +00:05:30.760 --> 00:05:33.799 out. But for now, I think I'm happy with the color setup. Now I -05:33.514 --> 05:35.095 +00:05:33.800 --> 00:05:37.599 can really focus on the coding. Well, that's all good. And -05:37.156 --> 05:44.162 +00:05:37.600 --> 00:05:40.839 I'm sure plenty of people listening to you now, you know, -05:37.156 --> 05:44.162 +00:05:40.840 --> 00:05:43.639 find this relatable, how they eventually got into -05:37.156 --> 05:44.162 +00:05:43.640 --> 00:05:46.879 programming. Like for you, you did say that you were a -05:44.222 --> 05:47.745 +00:05:46.880 --> 00:05:50.519 software engineer now. But I found plenty of people, -05:48.705 --> 05:53.469 +00:05:50.520 --> 00:05:54.679 especially doing workshops, that just started you know, -05:54.339 --> 06:01.267 +00:05:54.680 --> 00:05:57.639 their software engineering journey just with Emacs and -05:54.339 --> 06:01.267 +00:05:57.640 --> 00:05:59.239 they just realized they were doing something completely -05:54.339 --> 06:01.267 +00:05:59.240 --> 00:06:01.999 different, like I was studying humanities. But then you -06:01.787 --> 00:06:02.687 +00:06:02.000 --> 00:06:05.079 touch Emacs and you realize, yeah, this whole programming -06:01.787 --> 06:06.693 +00:06:05.080 --> 00:06:06.679 shtick is actually pretty damn cool. -00:06:07.280 --> 00:06:09.399 +00:06:06.680 --> 00:06:09.079 And then you find yourself again, -00:06:09.400 --> 00:06:11.039 +00:06:09.080 --> 00:06:10.999 five to 10 years later, becoming a software -00:06:11.040 --> 00:06:12.919 +00:06:11.000 --> 00:06:12.999 engineer. So yeah, that's all good. -00:06:12.920 --> 00:06:14.519 +00:06:13.000 --> 00:06:13.919 So we do have a couple of -00:06:14.520 --> 00:06:18.439 +00:06:13.920 --> 00:06:18.439 questions and I'd like to move into them so that I, I mean, -00:06:18.440 --> 00:06:22.439 +00:06:18.440 --> 00:06:22.399 people have questions and for me it's okay for me to chat with -00:06:22.440 --> 00:06:25.119 +00:06:22.400 --> 00:06:25.119 you but obviously it's better if people ask you the question -00:06:25.120 --> 00:06:27.679 +00:06:25.120 --> 00:06:27.639 themselves. And again, if you want to ask questions to Ryota -00:06:27.680 --> 00:06:31.079 +00:06:27.640 --> 00:06:31.039 directly, feel free to join us on BBB and whenever we're done -00:06:31.080 --> 00:06:33.519 +00:06:31.040 --> 00:06:33.519 with the questions on the pad, I'm more than happy -00:06:33.520 --> 00:06:34.444 +00:06:33.520 --> 00:06:35.319 to let you ask your questions live. NOTE Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps? -06:35.982 --> 00:06:37.902 +00:06:35.320 --> 00:06:37.799 All right, so starting with the first question, -00:06:37.903 --> 00:06:45.108 +00:06:37.800 --> 00:06:39.999 is there any intention to create a library -00:06:37.903 --> 06:45.108 +00:06:40.000 --> 00:06:42.559 for working with more experimental color spaces, pulling -06:35.982 --> 06:45.108 +00:06:42.560 --> 00:06:45.679 code out of Hasliberg for this purpose, perhaps? Although I -06:45.329 --> 06:46.049 +00:06:45.680 --> 00:06:50.479 do not know. Hasliberg, you might? Yeah, Hasliberg. And to -06:49.692 --> 06:50.892 +00:06:50.480 --> 00:06:55.119 answer the question, started the journey just for myself -06:52.859 --> 07:04.331 +00:06:55.120 --> 00:06:58.479 and I didn't think that it would be actually useful for other -06:52.859 --> 07:04.331 +00:06:58.480 --> 00:07:03.319 use cases and this conference talk just came about kind of -06:52.859 --> 07:04.331 +00:07:03.320 --> 00:07:08.079 out of sheer luck really. So the idea I think I can definitely -07:04.771 --> 07:14.501 +00:07:08.080 --> 00:07:12.199 work it out and I don't think there will be too, the original -07:04.771 --> 07:14.501 +00:07:12.200 --> 00:07:17.639 code that I started with was I had to use some color space and I -07:15.931 --> 07:21.595 +00:07:17.640 --> 00:07:22.479 started with sRGB and then went to HSL and then went to LCH. So -07:21.996 --> 07:24.678 +00:07:22.480 --> 00:07:25.479 I think there has been quite a bit that I learned from it. At -07:25.458 --> 07:33.885 +00:07:25.480 --> 00:07:29.999 the same time, I may be tempted to actually maybe perhaps -07:25.458 --> 07:33.885 +00:07:30.000 --> 00:07:34.159 contribute back to ct.el rather than creating my own. I -07:34.105 --> 07:36.227 +00:07:34.160 --> 00:07:36.279 think that would make more sense perhaps. -07:36.607 --> 00:07:39.548 +00:07:36.280 --> 00:07:39.479 But for my own kind of taste that I thought -00:07:39.549 --> 00:07:42.891 +00:07:39.480 --> 00:07:42.839 that it would be something I can work out in my theme, -00:07:42.892 --> 00:07:44.273 +00:07:42.840 --> 00:07:46.879 but I don't have any I think, you know, making a -07:45.813 --> 07:53.975 +00:07:46.880 --> 00:07:49.999 library is definitely something that I can think about, but -07:45.813 --> 07:53.975 +00:07:50.000 --> 00:07:53.679 perhaps maybe making it too many packages isn't exactly -07:45.813 --> 07:53.975 +00:07:53.680 --> 00:07:57.319 what I want. But for my own use case, I think I just wanted to -07:55.175 --> 08:06.317 +00:07:57.320 --> 00:07:59.919 have something that just didn't have any external -07:55.175 --> 08:06.317 +00:07:59.920 --> 00:08:04.119 dependency so that I can use the vanilla Emacs with my -07:55.175 --> 08:06.317 +00:08:04.120 --> 00:08:09.639 colors. I think that's how it started, but I'm definitely up -08:06.757 --> 08:11.558 +00:08:09.640 --> 00:08:13.719 for it if there is interest about it. Yeah, well, thank you -08:12.622 --> 00:08:13.615 +00:08:13.720 --> 00:08:15.279 for this. It's always good to contribute. -00:08:16.040 --> 00:08:16.399 +00:08:15.280 --> 00:08:16.399 I'm tempted to say -00:08:16.400 --> 00:08:18.679 +00:08:16.400 --> 00:08:18.279 that's how they get you. You know, you do something really -00:08:18.680 --> 00:08:24.799 +00:08:18.280 --> 00:08:23.639 cool and you share it with people and they have the, you know, -00:08:24.800 --> 00:08:27.080 +00:08:23.640 --> 00:08:27.239 they just ask you, oh, do you have your code online? And you -08:27.166 --> 08:28.667 +00:08:27.240 --> 00:08:29.399 realize, no, I haven't pushed it. And then they start -08:28.707 --> 08:30.107 +00:08:29.400 --> 00:08:32.359 pressing you on. well, you need to do this, this is amazing -08:30.287 --> 08:33.349 +00:08:32.360 --> 00:08:35.879 and you need to share it. You know, I had plenty of people ask -08:33.849 --> 08:41.735 +00:08:35.880 --> 00:08:40.519 me to share my dot files when I was tackling the org agenda -08:33.849 --> 08:41.735 +00:08:40.520 --> 00:08:44.039 issue that I mentioned earlier. And yeah, eventually when -08:42.575 --> 08:54.243 +00:08:44.040 --> 00:08:47.479 you get to publishing your stuff, you also feel great -08:42.575 --> 08:54.243 +00:08:47.480 --> 00:08:50.279 because you're putting a little bit of your intelligence -08:42.575 --> 08:54.243 +00:08:50.280 --> 00:08:53.679 into the world and it can be the start of the journey for -08:42.575 --> 08:54.243 +00:08:53.680 --> 00:08:56.239 someone else. You know, maybe someone will find your -08:54.283 --> 08:59.867 +00:08:56.240 --> 00:08:58.679 library at some point and realize, yeah, I wanted to do -08:54.283 --> 08:59.867 +00:08:58.680 --> 00:09:01.239 something slightly differently. and then they either -09:00.387 --> 09:10.793 +00:09:01.240 --> 00:09:04.439 contribute to a library or they make their own but it's a -09:00.387 --> 09:10.793 +00:09:04.440 --> 00:09:07.359 complete journey that starts with just people taking the -09:00.387 --> 09:10.793 +00:09:07.360 --> 00:09:12.039 time to publish the content of the brain basically. Yeah, -09:11.894 --> 09:13.354 +00:09:12.040 --> 00:09:15.519 that's the power of open source now. It's just how we really -09:13.654 --> 09:21.276 +00:09:15.520 --> 00:09:19.119 appreciate the open source culture being cultivated -09:13.654 --> 09:21.276 +00:09:19.120 --> 00:09:23.159 throughout so many years. And yeah, this is something that -09:21.736 --> 09:24.337 +00:09:23.160 --> 00:09:26.999 I'm definitely keen about. So yeah, open for suggestions. -09:26.618 --> 09:29.298 +00:09:27.000 --> 00:09:30.079 And exactly, that's how I started with the journey. And -00:09:29.760 --> 00:09:33.559 +00:09:30.080 --> 00:09:33.519 yeah, while this is very experimental and very personal, -00:09:33.560 --> 00:09:38.239 +00:09:33.520 --> 00:09:38.199 yeah, I'm not, you know, tied down to one particular way -00:09:38.240 --> 00:09:41.679 +00:09:38.200 --> 00:09:41.399 only. So yeah we'll be open to suggestions like this one -00:09:41.680 --> 00:09:44.839 +00:09:41.400 --> 00:09:44.719 which I would definitely think about. Yeah that's amazing -00:09:44.840 --> 00:09:46.879 +00:09:44.720 --> 00:09:46.999 and just to be clear you know this is not a there's no -00:09:46.880 --> 00:09:47.840 +00:09:47.000 --> 00:09:50.639 incentive one. I'm not pushing you to publish your library. -09:51.070 --> 09:57.595 +00:09:50.640 --> 00:09:53.799 You know it was very personal for you and at the end if you -09:51.070 --> 09:57.595 +00:09:53.800 --> 00:09:56.199 believe it might be useful for others it's a nice thing to -09:51.070 --> 09:57.595 +00:09:56.200 --> 00:09:58.799 eventually think about publishing it. But just the fact -09:58.056 --> 10:00.117 +00:09:58.800 --> 00:10:01.439 that you showed up at EmacsConf... Sorry, I'm -10:01.278 --> 00:10:02.698 +00:10:01.440 --> 00:10:02.639 starting to lose my voice on the morning -00:10:02.699 --> 00:10:03.280 +00:10:02.640 --> 00:10:03.839 of the first day. That's -10:03.520 --> 00:10:08.559 +00:10:03.840 --> 00:10:07.639 not boding well for the two next days. I mean, just one day. -00:10:08.560 --> 00:10:10.079 +00:10:07.640 --> 00:10:09.159 But just the -00:10:10.080 --> 00:10:13.279 +00:10:09.160 --> 00:10:13.199 fact that you're showing up at EmacsConf and sharing about -00:10:13.280 --> 00:10:17.119 +00:10:13.200 --> 00:10:17.039 all of this, the process, how you got to it eventually, it's -00:10:17.120 --> 00:10:19.439 +00:10:17.040 --> 00:10:19.639 also a part of sharing. And I think it's also amazing in its -00:10:19.440 --> 00:10:26.039 +00:10:19.640 --> 00:10:26.039 own way. Absolutely. Okay, I'm going to try to read the next -00:10:26.040 --> 00:10:31.719 +00:10:26.040 --> 00:10:31.639 question and then try to cough a little bit. So can we have... -00:10:31.720 --> 00:10:36.919 +00:10:31.640 --> 00:10:36.759 Oh, sorry, Bala. Sorry. I was the one who asked the question. -00:10:36.920 --> 00:10:40.120 +00:10:36.760 --> 00:10:40.279 I thought I could ask it live here rather than... Thank you. -10:40.188 --> 10:41.368 +00:10:40.280 --> 00:10:46.039 I'll go cough a little bit. So here I am. Thanks, Ryota, for -10:45.050 --> 10:47.190 +00:10:46.040 --> 00:10:50.519 the nice talk. This is great. I loved it. Your attention to -10:49.531 --> 00:10:50.140 +00:10:50.520 --> 00:10:51.519 detail was awesome. NOTE Q: Can we have a dark as well as light theme variations made from your theme? -00:10:51.880 --> 00:10:55.079 +00:10:51.520 --> 00:10:54.959 So I was just looking at the code and I was -00:10:55.080 --> 00:10:58.839 +00:10:54.960 --> 00:10:58.759 wondering, do you have a dark and a light theme variation -00:10:58.840 --> 00:11:02.479 +00:10:58.760 --> 00:11:02.599 which can be made from your theme? Or do you have to customize -00:11:02.480 --> 00:11:05.519 +00:11:02.600 --> 00:11:06.199 it every time? That was my question. And thanks for that. -00:11:05.520 --> 00:11:07.640 +00:11:06.200 --> 00:11:09.679 Thank you very much. I appreciate your feedback and -00:11:10.240 --> 00:11:15.079 +00:11:09.680 --> 00:11:15.039 questions. So to answer the question, the short answer is -00:11:15.080 --> 00:11:18.639 +00:11:15.040 --> 00:11:18.439 that I do have both dark and light themes with some sorts of -00:11:18.640 --> 00:11:22.199 +00:11:18.440 --> 00:11:22.199 standard colors that I personally liked. And there were a -00:11:22.200 --> 00:11:26.719 +00:11:22.200 --> 00:11:26.679 few things that I showed in the demo. where I showed, I think, -00:11:26.720 --> 00:11:30.039 +00:11:26.680 --> 00:11:29.999 three different dark theme colors. So light theme is -00:11:30.040 --> 00:11:31.440 +00:11:30.000 --> 00:11:31.559 definitely something that I can do. -00:11:31.800 --> 00:11:33.879 +00:11:31.560 --> 00:11:33.759 And the idea around Hasliberg theme -00:11:33.880 --> 00:11:36.359 +00:11:33.760 --> 00:11:36.279 and just my theming in general was that -00:11:36.360 --> 00:11:39.679 +00:11:36.280 --> 00:11:39.599 when I feel like I want to work in dark theme and when I want to -00:11:39.680 --> 00:11:42.440 +00:11:39.600 --> 00:11:42.159 work in the standard way, I would just use the standard color. -00:11:42.480 --> 00:11:44.959 +00:11:42.160 --> 00:11:44.919 But when I feel like maybe it's just so cold that I want -00:11:44.960 --> 00:11:49.399 +00:11:44.920 --> 00:11:48.519 to have a bit of a warm colors near me, I would use the orange -00:11:49.400 --> 00:11:52.359 +00:11:48.520 --> 00:11:52.279 theme, without changing too much of the kind of general -00:11:52.360 --> 00:11:55.679 +00:11:52.280 --> 00:11:55.639 feeling and experience. So that can be said for the light -00:11:55.680 --> 00:11:58.959 +00:11:55.640 --> 00:11:58.959 theme as well. So there is something and the kind of -00:11:58.960 --> 00:12:04.919 +00:11:58.960 --> 00:12:04.839 customization isn't that difficult to extend. So I do have -00:12:04.920 --> 00:12:09.079 +00:12:04.840 --> 00:12:09.359 both dark and light, but primarily I'm just looking at the -00:12:09.080 --> 00:12:10.239 +00:12:09.360 --> 00:12:12.839 dark theme as my main driver. But yeah, they are both -00:12:10.240 --> 00:12:13.240 +00:12:12.840 --> 00:12:18.239 available. Great. Thank you so much. I will definitely try -00:12:18.208 --> 12:18.865 +00:12:18.240 --> 00:12:21.719 your theme out. I'm definitely on the lookout for a nice, -12:19.205 --> 12:22.426 +00:12:21.720 --> 00:12:26.119 friendly theme. Thank you very much. As I said, this is a -12:25.388 --> 12:27.429 +00:12:26.120 --> 00:12:31.279 personal theme. I'm not sure if it really fits everyone's -12:29.089 --> 12:42.816 +00:12:31.280 --> 00:12:37.159 need, but it is one inspiration that I hope that can lead to -12:29.089 --> 12:42.816 +00:12:37.160 --> 00:12:40.639 another nice theming that could work for someone -12:29.089 --> 12:42.816 +00:12:40.640 --> 00:12:44.199 specifically for some use cases. I don't have to solve -12:42.996 --> 12:44.977 +00:12:44.200 --> 00:12:48.719 everyone's problem. Yeah, and I mean, it was sufficient to -12:46.553 --> 12:49.715 +00:12:48.720 --> 00:12:50.719 be inspirational to people. I mean, just Bala just -12:49.755 --> 12:58.619 +00:12:50.720 --> 00:12:53.759 mentioned it right now, but I'm sure plenty of people who -12:49.755 --> 12:58.619 +00:12:53.760 --> 00:12:55.999 watched live, but also people will be watching in the -12:49.755 --> 12:58.619 +00:12:56.000 --> 00:12:58.599 future, will have the interest to speak by what you've done. -12:58.699 --> 13:00.040 +00:12:58.600 --> 00:13:05.079 So thank you again so much for this. Yep. All right, well, I -13:04.102 --> 13:06.603 +00:13:05.080 --> 00:13:09.719 don't see any further questions. So I suggest we move -13:07.083 --> 13:10.525 +00:13:09.720 --> 00:13:14.279 towards closure. Ryota, do you have any last words? No, I -13:13.775 --> 13:14.175 +00:13:14.280 --> 00:13:17.079 don't. So yeah, thank you very much for attending. And it was -13:16.577 --> 13:18.979 +00:13:17.080 --> 00:13:20.519 great fun putting this together. And I really didn't think -13:19.299 --> 13:27.545 +00:13:20.520 --> 00:13:24.759 that I would be talking about my personal colors and -13:19.299 --> 13:27.545 +00:13:24.760 --> 00:13:27.759 personal favorites, like orange being my favorite color. -13:27.845 --> 13:31.228 +00:13:27.760 --> 00:13:30.119 This wouldn't be something that I would say out in any -13:27.845 --> 13:31.228 +00:13:30.120 --> 00:13:34.159 conference, to be honest. But it just came out to be. And -13:33.890 --> 13:35.491 +00:13:34.160 --> 00:13:37.479 happy that I had a chance. So thank you very much for giving me -13:35.651 --> 13:39.154 +00:13:37.480 --> 00:13:41.439 the opportunity to talk. in this amazing conference and -13:39.574 --> 13:52.473 +00:13:41.440 --> 00:13:44.319 yeah I can't just wait to check out other talks which you know -13:39.574 --> 13:52.473 +00:13:44.320 --> 00:13:46.919 I know that there isn't you know other talks that are -13:39.574 --> 13:52.473 +00:13:46.920 --> 00:13:50.199 happening right now I was actually wanted to to join them and -13:39.574 --> 13:52.473 +00:13:50.200 --> 00:13:52.759 check check that out so I will probably do that right now. -13:53.419 --> 13:53.899 +00:13:52.760 --> 00:13:56.839 Well, sure. Well, I won't hold you any longer then. Thank -13:56.401 --> 13:56.741 +00:13:56.840 --> 00:13:59.759 you. For me, it was just amazing to, you know, generally when -13:57.682 --> 14:03.285 +00:13:59.760 --> 00:14:01.639 you ask someone what their favorite color, you know, they -13:57.682 --> 14:03.285 +00:14:01.640 --> 00:14:04.399 just tell you orange or blue or whatever. They don't go then -14:03.586 --> 14:10.690 +00:14:04.400 --> 00:14:07.039 to chat about 20 minutes about their favorite color and how -14:03.586 --> 14:10.690 +00:14:07.040 --> 00:14:10.079 they tuned their entire editor to work exactly around their -14:03.586 --> 14:10.690 +00:14:10.080 --> 00:14:14.759 favorite colors. So it was inspiring. And I also want to try -14:12.912 --> 14:21.057 +00:14:14.760 --> 00:14:17.999 it out, frankly, because my theme has been utterly bad for -14:12.912 --> 14:21.057 +00:14:18.000 --> 00:14:20.639 the last five years and I need some change into my life. All -14:21.497 --> 14:21.677 +00:14:20.640 --> 00:14:24.319 right. Thank you so much for your time. Thank you very much, -14:23.629 --> 14:24.654 +00:14:24.320 --> 00:14:30.640 everyone. Cheers. Bye-bye. + diff --git a/2024/captions/emacsconf-2024-gypsum--gypsum-my-clone-of-emacs-and-elisp-written-in-scheme--ramin-honary--answers.vtt b/2024/captions/emacsconf-2024-gypsum--gypsum-my-clone-of-emacs-and-elisp-written-in-scheme--ramin-honary--answers.vtt index 0142a879..7c2708d9 100644 --- a/2024/captions/emacsconf-2024-gypsum--gypsum-my-clone-of-emacs-and-elisp-written-in-scheme--ramin-honary--answers.vtt +++ b/2024/captions/emacsconf-2024-gypsum--gypsum-my-clone-of-emacs-and-elisp-written-in-scheme--ramin-honary--answers.vtt @@ -1,725 +1,725 @@ WEBVTT -00:00.069 --> 00:01.850 -Troy Hinckley's project that I'm talking about. I was going +00:00:00.000 --> 00:00:02.999 +...Troy Hinckley's project that I'm talking about. I was going -00:02.350 --> 00:22.139 +00:00:03.000 --> 00:00:08.799 to mention this in my presentation, but it's possible, -00:02.350 --> 00:22.139 +00:00:08.800 --> 00:00:16.359 theoretically, that Troy Hinckley, his project could be -00:02.350 --> 00:22.139 +00:00:16.360 --> 00:00:18.559 used as a scheme of limitation that actually runs my own -00:02.350 --> 00:22.139 +00:00:18.560 --> 00:00:23.759 version of Emacs. And although, you know, This is -00:25.478 --> 00:29.380 +00:00:23.760 --> 00:00:30.719 completely theoretical, and I don't know how difficult -00:25.478 --> 00:29.380 +00:00:30.720 --> 00:00:34.079 that would be. But if Troy Hinckley implemented enough of -00:30.781 --> 00:47.029 +00:00:34.080 --> 00:00:39.879 the R7-RS standard in Rust, it would theoretically be -00:30.781 --> 00:47.029 +00:00:39.880 --> 00:00:46.719 possible to run the Gypsum editor in Troy Hinckley's own -00:30.781 --> 00:47.029 +00:00:46.720 --> 00:00:50.239 editor. I thought that was kind of interesting, and I -00:48.270 --> 00:53.833 +00:00:50.240 --> 00:00:59.119 thought it was worth mentioning, at least in the questions -00:48.270 --> 00:53.833 +00:00:59.120 --> 00:01:12.159 and answers. -01:12.179 --> 01:14.080 +00:01:12.160 --> 00:01:16.199 I also mentioned this in the presentation. I wanted to see -01:14.940 --> 01:22.364 +00:01:16.200 --> 00:01:20.119 Robin Templeton's project presentation, but -01:14.940 --> 01:22.364 +00:01:20.120 --> 00:01:22.399 unfortunately it's going to be at like four in the morning -01:14.940 --> 01:22.364 +00:01:22.400 --> 00:01:26.239 for me. So I'm going to try and watch that tomorrow, but -01:22.984 --> 01:31.428 +00:01:26.240 --> 00:01:29.559 that's also going to be a very interesting project to keep an -01:22.984 --> 01:31.428 +00:01:29.560 --> 00:01:34.039 eye on if you're interested in Scheme. That's the project -01:33.149 --> 01:38.051 +00:01:34.040 --> 00:01:37.519 where you've got the Guylain interpreter running inside of -01:33.149 --> 01:38.051 +00:01:37.520 --> 00:02:04.679 the Emacs process. It's dynamically linked as a library. -02:04.699 --> 02:06.748 +00:02:04.680 --> 00:02:08.759 I'm ready for questions from anybody. You can ask or you can -02:07.431 --> 02:09.079 +00:02:08.760 --> 00:02:32.079 type. It's up to you. -02:32.319 --> 02:34.521 +00:02:32.080 --> 00:02:37.319 Okay, let me check the etherpad. -02:37.304 --> 02:38.245 +00:02:37.320 --> 00:02:41.159 Let's see here. -02:41.208 --> 02:42.830 +00:02:41.160 --> 00:02:42.719 I'm not sure if I'm doing that right. -02:46.373 --> 02:47.554 +00:02:42.720 --> 00:02:54.199 Let me check one more time. Oh, there it goes. -02:54.221 --> 02:55.702 +00:02:54.200 --> 00:03:00.079 Let's see, so this is... -03:00.151 --> 03:02.072 +00:03:00.080 --> 00:03:02.239 I didn't know about that first bit of history. Oh, I've heard -03:02.332 --> 00:03:09.369 +00:03:02.240 --> 00:03:06.119 RMS say that Scheme Guile is just a nicer Lisp, but I didn't -03:02.332 --> 03:09.776 +00:03:06.120 --> 00:03:09.079 know there were concrete talks attempts to use Guile for -03:02.332 --> 03:09.776 +00:03:09.080 --> 00:03:14.319 Emacs that early. Let's see, that was from janneke. NOTE Q: I'm curious to know how the hell guile-emacs deals with all of the dynamically scoped modules out there. Is there any effort to automatically modularize and namespace stuff? -00:03:09.370 --> 00:03:19.241 +00:03:14.320 --> 00:03:17.439 I'm curious to know how the hell Guile Emacs deals with all the -03:14.318 --> 03:19.241 +00:03:17.440 --> 00:03:21.359 dynamically scoped modules out there. Is there any effort -03:20.181 --> 03:24.943 +00:03:21.360 --> 00:03:29.759 to automatically modularize and name? Let's see. -03:30.523 --> 03:35.806 +00:03:29.760 --> 00:03:40.919 That might be a better question for Robin Templeton. In my -03:36.727 --> 03:46.573 +00:03:40.920 --> 00:03:44.639 own project, -03:36.727 --> 03:46.573 +00:03:44.640 --> 00:03:49.399 there's no module system for Emacs Lisp. There is a module -03:46.693 --> 03:48.234 +00:03:49.400 --> 00:03:55.559 system for Scheme. And the Emacs Lisp interpreter runs in -03:49.695 --> 03:55.158 +00:03:55.560 --> 00:04:01.599 its own environment. the require system or whatever module -03:57.068 --> 04:11.736 +00:04:01.600 --> 00:04:06.359 system that Emacs has, once it's implemented, all of that -03:57.068 --> 04:11.736 +00:04:06.360 --> 00:04:09.759 would just happen inside of the Emacs Lisp environment, -03:57.068 --> 04:11.736 +00:04:09.760 --> 00:04:12.399 which is inside of the Scheme environment. And -04:12.437 --> 04:15.898 +00:04:12.400 --> 00:04:21.479 environments are objects in Scheme. -04:21.522 --> 04:24.103 +00:04:21.480 --> 00:04:26.399 I think a more difficult question is how to handle -04:26.420 --> 04:31.942 +00:04:26.400 --> 00:04:33.279 threading, and Scheme has very good threading built in, in -04:26.420 --> 04:31.942 +00:04:33.280 --> 00:04:34.839 Serphe-18[??]. -04:34.283 --> 04:48.028 +00:04:34.840 --> 00:04:43.399 But I don't think it will be easy to write Emacs Lisp form -04:34.283 --> 04:48.028 +00:04:43.400 --> 00:04:48.479 bindings to the Scheme multi-threading implementation. -04:48.548 --> 04:50.749 +00:04:48.480 --> 00:04:52.279 Emacs Lisp was just not cut out for that kind of thing. So I -04:51.710 --> 04:59.894 +00:04:52.280 --> 00:04:56.559 think each Emacs Lisp, you could, I suppose, have multiple -04:51.710 --> 04:59.894 +00:04:56.560 --> 00:05:00.039 threads each running their own Emacs Lisp environment. -05:01.375 --> 05:02.956 +00:05:00.040 --> 00:05:04.999 Scheme would make that very simple to do. -05:06.018 --> 05:16.744 +00:05:05.000 --> 00:05:08.759 And then there'd just be a question of how you would get those -05:06.018 --> 05:16.744 +00:05:08.760 --> 00:05:11.679 different interpreters to communicate with each other, -05:06.018 --> 05:16.744 +00:05:11.680 --> 00:05:16.279 perhaps using the same protocol that's used by the Emacs -05:06.018 --> 05:16.744 +00:05:16.280 --> 00:05:23.639 server. But I haven't thought that far ahead yet. NOTE Q: Would it be possible to support a GUI toolkit other than GTK? -05:23.646 --> 05:28.709 +00:05:23.640 --> 00:05:26.839 Would it be possible to support a GUI toolkit other than the -05:23.646 --> 05:28.709 +00:05:26.840 --> 00:05:31.319 GTK? Like, how is it still supports Lucid? Yes, this is -05:31.291 --> 05:33.232 +00:05:31.320 --> 00:05:36.999 absolutely a goal of the project. I'm trying to keep the back -05:33.873 --> 05:38.416 +00:05:37.000 --> 00:05:41.599 end separate as possible. The scheme has what you call -05:39.817 --> 05:42.478 +00:05:41.600 --> 00:05:45.239 parameters. And these are like global variables that are -05:43.199 --> 05:46.221 +00:05:45.240 --> 00:05:50.519 still somewhat thread safe. And every call to the GUI goes -05:47.484 --> 05:51.225 +00:05:50.520 --> 00:05:58.199 through a parameter. So the Emacs, the interpreter and the -05:52.125 --> 05:59.367 +00:05:58.200 --> 00:06:01.679 editor logic is all in one module. And then that module calls -05:59.987 --> 06:04.309 +00:06:01.680 --> 00:06:06.319 out into a separate GUI module. And then you can implement -06:04.989 --> 06:07.690 +00:06:06.320 --> 00:06:11.599 different GUI modules. So you could have one for GTK3, one -06:08.430 --> 06:13.171 +00:06:11.600 --> 00:06:16.879 for GTK4, if you want to write the extern C bindings around Qt -06:13.843 --> 06:20.725 +00:06:16.880 --> 00:06:21.199 or full tick, that would certainly be possible as well. It -06:21.185 --> 06:32.168 +00:06:21.200 --> 00:06:25.919 would be nice maybe to have an SDL implementation based -06:21.185 --> 06:32.168 +00:06:25.920 --> 00:06:30.999 maybe on Chikiti or some kind of immediate mode GUI, -06:21.185 --> 06:32.168 +00:06:31.000 --> 00:06:37.399 something like that. But definitely GTK3 through Guile GI -06:33.808 --> 06:38.750 +00:06:37.400 --> 00:06:41.319 is the reference implementation. Things start there. But -06:41.298 --> 06:43.959 +00:06:41.320 --> 00:06:43.999 I'm very interested in supporting other GUIs, yes. Let's -06:45.199 --> 00:06:45.256 +00:06:44.000 --> 00:06:46.039 see. NOTE Q: Do you plan to provide improvements to Elisp as a language, or is the focus on a compatibility layer to facilitate doing all new extensions, etc. in Scheme? -00:06:45.257 --> 00:06:45.879 +00:06:46.040 --> 00:06:50.759 Question, do you plan to provide improvements to ELisp -06:47.540 --> 06:56.342 +00:06:50.760 --> 00:06:54.519 as a language or focus on a compatibility layer to -06:47.540 --> 06:56.342 +00:06:54.520 --> 00:06:57.999 facilitate all new extensions in Scheme? Yeah, the second -06:57.142 --> 06:57.962 +00:06:58.000 --> 00:07:04.719 one. I want to move off to Scheme. I would like for this -07:03.384 --> 07:05.264 +00:07:04.720 --> 00:07:08.999 project to try and keep up to date with each new release of -07:05.666 --> 07:10.789 +00:07:09.000 --> 00:07:13.799 Emacs and Emacs Lisp. That's a difficult moving target to -07:11.850 --> 07:14.552 +00:07:13.800 --> 00:07:18.639 follow, I realize. But to the greatest extent possible, any -07:15.152 --> 07:23.397 +00:07:18.640 --> 00:07:25.239 new features to Emacs Lisp will be pulled in from GNU Emacs. -07:25.419 --> 07:29.041 +00:07:25.240 --> 00:07:28.599 If we happen to be able to implement something cool in -07:25.419 --> 07:29.041 +00:07:28.600 --> 00:07:31.639 Scheme, and be able to port it over to Emacs Lisp, then sure, -07:29.437 --> 07:36.543 +00:07:31.640 --> 00:07:35.799 it'd be nice to be able to upload or to submit that upstream to -07:29.437 --> 07:36.543 +00:07:35.800 --> 00:07:43.079 the GNU Emacs. But I think I would prefer to have new features -07:38.584 --> 07:43.708 +00:07:43.080 --> 00:07:47.799 written in Scheme. I would like this gypsum to be more of a -07:43.989 --> 07:52.075 +00:07:47.800 --> 00:07:51.479 Scheme app platform that just happens to be able to also run -07:43.989 --> 07:52.075 +00:07:51.480 --> 00:07:56.199 Emacs Lisp. That's how I see it. Of course, this will be a -07:54.577 --> 07:56.699 +00:07:56.200 --> 00:08:00.799 community project. I'm open to debate about that if anybody -07:58.809 --> 08:02.012 +00:08:00.800 --> 00:08:02.079 wants to convince me otherwise. -08:08.439 --> 08:11.683 +00:08:02.080 --> 00:08:11.759 Why is being able to interpret all of that EL a useful goal? -08:12.464 --> 08:14.626 +00:08:11.760 --> 00:08:15.519 Sure, there is a lot of code written in Elisp. Can we -08:15.206 --> 08:17.749 +00:08:15.520 --> 00:08:18.959 consider... Oh, it's still being written. Please go ahead -08:18.390 --> 08:19.491 +00:08:18.960 --> 00:08:19.439 and finish writing. NOTE Q: Can we consider a translator like utility to convert elisp to scheme, once guile-emacs becomes a reality? -08:29.673 --> 08:35.576 +00:08:19.440 --> 00:08:32.519 Can we consider a translator like utility to convert eLisp -08:29.673 --> 08:35.576 +00:08:32.520 --> 00:08:37.519 to Scheme once Guile-Emacs has become a reality? -08:36.716 --> 08:37.076 +00:08:37.520 --> 00:08:42.119 Certainly. For the time being, I just wanted to get the -08:38.717 --> 08:42.639 +00:08:42.120 --> 00:08:47.559 interpreter running. So the actual, the Guile-Emacs Lisp, -08:44.520 --> 08:58.666 +00:08:47.560 --> 00:08:51.919 the one that was written in 2011 that I didn't write, that -08:44.520 --> 08:58.666 +00:08:51.920 --> 00:08:57.599 actually does compile to, I think it's the tree -08:44.520 --> 08:58.666 +00:08:57.600 --> 00:08:59.239 intermediate representation It's one of the intermediate -08:59.076 --> 09:03.697 +00:08:59.240 --> 00:09:03.759 languages that Guile uses to compile Guile scheme itself. -09:04.817 --> 09:09.299 +00:09:03.760 --> 00:09:09.079 So the Emacs lisp that was written before actually does -09:04.817 --> 09:09.299 +00:09:09.080 --> 00:09:13.119 that. It actually compiles and makes use of the entire Guile -09:09.339 --> 09:20.761 +00:09:13.120 --> 00:09:17.479 compiler tool chain and actually produces like JIT -09:09.339 --> 09:20.761 +00:09:17.480 --> 00:09:21.719 compilable binaries, which is really cool. Like I said, -09:23.342 --> 09:25.943 +00:09:21.720 --> 00:09:27.519 that's the one that I had trouble getting to work properly. -09:29.209 --> 09:30.890 +00:09:27.520 --> 00:09:34.399 Maybe we can follow that architecture. I'm not sure how to do -09:33.052 --> 09:45.102 +00:09:34.400 --> 00:09:37.919 that, but I would like to be able to do some kind of -09:33.052 --> 09:45.102 +00:09:37.920 --> 00:09:41.999 translating, keeping in mind that we want to have this be -09:33.052 --> 09:45.102 +00:09:42.000 --> 00:09:48.919 portable, do various schemes. And so Guile makes this very -09:45.988 --> 09:50.289 +00:09:48.920 --> 00:09:52.719 easy, but other schemes don't. Gambit might do this pretty -09:51.549 --> 09:53.530 +00:09:52.720 --> 00:09:57.919 well as well. It compiles to C and then compiles C down to a -09:53.950 --> 10:01.471 +00:09:57.920 --> 00:10:06.159 dynamically linkable library. So yeah, I think probably -10:03.372 --> 10:09.373 +00:10:06.160 --> 00:10:09.559 the most portable, I'm just thinking out loud right now, -10:10.652 --> 10:21.715 +00:10:09.560 --> 00:10:13.239 most portable implementation will just be able to -10:10.652 --> 10:21.715 +00:10:13.240 --> 00:10:17.119 translate Emacs Lisp directly to Scheme, which is not what -10:10.652 --> 10:21.715 +00:10:17.120 --> 00:10:22.439 the old Guile Emacs Lisp implementation does. That goes to -10:21.755 --> 10:26.777 +00:10:22.440 --> 00:10:26.439 TreeIL, so it's very, very Guile-specific, can't be -10:21.755 --> 10:26.777 +00:10:26.440 --> 00:10:30.799 ported. But yeah, if we could somehow get Emacs Lisp -10:28.359 --> 10:42.045 +00:10:30.800 --> 00:10:36.999 translated to Scheme and then compiled, say, in Shea Scheme -10:28.359 --> 10:42.045 +00:10:37.000 --> 00:10:40.879 or Gambit or MIT Scheme or one of those other compilers, that -10:28.359 --> 10:42.045 +00:10:40.880 --> 00:10:44.919 would be very cool. And I would absolutely love to do that. -10:44.906 --> 10:49.948 +00:10:44.920 --> 00:10:49.279 And I would very quickly accept any code into the code base -10:44.906 --> 10:49.948 +00:10:49.280 --> 00:10:50.599 that would do that. NOTE Q: Why is being able to interpret all of \`init.el\` an useful goal? -10:54.390 --> 10:56.291 +00:10:50.600 --> 00:10:59.119 Oh, and to answer the question about init.el, -10:59.207 --> 11:17.215 +00:10:59.120 --> 00:11:02.839 It's just because people spend a lot of time on their configs -10:59.207 --> 11:17.215 +00:11:02.840 --> 00:11:06.959 and it would be nice if, you know, you're starting to use this -10:59.207 --> 11:17.215 +00:11:06.960 --> 00:11:14.079 new editor and want it to be similar to Emacs users, just the -10:59.207 --> 11:17.215 +00:11:14.080 --> 00:11:16.519 Emacs community in general and people who are familiar with -10:59.207 --> 11:17.215 +00:11:16.520 --> 00:11:20.879 using Emacs. It would be more useful to everybody in the -11:17.715 --> 11:25.379 +00:11:20.880 --> 00:11:25.119 Emacs community if this were more compatible with GNU -11:17.715 --> 11:25.379 +00:11:25.120 --> 00:11:35.999 Emacs. And so that's why that's, I think that's an important -11:25.679 --> 11:27.960 +00:11:36.000 --> 00:11:38.559 goal. -11:34.465 --> 11:35.467 +00:11:38.560 --> 00:12:01.839 Question is not yet. Great. Oh, here comes another -11:38.471 --> 11:39.613 +00:12:01.840 --> 00:12:02.279 question. NOTE Q: What is the plan to handle elisp packages that depend on 3rd party/external libraries? (libgit/magit or rg/ripgrep)? -12:08.539 --> 12:17.742 +00:12:02.280 --> 00:12:11.879 Okay, what is the plan to handle elisp packages that depend -12:08.539 --> 12:17.742 +00:12:11.880 --> 00:12:16.119 on third-party or external libraries like git or magit -12:08.539 --> 12:17.742 +00:12:16.120 --> 00:12:22.719 or ripgrep? So that's going to be tricky. It depends on how -12:21.523 --> 12:26.224 +00:12:22.720 --> 00:12:27.079 these external packages are linked into emacs. If it's -12:26.844 --> 12:33.646 +00:12:27.080 --> 00:12:32.879 going to be a dynamic library like Robin Templeton's -12:26.844 --> 12:33.646 +00:12:32.880 --> 00:12:38.039 project which you load the libgit library into the Emacs -12:35.289 --> 12:41.931 +00:12:38.040 --> 00:12:43.159 process, that is going to be extremely difficult. So if you -12:44.032 --> 12:52.975 +00:12:43.160 --> 00:12:49.359 have an external library like, I don't know, libgit or -12:44.032 --> 12:52.975 +00:12:49.360 --> 00:12:59.279 what's the GUI thing? Cabal. No, not Cabal. Cairo, libcairo -12:57.736 --> 13:01.398 +00:12:59.280 --> 00:13:01.439 to do SVG graphics and so on. -13:04.483 --> 13:17.480 +00:13:01.440 --> 00:13:09.719 You can do that very easily with Guile, but then on top of -13:04.483 --> 13:17.480 +00:13:09.720 --> 00:13:14.719 that, implementing Emacs list bindings to it, I mean, -13:04.483 --> 13:17.480 +00:13:14.720 --> 00:13:17.199 you've got two layers there, and that makes things pretty -13:04.483 --> 13:17.480 +00:13:17.200 --> 00:13:23.119 difficult. So it's possible. And to some degree, maybe -13:21.935 --> 13:30.842 +00:13:23.120 --> 00:13:27.799 necessary for example, Cairo, if we want to do SVG graphics -13:21.935 --> 13:30.842 +00:13:27.800 --> 00:13:30.599 the way that Emacs Lisp does, we're going to have to have -13:21.935 --> 13:30.842 +00:13:30.600 --> 00:13:33.959 that. So that would be necessary. We would have to have those -13:32.643 --> 13:33.944 +00:13:33.960 --> 00:13:39.199 two layers. Yes, let's do that. But if it's like for Magit, -13:38.047 --> 13:50.596 +00:13:39.200 --> 00:13:45.479 you can just call out to your git process, and then you're -13:38.047 --> 13:50.596 +00:13:45.480 --> 00:13:50.719 just using the regular process APIs that Emacs Lisp has. And -13:51.451 --> 13:58.475 +00:13:50.720 --> 00:13:57.119 that can be, already we, like Guile has some very good -13:51.451 --> 13:58.475 +00:13:57.120 --> 00:14:08.079 implementations for process management. And so it would -13:59.055 --> 14:05.438 +00:14:08.080 --> 00:14:12.439 just be a matter of wrapping up those in the Emacs lisp form -13:59.055 --> 14:05.438 +00:14:12.440 --> 00:14:24.919 bindings. So yeah, dynamic libraries, I wanna try to avoid. -14:12.222 --> 14:20.366 +00:14:24.920 --> 00:14:32.799 And I would prefer to do things more through, you know, -14:12.222 --> 14:20.366 +00:14:32.800 --> 00:14:40.399 launching a child process in the Emacs process. and then -14:20.956 --> 14:24.798 +00:14:40.400 --> 00:14:47.239 communicating over the standard in, standard out -14:20.956 --> 14:24.798 +00:14:47.240 --> 00:14:47.959 channels. -14:29.460 --> 14:40.386 +00:14:47.960 --> 00:14:52.799 That's the easier way to do things, I think, because then you -14:29.460 --> 14:40.386 +00:14:52.800 --> 00:14:58.519 can just use the process library that Emacs already has, and -14:29.460 --> 14:40.386 +00:14:58.520 --> 00:15:03.239 you can just reuse all of that code. -14:43.969 --> 14:49.912 +00:15:03.240 --> 00:15:09.079 I'm not sure how ripgrep works, unfortunately, but I -14:43.969 --> 14:49.912 +00:15:09.080 --> 00:15:15.279 believe that's also a process, a child process. So, we can -14:50.412 --> 14:53.774 +00:15:15.280 --> 00:15:23.479 just reuse all of the Emacs Lisp code that does that already. -14:54.014 --> 15:05.979 +00:15:23.480 --> 00:15:30.399 We just need to make sure that the process management -14:54.014 --> 15:05.979 +00:15:30.400 --> 00:15:35.119 implementation and scheme is properly bound to Emacs Lisp, -14:54.014 --> 15:05.979 +00:15:35.120 --> 00:15:43.359 and it works the same as GNU Emacs does. Once that's all set, -15:06.360 --> 15:13.383 +00:15:43.360 --> 00:15:48.399 then these porcelains, like around git, should fall into -15:06.360 --> 15:13.383 +00:15:48.400 --> 00:15:55.279 place. without too much difficulty, hopefully. NOTE Q: Not really a question, but how about Schemacs as a name? -15:21.112 --> 15:22.593 +00:15:55.280 --> 00:15:59.199 How about Schemax as a name? I like the name. I like that name. -15:28.937 --> 15:32.920 +00:15:59.200 --> 00:16:03.119 I haven't really looked into like, is that already used or is -15:28.937 --> 15:32.920 +00:16:03.120 --> 00:16:09.759 that going to be confusing? But certainly something we can -15:33.380 --> 15:35.021 +00:16:09.760 --> 00:16:10.959 discuss. -15:38.243 --> 15:39.264 +00:16:10.960 --> 00:16:13.039 Another thing I should mention, -15:42.157 --> 15:48.278 +00:16:13.040 --> 00:16:18.759 I should probably set up a server or something like Discord -15:42.157 --> 15:48.278 +00:16:18.760 --> 00:16:25.359 or something like that. Discourse, not Discord. -15:51.619 --> 15:56.220 +00:16:25.360 --> 00:16:31.599 Discourse, the open source one, where we could actually -15:51.619 --> 15:56.220 +00:16:31.600 --> 00:16:49.239 chat about this stuff. For the time being, ActivityPub, -15:56.540 --> 16:05.562 +00:16:49.240 --> 00:16:52.399 mostly Mastodon, is how I communicate with people in real -15:56.540 --> 16:05.562 +00:16:52.400 --> 00:16:57.279 time, that or email. So if you want to get a hold of me, check -16:09.809 --> 16:15.571 +00:16:57.280 --> 00:17:02.439 the notes for this presentation and just send me an email. -16:16.752 --> 16:18.012 +00:17:02.440 --> 00:17:09.039 Any question at all is fine. If you want to contribute code, -16:19.633 --> 16:25.495 +00:17:09.040 --> 00:17:12.799 if you want to just learn how to contribute code, send me any -16:19.633 --> 16:25.495 +00:17:12.800 --> 00:17:22.199 questions. It's fine. I'm happy to answer them. And we can -16:30.256 --> 16:31.757 +00:17:22.200 --> 00:17:25.879 talk about the name as well. NOTE Q: Why is it not feasible for the Emacs layer that interprets Emacs Lisp (the core in C) ot have a Scheme interpreter, instead of using Guile? -16:45.931 --> 16:54.215 +00:17:25.880 --> 00:17:30.239 Okay, why is it not feasible for the Emacs layer that -16:45.931 --> 16:54.215 +00:17:30.240 --> 00:17:34.319 interprets Emacs Lisp, the core in C, have a Scheme -16:45.931 --> 16:54.215 +00:17:34.320 --> 00:17:39.799 interpreter instead of using Guile? Let's see, I have to, -16:55.496 --> 16:57.257 +00:17:39.800 --> 00:17:48.799 okay. Emacs layer interprets Emacs Lisp, the core in C, have -16:57.737 --> 17:05.942 +00:17:48.800 --> 00:17:54.079 a Scheme interpreter instead of using Guile. Okay, so that, -17:07.362 --> 17:13.906 +00:17:54.080 --> 00:17:59.959 the question xlarsx is asking, xlars, x, So Lars is asking, -17:14.744 --> 17:28.093 +00:17:59.960 --> 00:18:02.319 is it not feasible for there to be an -17:14.744 --> 17:28.093 +00:18:02.320 --> 00:18:06.839 Emacs layer that interprets Emacs Lisp have a scheme -17:14.744 --> 17:28.093 +00:18:06.840 --> 00:18:33.079 interpreter? This is Robin Templeton's project. And -17:30.815 --> 17:32.156 +00:18:33.080 --> 00:18:39.839 they're presenting later today. So check the roster and be -17:32.697 --> 17:41.303 +00:18:39.840 --> 00:18:45.199 sure to see that presentation because that's exactly what -17:32.697 --> 17:41.303 +00:18:45.200 --> 00:18:52.119 Robin Templeton is doing. That's not what I'm doing though. -17:44.419 --> 17:46.459 +00:18:52.120 --> 00:18:57.239 I'm trying to create something in Scheme. But yes, there is -17:48.280 --> 17:54.921 +00:18:57.240 --> 00:19:02.959 an attempt to get an Scheme interpreter to run inside of -17:48.280 --> 17:54.921 +00:19:02.960 --> 00:19:07.159 Emacs itself. And it has its own method of binding to Emacs -17:55.181 --> 18:05.323 +00:19:07.160 --> 00:19:11.199 Lisp functions and translating data like Lisp structures -17:55.181 --> 18:05.323 +00:19:11.200 --> 00:19:14.439 between Guile Scheme and Emacs Lisp. Robin will explain all -18:05.943 --> 18:08.284 +00:19:14.440 --> 00:19:15.799 of that in their presentation. -18:28.519 --> 18:33.020 +00:19:15.800 --> 00:19:18.919 OK, I think I've got through all the questions on Etherpad. -18:33.620 --> 18:35.500 +00:19:18.920 --> 00:19:23.879 But I'm going to hang out here for a bit longer. And yeah, feel -18:37.621 --> 18:46.182 +00:19:23.880 --> 00:19:28.239 free to do a video chat with me or send me more questions on -18:37.621 --> 18:46.182 +00:19:28.240 --> 00:19:33.839 Etherpad or here in the big blue button. And so I'm just going -18:47.002 --> 18:48.082 +00:19:33.840 --> 00:21:49.119 to hang out. And thanks for asking all your questions. And -18:51.663 --> 18:56.024 +00:21:49.120 --> 00:21:50.839 yeah, I look forward to working with all of you if you're -18:51.663 --> 18:56.024 +00:21:50.840 --> 00:21:51.799 interested. take it easy. Thanks so much for the talk and -18:59.935 --> 19:08.180 +00:21:51.800 --> 00:21:53.199 looking forward to seeing some of your progress as this -18:59.935 --> 19:08.180 +00:21:53.200 --> 00:21:54.359 moves forward, exciting space. We'll go ahead and leave the -19:09.261 --> 19:14.925 +00:21:54.360 --> 00:21:54.879 room open for you and thanks for offering to hang out and chat -19:09.261 --> 19:14.925 +00:21:54.880 --> 00:21:55.639 with other people that come by. Feel free to throw something -19:15.025 --> 19:18.287 +00:21:55.640 --> 00:21:56.719 in the chat if you want to remind people you're still here. -19:19.557 --> 19:25.143 +00:21:56.720 --> 00:21:57.919 Meanwhile, on the stream, we have moved along to our next -19:19.557 --> 19:25.143 +00:21:57.920 --> 00:21:59.599 talk on Rust, and that is just getting started. But again, -19:25.283 --> 19:30.549 +00:21:59.600 --> 00:22:00.479 we're continuing to record this, and I'll just keep an eye on -19:25.283 --> 19:30.549 +00:22:00.480 --> 00:22:01.239 it to stop the recording. Thank you. Thank you. It was -19:33.352 --> 19:33.853 +00:22:01.240 --> 00:22:01.559 awesome. -21:47.935 --> 21:50.558 +00:22:01.560 --> 00:22:03.959 So it seems like it's slowed down here for the Q&A. I don't see -21:50.638 --> 21:53.741 +00:22:03.960 --> 00:22:05.439 anybody else on BBB, so I'm going to go ahead and stop the -21:50.638 --> 21:53.741 +00:22:05.440 --> 00:22:08.479 recording. We can start it back up. I would say, yes, there's -21:55.282 --> 21:58.906 +00:22:08.480 --> 00:22:09.519 a lot of things you can do with this. You can handle -21:58.926 --> 22:00.627 +00:22:09.520 --> 00:22:11.239 processing. Yeah, I'm going to try and join over the chat for -22:02.029 --> 22:07.614 +00:22:11.240 --> 00:22:14.679 the next talk. I'm not sure if I can do both big blue buttons at -22:08.635 --> 22:11.538 +00:22:14.680 --> 00:22:15.759 the same time. You should be able to just watch your mute -22:13.206 --> 22:19.998 +00:22:15.760 --> 00:22:19.159 settings and mute tab settings and whatever all you have to -22:13.206 --> 22:19.998 +00:22:19.160 --> 00:23:37.800 avoid bleed through. Okay. diff --git a/2024/captions/emacsconf-2024-julia--exploring-shared-philosophies-in-julia-and-emacs--gabriele-bozzola--answers.vtt b/2024/captions/emacsconf-2024-julia--exploring-shared-philosophies-in-julia-and-emacs--gabriele-bozzola--answers.vtt index d37f80ef..5f0d3fc5 100644 --- a/2024/captions/emacsconf-2024-julia--exploring-shared-philosophies-in-julia-and-emacs--gabriele-bozzola--answers.vtt +++ b/2024/captions/emacsconf-2024-julia--exploring-shared-philosophies-in-julia-and-emacs--gabriele-bozzola--answers.vtt @@ -2,345 +2,345 @@ WEBVTT NOTE Q: Do you have any suggestions for interactive debugging of Julia code in Emacs? -00:00.089 --> 00:00.829 +00:00:00.000 --> 00:00:05.319 ... answer to that. I, I think the infrastructure for an -00:01.509 --> 00:14.192 +00:00:05.320 --> 00:00:08.599 ecosystem in Julia in general is as mature as other -00:01.509 --> 00:14.192 +00:00:08.600 --> 00:00:12.559 languages, and even debugger infiltrator themselves are -00:01.509 --> 00:14.192 +00:00:12.560 --> 00:00:17.519 not particularly well developed. And so I don't think -00:15.853 --> 00:19.214 +00:00:17.520 --> 00:00:21.519 there's much we can do about that right now. I think that it's -00:21.570 --> 00:28.057 +00:00:21.520 --> 00:00:25.999 unfortunate that most of the development for these type of -00:21.570 --> 00:28.057 +00:00:26.000 --> 00:00:31.759 tools is tightly linked to VS code. But even there, I don't -00:29.218 --> 00:36.225 +00:00:31.760 --> 00:00:35.719 think that there's much done in terms of interactive -00:29.218 --> 00:36.225 +00:00:35.720 --> 00:00:42.359 debugging. So I, yeah, I think this has to be worked on mostly -00:36.866 --> 00:43.213 +00:00:42.360 --> 00:00:47.519 on the Julia side first. And then probably Emacs can get -00:43.820 --> 00:48.303 +00:00:47.520 --> 00:00:51.239 something out of that. I know that there's development in -00:49.183 --> 00:57.728 +00:00:51.240 --> 00:00:55.559 debugger.jl itself for future releases to make it at least -00:49.183 --> 00:57.728 +00:00:55.560 --> 00:01:01.839 faster and more stable. But yeah, I think we're not there as -00:58.809 --> 01:03.852 +00:01:01.840 --> 00:01:06.879 Julia community itself. So let alone Emacs, integration -01:04.192 --> 01:07.234 +00:01:06.880 --> 00:01:11.239 with Emacs. The way I personally debug is mostly using, -01:08.286 --> 01:15.508 +00:01:11.240 --> 00:01:15.199 well, debugger and infiltrator with Julia REPL mode in NOTE Q: Can you call out something that Julia has that Emacs does not, and which could benefit Emacs? -01:08.286 --> 01:15.508 +00:01:15.200 --> 00:01:21.679 Emacs. The second question, can you call out something that -01:18.009 --> 01:24.891 +00:01:21.680 --> 00:01:26.839 Julia has that Emacs does not and which could benefit Emacs? -01:26.852 --> 01:27.852 +00:01:26.840 --> 00:01:31.879 Nothing stands out to me except the usual multi-threading -01:28.848 --> 01:32.552 +00:01:31.880 --> 00:01:36.119 and things like this. I don't necessarily see something -01:33.432 --> 01:46.783 +00:01:36.120 --> 00:01:42.479 that Julia has going on that DMX doesn't have, but I see some -01:33.432 --> 01:46.783 +00:01:42.480 --> 00:01:45.839 differences and approaches that I think are important, -01:33.432 --> 01:46.783 +00:01:45.840 --> 00:01:49.759 like the community. I think Julia is a very active and tight -01:47.384 --> 01:50.266 +00:01:49.760 --> 00:01:54.159 community. Julia uses Slack and is very, very active. I -01:54.093 --> 01:57.736 +00:01:54.160 --> 00:01:56.559 think he might say something like that, but it's maybe more -01:54.093 --> 01:57.736 +00:01:56.560 --> 00:02:01.799 on Reddit, IRC. JuliaCon is big and brings together lots and -01:59.078 --> 02:02.381 +00:02:01.800 --> 00:02:05.159 lots of people. And I think the sense of community is really -02:03.221 --> 02:05.263 +00:02:05.160 --> 00:02:10.479 powerful. It's very easy to essentially meet people that -02:06.364 --> 02:16.834 +00:02:10.480 --> 00:02:12.919 are interested in what we're building and interested in -02:06.364 --> 02:16.834 +00:02:12.920 --> 00:02:15.999 what we're doing and interested in Julian, our, you know, -02:06.364 --> 02:16.834 +00:02:16.000 --> 00:02:21.239 hacker spirit. I think Emacs is a very strong community. -02:21.228 --> 02:26.151 +00:02:21.240 --> 00:02:24.279 We're here on a Saturday talking about Emacs, which again -02:21.228 --> 02:26.151 +00:02:24.280 --> 00:02:29.679 proves that we are doing this. But I'd like to emphasize that -02:27.192 --> 02:35.696 +00:02:29.680 --> 00:02:33.639 the community is a really important aspect in Julia that I -02:27.192 --> 02:35.696 +00:02:33.640 --> 00:02:38.159 think we should double down on our side. The next question is NOTE Q: Is there a way to use lisp syntax with Julia, like hy for python or lisp flavoured erlang? -02:36.797 --> 02:44.841 +00:02:38.160 --> 00:02:46.519 about Lisp syntax with Julia, like what we can do in Python. -02:48.038 --> 02:53.180 +00:02:46.520 --> 00:02:52.359 I don't think that's, I don't, I am not aware of any package -02:48.038 --> 02:53.180 +00:02:52.360 --> 00:02:56.879 that does that. I would bet that there's something there. I -02:56.722 --> 02:58.063 +00:02:56.880 --> 00:03:01.519 think that that's possible. Indeed, there used to be a Lisp -02:59.243 --> 03:07.027 +00:03:01.520 --> 00:03:08.079 interpreter in Julia itself until the latest release. The -03:07.647 --> 03:12.229 +00:03:08.080 --> 00:03:12.039 syntax parsing was done with a Lisp, it was called TemtoList -03:07.647 --> 03:12.229 +00:03:12.040 --> 00:03:18.679 indeed. I think this got rid, get rid of this for our more -03:16.124 --> 03:23.489 +00:03:18.680 --> 00:03:23.039 Julia-based solution that is faster and with better code -03:16.124 --> 03:23.489 +00:03:23.040 --> 00:03:28.599 provenance. I think that it should be possible to use the -03:25.430 --> 03:35.437 +00:03:28.600 --> 00:03:33.319 metaprogramming features in Julia to change the structure -03:25.430 --> 03:35.437 +00:03:33.320 --> 00:03:38.159 of your syntax to be a Lispy syntax. I do want to emphasize -03:36.238 --> 00:03:44.664 +00:03:38.160 --> 00:03:43.879 that Julia is heavily inspired by Lisp, so I wouldn't be -03:36.238 --> 03:44.664 +00:03:43.880 --> 00:03:49.239 surprised if if something like this were possible. -03:49.309 --> 00:03:51.167 +00:03:49.240 --> 00:03:51.239 I have tried Julia Snail. NOTE Q: Have you tried the Julia Snail package for Emacs? It tries to be like SLY/SLIME for Common Lisp. -00:03:51.168 --> 00:03:51.070 +00:03:51.240 --> 00:03:54.399 So the next question is about Julia -03:51.270 --> 03:52.712 +00:03:54.400 --> 00:03:58.199 Snail. I found Julia REPL to be a little bit easier to set up -03:53.312 --> 03:58.436 +00:03:58.200 --> 00:04:02.839 and use. So I just settled on that. I should maybe revisit -04:00.918 --> 04:03.480 +00:04:02.840 --> 00:04:05.999 that. In particular, I use the Julia REPL with the vterm -04:03.720 --> 04:11.406 +00:04:06.000 --> 00:04:10.959 backend, which essentially makes a companion REPL to my -04:03.720 --> 04:11.406 +00:04:10.960 --> 00:04:15.439 scripts. And that works for me. I do think that the tooling -04:15.638 --> 04:16.518 +00:04:15.440 --> 00:04:19.239 uh, could be improved. I think there is definitely much room -04:17.399 --> 04:22.040 +00:04:19.240 --> 00:04:26.079 and I would like to see improvement in that area. Um, and, uh, NOTE Q: Is there a data inspector for a Julia REPL available that you can use in Emacs? -04:22.940 --> 04:28.322 +00:04:26.080 --> 00:04:31.639 so we have data inspector for Julia REPL. -04:32.043 --> 04:34.784 +00:04:31.640 --> 00:04:37.279 I don't think so. I don't, is there any data inspector -04:34.804 --> 04:39.826 +00:04:37.280 --> 00:04:40.439 in for, for the Julia REPL that we can use in Emacs? -04:43.223 --> 00:04:43.489 +00:04:40.440 --> 00:04:44.839 I'm not sure. I don't think so. -00:04:44.840 --> 00:04:47.839 +00:04:44.840 --> 00:04:47.799 I think the way I look at data is -00:04:47.840 --> 00:04:50.519 +00:04:47.800 --> 00:04:50.519 essentially ignoring Emacs when encoded. It's just using the -00:04:50.520 --> 00:04:54.759 +00:04:50.520 --> 00:04:56.839 REPL. And again, with Julia REPL. So I'm not aware of any -00:04:54.760 --> 00:04:57.720 +00:04:56.840 --> 00:05:00.479 specialized tool And again, maybe this is, again, a good -04:58.652 --> 05:05.595 +00:05:00.480 --> 00:05:04.279 moment to emphasize that tooling, the Julia community -04:58.652 --> 05:05.595 +00:05:04.280 --> 00:05:09.079 clusters around VS Code. And there is tools like the, pretty -05:06.315 --> 05:11.578 +00:05:09.080 --> 00:05:14.199 much all the work with VS Code, unfortunately. And while -05:12.578 --> 05:21.242 +00:05:14.200 --> 00:05:17.759 there's a very, very decent Julia mode and Julia repo mode -05:12.578 --> 05:21.242 +00:05:17.760 --> 00:05:21.439 and Julia snail, there's definitely, definitely room for -05:12.578 --> 05:21.242 +00:05:21.440 --> 00:05:24.359 improvement. NOTE Q: Have you tried literate programming Julia (using Org babel or some other means) in Emacs? -05:24.443 --> 05:28.145 +00:05:24.360 --> 00:05:27.759 Next, we have a question about literate programming in -05:24.443 --> 05:28.145 +00:05:27.760 --> 00:05:32.439 Julia. I haven't done much of it with Org Babel or -05:29.505 --> 05:32.906 +00:05:32.440 --> 00:05:37.079 anything else. I haven't done much of it. I can say that Julia -05:35.827 --> 05:46.070 +00:05:37.080 --> 00:05:40.719 has developed a new iteration of notebooks called Pluto. -05:46.090 --> 05:48.471 +00:05:40.720 --> 00:05:47.119 Here I'm thinking about Jupyter notebooks. The Pluto -05:51.021 --> 06:02.988 +00:05:47.120 --> 00:05:55.359 notebooks for Julia try to remove a bunch of the pain points -05:51.021 --> 06:02.988 +00:05:55.360 --> 00:06:00.439 that Jupyter notebooks have, meaning you cannot easily -05:51.021 --> 06:02.988 +00:06:00.440 --> 00:06:03.639 commit them to Git or things like this. -06:06.450 --> 06:09.152 +00:06:03.640 --> 00:06:09.279 I haven't used them, but I know some people are very fond of -06:06.450 --> 06:09.152 +00:06:09.280 --> 00:06:13.559 them. And so I think that that's what some of the Julia -06:09.872 --> 06:15.195 +00:06:13.560 --> 00:06:16.879 community would use for notebooks. And I think they can -06:15.315 --> 06:19.298 +00:06:16.880 --> 00:06:22.239 interact with Emacs with no problem. And that would be a form -06:20.974 --> 06:23.035 +00:06:22.240 --> 00:06:26.879 of later programming. But if you can do it in Python, you can -06:24.015 --> 06:27.696 +00:06:26.880 --> 00:06:32.119 do it in Julia. I think there is no reason. And actually, you -06:30.617 --> 06:38.719 +00:06:32.120 --> 00:06:35.839 can take advantage of all this just-in-time or -06:30.617 --> 06:38.719 +00:06:35.840 --> 00:06:38.239 just-out-of-time compilation by keeping the same -06:30.617 --> 06:38.719 +00:06:38.240 --> 00:06:45.199 session. So I think it will be definitely a nice use case. So -06:44.681 --> 06:47.222 +00:06:45.200 --> 00:06:49.199 these are the questions that I see here. I'm going to scroll -06:48.561 --> 06:54.486 +00:06:49.200 --> 00:06:52.759 through the comments and see if there's something that I -06:48.561 --> 06:54.486 +00:06:52.760 --> 00:06:57.319 should say about comments. I'm excited people want to learn -06:56.228 --> 06:57.669 +00:06:57.320 --> 00:07:02.519 Julia. I have to say that if I want to do GPU computing -06:58.990 --> 07:06.757 +00:07:02.520 --> 00:07:06.399 nowadays, I find it much easier to do it with Julia than with -06:58.990 --> 07:06.757 +00:07:06.400 --> 00:07:11.759 CUDA. So I encourage people to look into that. And I do, -07:11.758 --> 07:26.807 +00:07:11.760 --> 00:07:19.359 again, I would like to share what makes me excited about -07:11.758 --> 07:26.807 +00:07:19.360 --> 00:07:23.799 Emacs, about this being open, being collaborative, being -07:11.758 --> 07:26.807 +00:07:23.800 --> 00:07:26.399 respectable with documentation is something that I find in -07:11.758 --> 07:26.807 +00:07:26.400 --> 00:07:30.999 Julia. So I think people that are excited about the same -07:27.367 --> 07:35.192 +00:07:31.000 --> 00:07:35.279 features will find a little bit of joy in working with Julia. -07:38.214 --> 07:39.675 +00:07:35.280 --> 00:07:41.999 I think I addressed what I have here. I don't know if there's -07:40.189 --> 07:43.532 +00:07:42.000 --> 00:07:43.559 anything else that I should add. -07:51.718 --> 07:54.000 +00:07:43.560 --> 00:07:52.879 It took me a minute to unmute there. -00:07:54.040 --> 00:07:58.399 +00:07:52.880 --> 00:07:57.519 No, I think that was awesome. And thank you so much. -00:07:58.400 --> 00:08:00.399 +00:07:57.520 --> 00:08:00.119 I guess I thought it would -00:08:00.400 --> 00:08:06.559 +00:08:00.120 --> 00:08:06.279 collapse that shared area on BBB, my mistake, on the stream, -00:08:06.560 --> 00:08:12.399 +00:08:06.280 --> 00:08:12.359 or I would have left it open. But in any case, no, I thought -00:08:12.400 --> 00:08:15.079 +00:08:12.360 --> 00:08:15.079 that was great. You did a great job of responding to all the -00:08:15.080 --> 00:08:17.879 +00:08:15.080 --> 00:08:17.839 questions and comments. And thank you again so much for your -00:08:17.880 --> 00:08:20.920 +00:08:17.840 --> 00:08:23.199 talk and getting us all excited to learn Julia. Thank you. -08:24.094 --> 08:25.275 +00:08:23.200 --> 00:08:27.759 Enjoy EmacsConf. And again, thanks so much for attending, -08:25.335 --> 08:30.220 +00:08:27.760 --> 00:08:42.400 for being EmacsConf. Thank you. diff --git a/2024/captions/emacsconf-2024-transducers--transducers-finally-ergonomic-data-processing-for-emacs--colin-woodbury--answers.vtt b/2024/captions/emacsconf-2024-transducers--transducers-finally-ergonomic-data-processing-for-emacs--colin-woodbury--answers.vtt index 375cad2a..e8cb84c4 100644 --- a/2024/captions/emacsconf-2024-transducers--transducers-finally-ergonomic-data-processing-for-emacs--colin-woodbury--answers.vtt +++ b/2024/captions/emacsconf-2024-transducers--transducers-finally-ergonomic-data-processing-for-emacs--colin-woodbury--answers.vtt @@ -10,7 +10,7 @@ morning here in Tokyo. Are we connected all right? 00:00:37.880 --> 00:00:40.879 -Okay, I seem to be struggling still with my audio. 1 2nd +Okay, I seem to be struggling still with my audio. One second... 00:00:40.880 --> 00:00:44.519 calling. Yeah, you were muted for a moment there. Okay, diff --git a/2024/info/blee-before.md b/2024/info/blee-before.md index 1c53259d..e96b5b09 100644 --- a/2024/info/blee-before.md +++ b/2024/info/blee-before.md @@ -26,7 +26,7 @@ Status: TO_CAPTION_QA 42:54.267 Economics and Business Dimmensions of ByStar Digital Ecosystem 43:38.433 Pointers for Digging Deeper -"""]]
Duration: 45:30 minutes
+"""]]
Duration: 45:30 minutes
# Q&A @@ -37,6 +37,6 @@ Status: TO_CAPTION_QA 09:40.053 Q: As a specific example of how "ownership is not clean" ... 15:05.278 Q: Do you have any recommended reading materials designed for such an audience? -"""]]
Listen to just the audio:
Duration: 18:11 minutes
+"""]]
Listen to just the audio:
Duration: 18:11 minutes
# Description \ No newline at end of file diff --git a/2024/info/casual-before.md b/2024/info/casual-before.md index 6751ca43..c580fe70 100644 --- a/2024/info/casual-before.md +++ b/2024/info/casual-before.md @@ -29,7 +29,7 @@ Status: TO_CAPTION_QA 17:02.640 Casual has transformed my user experience with Emacs 17:34.451 Thanks and acknowledgements -"""]]
Duration: 18:24 minutes
+"""]]
Duration: 18:24 minutes
# Q&A @@ -42,6 +42,6 @@ Status: TO_CAPTION_QA 14:40.282 Q: What modes are you working on at the moment for casual / are excited to explore? 18:14.280 Getting older -"""]]
Listen to just the audio:
Duration: 22:12 minutes
+"""]]
Listen to just the audio:
Duration: 22:12 minutes
# Description \ No newline at end of file diff --git a/2024/info/color-after.md b/2024/info/color-after.md index fd9b31fd..a6726801 100644 --- a/2024/info/color-after.md +++ b/2024/info/color-after.md @@ -192,256 +192,256 @@ Captioner: sachac

Q&A transcript (unedited)

-[[!template text="""... Org mode and kind of note taking. And that meant that it wasn't""" start="00:00:00.169" video="qanda-color" id="subtitle"]] -[[!template text="""too difficult to get started with. But when I started more on""" start="00:00:02.810" video="qanda-color" id="subtitle"]] -[[!template text="""the coding side, because I'm a software engineer, you know,""" start="00:00:08.972" video="qanda-color" id="subtitle"]] -[[!template text="""on the day job. That kind of got me to think that the colors and""" start="00:00:08.972" video="qanda-color" id="subtitle"]] -[[!template text="""how themes look, how Emacs looks, was affecting. And that's""" start="00:00:16.366" video="qanda-color" id="subtitle"]] -[[!template text="""how it kind of came to picture. So I could have kind of gone""" start="00:00:25.331" video="qanda-color" id="subtitle"]] -[[!template text="""into a little bit more coding side of things, but I didn't""" start="00:00:29.073" video="qanda-color" id="subtitle"]] -[[!template text="""want to stress too much on the talk. So that's why I kind of""" start="00:00:29.073" video="qanda-color" id="subtitle"]] -[[!template text="""stuck to a very small bits of Org Mode and Elisp. And yeah, I""" start="00:00:36.957" video="qanda-color" id="subtitle"]] -[[!template text="""think that's how it came about. Yeah, but that's perfectly""" start="00:00:42.319" video="qanda-color" id="subtitle"]] -[[!template text="""fine. That's one of the chief reasons why we have two tracks""" start="00:00:46.536" video="qanda-color" id="subtitle"]] -[[!template text="""for Emacs content. We've had those for the last four years, I""" start="00:00:49.437" video="qanda-color" id="subtitle"]] -[[!template text="""think. It's because we have a general track, which is more""" start="00:00:52.798" video="qanda-color" id="subtitle"]] -[[!template text="""geared towards people who want a general... well,""" start="00:00:55.119" video="qanda-color" id="subtitle"]] -[[!template text="""generally people who are highly interested into org mode""" start="00:00:55.119" video="qanda-color" id="subtitle"]] -[[!template text="""and not necessarily into coding, but just to whet their""" start="00:00:55.119" video="qanda-color" id="subtitle"]] -[[!template text="""appetite to what can be done. And on the DevTrack, we have,""" start="00:00:55.119" video="qanda-color" id="subtitle"]] -[[!template text="""well, this year we have talked about Rust and about other""" start="00:01:06.082" video="qanda-color" id="subtitle"]] -[[!template text="""fancy things that people can do with Emacs. But, you know,""" start="00:01:06.082" video="qanda-color" id="subtitle"]] -[[!template text="""I'm also a software engineer, you know, we do this all the""" start="00:01:13.006" video="qanda-color" id="subtitle"]] -[[!template text="""time. Sometimes it's just fine to just chat about colors and""" start="00:01:13.006" video="qanda-color" id="subtitle"]] -[[!template text="""just the results of what we develop rather than how the""" start="00:01:15.808" video="qanda-color" id="subtitle"]] -[[!template text="""sausage is made. So that's completely fine too. I'm not sure""" start="00:01:15.808" video="qanda-color" id="subtitle"]] +[[!template text="""... Org mode and kind of note taking. And that meant that it wasn't""" start="00:00:00.000" video="qanda-color" id="subtitle"]] +[[!template text="""too difficult to get started with. But when I started more on""" start="00:00:06.040" video="qanda-color" id="subtitle"]] +[[!template text="""the coding side, because I'm a software engineer, you know,""" start="00:00:10.680" video="qanda-color" id="subtitle"]] +[[!template text="""on the day job. That kind of got me to think that the colors and""" start="00:00:14.960" video="qanda-color" id="subtitle"]] +[[!template text="""how themes look, how Emacs looks, was affecting. And that's""" start="00:00:20.680" video="qanda-color" id="subtitle"]] +[[!template text="""how it kind of came to picture. So I could have kind of gone""" start="00:00:26.480" video="qanda-color" id="subtitle"]] +[[!template text="""into a little bit more coding side of things, but I didn't""" start="00:00:30.720" video="qanda-color" id="subtitle"]] +[[!template text="""want to stress too much on the talk. So that's why I kind of""" start="00:00:34.920" video="qanda-color" id="subtitle"]] +[[!template text="""stuck to a very small bits of Org Mode and Elisp. And yeah, I""" start="00:00:38.320" video="qanda-color" id="subtitle"]] +[[!template text="""think that's how it came about. Yeah, but that's perfectly""" start="00:00:43.440" video="qanda-color" id="subtitle"]] +[[!template text="""fine. That's one of the chief reasons why we have two tracks""" start="00:00:48.160" video="qanda-color" id="subtitle"]] +[[!template text="""for Emacs content. We've had those for the last four years, I""" start="00:00:52.120" video="qanda-color" id="subtitle"]] +[[!template text="""think. It's because we have a general track, which is more""" start="00:00:54.800" video="qanda-color" id="subtitle"]] +[[!template text="""geared towards people who want a general... well,""" start="00:00:57.280" video="qanda-color" id="subtitle"]] +[[!template text="""generally people who are highly interested into org mode""" start="00:00:59.240" video="qanda-color" id="subtitle"]] +[[!template text="""and not necessarily into coding, but just to whet their""" start="00:01:01.800" video="qanda-color" id="subtitle"]] +[[!template text="""appetite to what can be done. And on the DevTrack, we have,""" start="00:01:04.000" video="qanda-color" id="subtitle"]] +[[!template text="""well, this year we have talked about Rust and about other""" start="00:01:08.400" video="qanda-color" id="subtitle"]] +[[!template text="""fancy things that people can do with Emacs. But, you know,""" start="00:01:11.520" video="qanda-color" id="subtitle"]] +[[!template text="""I'm also a software engineer, you know, we do this all the""" start="00:01:13.560" video="qanda-color" id="subtitle"]] +[[!template text="""time. Sometimes it's just fine to just chat about colors and""" start="00:01:15.560" video="qanda-color" id="subtitle"]] +[[!template text="""just the results of what we develop rather than how the""" start="00:01:18.080" video="qanda-color" id="subtitle"]] +[[!template text="""sausage is made. So that's completely fine too. I'm not sure""" start="00:01:20.960" video="qanda-color" id="subtitle"]] -
[[!template new="1" text="""Why colour?""" start="00:01:23.733" video="qanda-color" id="subtitle"]]
[[!template text="""if you mentioned it in your presentation, but why color, out""" start="00:01:23.733" video="qanda-color" id="subtitle"]] -[[!template text="""of all the things you could be ricing on your setup, why were""" start="00:01:23.733" video="qanda-color" id="subtitle"]] -[[!template text="""you so interested about colors? I think it was just that""" start="00:01:23.733" video="qanda-color" id="subtitle"]] -[[!template text="""mainly that I had to do a lot of context switch between""" start="00:01:34.870" video="qanda-color" id="subtitle"]] -[[!template text="""different languages. Elisp is not the one because Elisp is""" start="00:01:34.870" video="qanda-color" id="subtitle"]] -[[!template text="""something that I would do for Emacs editing. But for day job,""" start="00:01:41.576" video="qanda-color" id="subtitle"]] -[[!template text="""I had to use mainly Go as I work with Kubernetes quite a bit. So""" start="00:01:47.061" video="qanda-color" id="subtitle"]] -[[!template text="""Go and also web languages like TypeScript, JavaScript, you""" start="00:01:52.525" video="qanda-color" id="subtitle"]] -[[!template text="""know, those languages, where I felt that whenever I was""" start="00:01:58.090" video="qanda-color" id="subtitle"]] -[[!template text="""switching context to a different language, I felt that it's""" start="00:01:58.090" video="qanda-color" id="subtitle"]] -[[!template text="""kind of annoying to see all the different colors in""" start="00:01:58.090" video="qanda-color" id="subtitle"]] -[[!template text="""languages like TypeScript, where, you know, VS Code way""" start="00:01:58.090" video="qanda-color" id="subtitle"]] -[[!template text="""would be very full of colors. which I felt that, okay, like,""" start="00:01:58.090" video="qanda-color" id="subtitle"]] -[[!template text="""why do I have to have that many different colors on let and""" start="00:02:14.262" video="qanda-color" id="subtitle"]] -[[!template text="""constant or the keywords where it could be just a white text?""" start="00:02:14.262" video="qanda-color" id="subtitle"]] -[[!template text="""It didn't have to be that colorful. So that was the bit, the""" start="00:02:23.789" video="qanda-color" id="subtitle"]] -[[!template text="""most annoying bit when it came to context switching. And I""" start="00:02:25.890" video="qanda-color" id="subtitle"]] -[[!template text="""felt that that just didn't happen in the Org Mode or writing""" start="00:02:30.974" video="qanda-color" id="subtitle"]] -[[!template text="""in general. So I had to find a way to make it work, make more""" start="00:02:30.974" video="qanda-color" id="subtitle"]] -[[!template text="""coding make my coding more kind of friendly to me and that's""" start="00:02:36.017" video="qanda-color" id="subtitle"]] -[[!template text="""when I thought maybe just the colors are something that's""" start="00:02:42.173" video="qanda-color" id="subtitle"]] -[[!template text="""bothering me and it actually was the case and that's how I got""" start="00:02:42.173" video="qanda-color" id="subtitle"]] -[[!template text="""to more into the color kind of journey and got too much into it""" start="00:02:42.173" video="qanda-color" id="subtitle"]] -[[!template text="""I guess. Right, and was it what eventually motivated you to""" start="00:02:42.173" video="qanda-color" id="subtitle"]] +
[[!template new="1" text="""Why colour?""" start="00:01:24.840" video="qanda-color" id="subtitle"]]
[[!template text="""if you mentioned it in your presentation, but why color, out""" start="00:01:24.840" video="qanda-color" id="subtitle"]] +[[!template text="""of all the things you could be ricing on your setup, why were""" start="00:01:28.880" video="qanda-color" id="subtitle"]] +[[!template text="""you so interested about colors? I think it was just that""" start="00:01:31.480" video="qanda-color" id="subtitle"]] +[[!template text="""mainly that I had to do a lot of context switch between""" start="00:01:37.560" video="qanda-color" id="subtitle"]] +[[!template text="""different languages. Elisp is not the one because Elisp is""" start="00:01:40.240" video="qanda-color" id="subtitle"]] +[[!template text="""something that I would do for Emacs editing. But for day job,""" start="00:01:44.120" video="qanda-color" id="subtitle"]] +[[!template text="""I had to use mainly Go as I work with Kubernetes quite a bit. So""" start="00:01:48.080" video="qanda-color" id="subtitle"]] +[[!template text="""Go and also web languages like TypeScript, JavaScript, you""" start="00:01:53.000" video="qanda-color" id="subtitle"]] +[[!template text="""know, those languages, where I felt that whenever I was""" start="00:01:58.120" video="qanda-color" id="subtitle"]] +[[!template text="""switching context to a different language, I felt that it's""" start="00:02:01.520" video="qanda-color" id="subtitle"]] +[[!template text="""kind of annoying to see all the different colors in""" start="00:02:05.360" video="qanda-color" id="subtitle"]] +[[!template text="""languages like TypeScript, where, you know, VS Code way""" start="00:02:08.840" video="qanda-color" id="subtitle"]] +[[!template text="""would be very full of colors. which I felt that, okay, like,""" start="00:02:12.000" video="qanda-color" id="subtitle"]] +[[!template text="""why do I have to have that many different colors on let and""" start="00:02:15.800" video="qanda-color" id="subtitle"]] +[[!template text="""constant or the keywords where it could be just a white text?""" start="00:02:18.760" video="qanda-color" id="subtitle"]] +[[!template text="""It didn't have to be that colorful. So that was the bit, the""" start="00:02:23.760" video="qanda-color" id="subtitle"]] +[[!template text="""most annoying bit when it came to context switching. And I""" start="00:02:27.680" video="qanda-color" id="subtitle"]] +[[!template text="""felt that that just didn't happen in the Org Mode or writing""" start="00:02:31.400" video="qanda-color" id="subtitle"]] +[[!template text="""in general. So I had to find a way to make it work, make more""" start="00:02:34.760" video="qanda-color" id="subtitle"]] +[[!template text="""coding make my coding more kind of friendly to me and that's""" start="00:02:40.800" video="qanda-color" id="subtitle"]] +[[!template text="""when I thought maybe just the colors are something that's""" start="00:02:46.200" video="qanda-color" id="subtitle"]] +[[!template text="""bothering me and it actually was the case and that's how I got""" start="00:02:50.040" video="qanda-color" id="subtitle"]] +[[!template text="""to more into the color kind of journey and got too much into it""" start="00:02:54.040" video="qanda-color" id="subtitle"]] +[[!template text="""I guess. Right, and was it what eventually motivated you to""" start="00:02:59.360" video="qanda-color" id="subtitle"]] -
[[!template new="1" text="""What motivated you to learn Elisp and get into the Emacs core?""" start="00:03:00.535" video="qanda-color" id="subtitle"]]
[[!template text="""learn Elisp and to get into the Emacs core? Because it's""" start="00:03:00.535" video="qanda-color" id="subtitle"]] -[[!template text="""funny how you find plenty of people using Emacs in Org Mode""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""and then they find something that they take particular""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""issue with, for you it's the color, and then they just go all""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""in trying to pull the rope as far as they can to try to""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""understand as much as possible about what code is managing""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""this part of the application. Like for you it was color, for""" start="00:03:05.798" video="qanda-color" id="subtitle"]] -[[!template text="""me it was the org agenda, I desperately wanted to make Org""" start="00:03:22.786" video="qanda-color" id="subtitle"]] -[[!template text="""Agenda do something that it wasn't able to do. And five""" start="00:03:25.367" video="qanda-color" id="subtitle"]] -[[!template text="""years, well, actually, no, 10 years later, I find myself""" start="00:03:31.433" video="qanda-color" id="subtitle"]] -[[!template text="""hosting Emacs Cons. So, you never know just how far you're""" start="00:03:31.433" video="qanda-color" id="subtitle"]] -[[!template text="""going to be pulling this rope. So, it's really interesting""" start="00:03:36.598" video="qanda-color" id="subtitle"]] -[[!template text="""for me that my call was this. But back to the question, is this""" start="00:03:39.561" video="qanda-color" id="subtitle"]] -[[!template text="""what eventually motivated you to get into Elisp and the core""" start="00:03:42.464" video="qanda-color" id="subtitle"]] -[[!template text="""of Emacs? I think that the original journey to move to Emacs""" start="00:03:42.464" video="qanda-color" id="subtitle"]] -[[!template text="""was around keybindings that I got annoyed with with other""" start="00:03:49.798" video="qanda-color" id="subtitle"]] -[[!template text="""solutions, not just, you know, not speaking of Emacs""" start="00:03:49.798" video="qanda-color" id="subtitle"]] -[[!template text="""keybinding or anything, like anything in general. The main""" start="00:03:49.798" video="qanda-color" id="subtitle"]] -[[!template text="""reason was that I used Dovrak keyboard layout, and that""" start="00:04:02.870" video="qanda-color" id="subtitle"]] -[[!template text="""meant that all the C-c, C-v, C-p, whatever, It just is""" start="00:04:02.870" video="qanda-color" id="subtitle"]] -[[!template text="""all over the place. So I had to find something that could work""" start="00:04:10.257" video="qanda-color" id="subtitle"]] -[[!template text="""for me. And Emacs was a solution that allowed me to do""" start="00:04:11.577" video="qanda-color" id="subtitle"]] -[[!template text="""anything. And that's the kind of the journey that it""" start="00:04:14.898" video="qanda-color" id="subtitle"]] -[[!template text="""originally started. And from there, started tweaking org""" start="00:04:18.019" video="qanda-color" id="subtitle"]] -[[!template text="""mode and writing experience to be tuned to my liking. Color""" start="00:04:21.599" video="qanda-color" id="subtitle"]] -[[!template text="""was another thing that I thought, OK, maybe I could do it""" start="00:04:29.101" video="qanda-color" id="subtitle"]] -[[!template text="""easily with org mode. And when I started to use more of the""" start="00:04:29.101" video="qanda-color" id="subtitle"]] -[[!template text="""coding side of things on Emacs, I felt that, okay, that was""" start="00:04:34.262" video="qanda-color" id="subtitle"]] -[[!template text="""something I needed to solve. So Elisp was always kind of""" start="00:04:39.355" video="qanda-color" id="subtitle"]] -[[!template text="""just a toolkit that, you know, I knew that it was available. I""" start="00:04:41.877" video="qanda-color" id="subtitle"]] -[[!template text="""knew that it would be something that I want to be able to use.""" start="00:04:48.322" video="qanda-color" id="subtitle"]] -[[!template text="""So I think in a way color was a good segue to understand how I""" start="00:04:52.646" video="qanda-color" id="subtitle"]] -[[!template text="""can kind of work out more of a complex logic with the editor""" start="00:04:52.646" video="qanda-color" id="subtitle"]] -[[!template text="""without having to write JavaScript or things that I don't""" start="00:04:59.136" video="qanda-color" id="subtitle"]] -[[!template text="""particularly like. So yeah, I think the journey around the""" start="00:04:59.136" video="qanda-color" id="subtitle"]] -[[!template text="""functional languages, functional kind of programming was""" start="00:05:07.440" video="qanda-color" id="subtitle"]] -[[!template text="""always something that I was keen about. And yeah, the whole""" start="00:05:07.440" video="qanda-color" id="subtitle"]] -[[!template text="""journey kind of made sense for me. And then moving on to the""" start="00:05:13.943" video="qanda-color" id="subtitle"]] -[[!template text="""color was just one way to get more involved in. So I can""" start="00:05:16.984" video="qanda-color" id="subtitle"]] -[[!template text="""totally see that this journey kind of making to a little bit""" start="00:05:21.406" video="qanda-color" id="subtitle"]] -[[!template text="""different angle But yeah, we shall see how that really turns""" start="00:05:21.406" video="qanda-color" id="subtitle"]] -[[!template text="""out. But for now, I think I'm happy with the color setup. Now I""" start="00:05:27.669" video="qanda-color" id="subtitle"]] -[[!template text="""can really focus on the coding. Well, that's all good. And""" start="00:05:33.514" video="qanda-color" id="subtitle"]] -[[!template text="""I'm sure plenty of people listening to you now, you know,""" start="00:05:37.156" video="qanda-color" id="subtitle"]] -[[!template text="""find this relatable, how they eventually got into""" start="00:05:37.156" video="qanda-color" id="subtitle"]] -[[!template text="""programming. Like for you, you did say that you were a""" start="00:05:37.156" video="qanda-color" id="subtitle"]] -[[!template text="""software engineer now. But I found plenty of people,""" start="00:05:44.222" video="qanda-color" id="subtitle"]] -[[!template text="""especially doing workshops, that just started you know,""" start="00:05:48.705" video="qanda-color" id="subtitle"]] -[[!template text="""their software engineering journey just with Emacs and""" start="00:05:54.339" video="qanda-color" id="subtitle"]] -[[!template text="""they just realized they were doing something completely""" start="00:05:54.339" video="qanda-color" id="subtitle"]] -[[!template text="""different, like I was studying humanities. But then you""" start="00:05:54.339" video="qanda-color" id="subtitle"]] -[[!template text="""touch Emacs and you realize, yeah, this whole programming""" start="00:06:01.787" video="qanda-color" id="subtitle"]] -[[!template text="""shtick is actually pretty damn cool.""" start="00:06:01.787" video="qanda-color" id="subtitle"]] -[[!template text="""And then you find yourself again,""" start="00:06:07.280" video="qanda-color" id="subtitle"]] -[[!template text="""five to 10 years later, becoming a software""" start="00:06:09.400" video="qanda-color" id="subtitle"]] -[[!template text="""engineer. So yeah, that's all good.""" start="00:06:11.040" video="qanda-color" id="subtitle"]] -[[!template text="""So we do have a couple of""" start="00:06:12.920" video="qanda-color" id="subtitle"]] -[[!template text="""questions and I'd like to move into them so that I, I mean,""" start="00:06:14.520" video="qanda-color" id="subtitle"]] +
[[!template new="1" text="""What motivated you to learn Elisp and get into the Emacs core?""" start="00:03:04.040" video="qanda-color" id="subtitle"]]
[[!template text="""learn Elisp and to get into the Emacs core? Because it's""" start="00:03:04.040" video="qanda-color" id="subtitle"]] +[[!template text="""funny how you find plenty of people using Emacs in Org Mode""" start="00:03:07.000" video="qanda-color" id="subtitle"]] +[[!template text="""and then they find something that they take particular""" start="00:03:09.400" video="qanda-color" id="subtitle"]] +[[!template text="""issue with, for you it's the color, and then they just go all""" start="00:03:11.400" video="qanda-color" id="subtitle"]] +[[!template text="""in trying to pull the rope as far as they can to try to""" start="00:03:15.040" video="qanda-color" id="subtitle"]] +[[!template text="""understand as much as possible about what code is managing""" start="00:03:18.040" video="qanda-color" id="subtitle"]] +[[!template text="""this part of the application. Like for you it was color, for""" start="00:03:21.360" video="qanda-color" id="subtitle"]] +[[!template text="""me it was the org agenda, I desperately wanted to make Org""" start="00:03:23.880" video="qanda-color" id="subtitle"]] +[[!template text="""Agenda do something that it wasn't able to do. And five""" start="00:03:28.000" video="qanda-color" id="subtitle"]] +[[!template text="""years, well, actually, no, 10 years later, I find myself""" start="00:03:32.440" video="qanda-color" id="subtitle"]] +[[!template text="""hosting Emacs Cons. So, you never know just how far you're""" start="00:03:35.200" video="qanda-color" id="subtitle"]] +[[!template text="""going to be pulling this rope. So, it's really interesting""" start="00:03:38.200" video="qanda-color" id="subtitle"]] +[[!template text="""for me that my call was this. But back to the question, is this""" start="00:03:40.400" video="qanda-color" id="subtitle"]] +[[!template text="""what eventually motivated you to get into Elisp and the core""" start="00:03:44.680" video="qanda-color" id="subtitle"]] +[[!template text="""of Emacs? I think that the original journey to move to Emacs""" start="00:03:47.760" video="qanda-color" id="subtitle"]] +[[!template text="""was around keybindings that I got annoyed with with other""" start="00:03:53.440" video="qanda-color" id="subtitle"]] +[[!template text="""solutions, not just, you know, not speaking of Emacs""" start="00:03:56.960" video="qanda-color" id="subtitle"]] +[[!template text="""keybinding or anything, like anything in general. The main""" start="00:03:59.840" video="qanda-color" id="subtitle"]] +[[!template text="""reason was that I used Dovrak keyboard layout, and that""" start="00:04:02.880" video="qanda-color" id="subtitle"]] +[[!template text="""meant that all the C-c, C-v, C-p, whatever, It just is""" start="00:04:07.520" video="qanda-color" id="subtitle"]] +[[!template text="""all over the place. So I had to find something that could work""" start="00:04:10.800" video="qanda-color" id="subtitle"]] +[[!template text="""for me. And Emacs was a solution that allowed me to do""" start="00:04:13.920" video="qanda-color" id="subtitle"]] +[[!template text="""anything. And that's the kind of the journey that it""" start="00:04:17.040" video="qanda-color" id="subtitle"]] +[[!template text="""originally started. And from there, started tweaking org""" start="00:04:20.480" video="qanda-color" id="subtitle"]] +[[!template text="""mode and writing experience to be tuned to my liking. Color""" start="00:04:24.040" video="qanda-color" id="subtitle"]] +[[!template text="""was another thing that I thought, OK, maybe I could do it""" start="00:04:28.440" video="qanda-color" id="subtitle"]] +[[!template text="""easily with org mode. And when I started to use more of the""" start="00:04:32.560" video="qanda-color" id="subtitle"]] +[[!template text="""coding side of things on Emacs, I felt that, okay, that was""" start="00:04:36.240" video="qanda-color" id="subtitle"]] +[[!template text="""something I needed to solve. So Elisp was always kind of""" start="00:04:40.800" video="qanda-color" id="subtitle"]] +[[!template text="""just a toolkit that, you know, I knew that it was available. I""" start="00:04:45.160" video="qanda-color" id="subtitle"]] +[[!template text="""knew that it would be something that I want to be able to use.""" start="00:04:48.440" video="qanda-color" id="subtitle"]] +[[!template text="""So I think in a way color was a good segue to understand how I""" start="00:04:52.200" video="qanda-color" id="subtitle"]] +[[!template text="""can kind of work out more of a complex logic with the editor""" start="00:04:57.160" video="qanda-color" id="subtitle"]] +[[!template text="""without having to write JavaScript or things that I don't""" start="00:05:03.360" video="qanda-color" id="subtitle"]] +[[!template text="""particularly like. So yeah, I think the journey around the""" start="00:05:06.360" video="qanda-color" id="subtitle"]] +[[!template text="""functional languages, functional kind of programming was""" start="00:05:09.400" video="qanda-color" id="subtitle"]] +[[!template text="""always something that I was keen about. And yeah, the whole""" start="00:05:11.880" video="qanda-color" id="subtitle"]] +[[!template text="""journey kind of made sense for me. And then moving on to the""" start="00:05:15.440" video="qanda-color" id="subtitle"]] +[[!template text="""color was just one way to get more involved in. So I can""" start="00:05:18.480" video="qanda-color" id="subtitle"]] +[[!template text="""totally see that this journey kind of making to a little bit""" start="00:05:22.000" video="qanda-color" id="subtitle"]] +[[!template text="""different angle But yeah, we shall see how that really turns""" start="00:05:26.280" video="qanda-color" id="subtitle"]] +[[!template text="""out. But for now, I think I'm happy with the color setup. Now I""" start="00:05:30.760" video="qanda-color" id="subtitle"]] +[[!template text="""can really focus on the coding. Well, that's all good. And""" start="00:05:33.800" video="qanda-color" id="subtitle"]] +[[!template text="""I'm sure plenty of people listening to you now, you know,""" start="00:05:37.600" video="qanda-color" id="subtitle"]] +[[!template text="""find this relatable, how they eventually got into""" start="00:05:40.840" video="qanda-color" id="subtitle"]] +[[!template text="""programming. Like for you, you did say that you were a""" start="00:05:43.640" video="qanda-color" id="subtitle"]] +[[!template text="""software engineer now. But I found plenty of people,""" start="00:05:46.880" video="qanda-color" id="subtitle"]] +[[!template text="""especially doing workshops, that just started you know,""" start="00:05:50.520" video="qanda-color" id="subtitle"]] +[[!template text="""their software engineering journey just with Emacs and""" start="00:05:54.680" video="qanda-color" id="subtitle"]] +[[!template text="""they just realized they were doing something completely""" start="00:05:57.640" video="qanda-color" id="subtitle"]] +[[!template text="""different, like I was studying humanities. But then you""" start="00:05:59.240" video="qanda-color" id="subtitle"]] +[[!template text="""touch Emacs and you realize, yeah, this whole programming""" start="00:06:02.000" video="qanda-color" id="subtitle"]] +[[!template text="""shtick is actually pretty damn cool.""" start="00:06:05.080" video="qanda-color" id="subtitle"]] +[[!template text="""And then you find yourself again,""" start="00:06:06.680" video="qanda-color" id="subtitle"]] +[[!template text="""five to 10 years later, becoming a software""" start="00:06:09.080" video="qanda-color" id="subtitle"]] +[[!template text="""engineer. So yeah, that's all good.""" start="00:06:11.000" video="qanda-color" id="subtitle"]] +[[!template text="""So we do have a couple of""" start="00:06:13.000" video="qanda-color" id="subtitle"]] +[[!template text="""questions and I'd like to move into them so that I, I mean,""" start="00:06:13.920" video="qanda-color" id="subtitle"]] [[!template text="""people have questions and for me it's okay for me to chat with""" start="00:06:18.440" video="qanda-color" id="subtitle"]] -[[!template text="""you but obviously it's better if people ask you the question""" start="00:06:22.440" video="qanda-color" id="subtitle"]] +[[!template text="""you but obviously it's better if people ask you the question""" start="00:06:22.400" video="qanda-color" id="subtitle"]] [[!template text="""themselves. And again, if you want to ask questions to Ryota""" start="00:06:25.120" video="qanda-color" id="subtitle"]] -[[!template text="""directly, feel free to join us on BBB and whenever we're done""" start="00:06:27.680" video="qanda-color" id="subtitle"]] -[[!template text="""with the questions on the pad, I'm more than happy""" start="00:06:31.080" video="qanda-color" id="subtitle"]] +[[!template text="""directly, feel free to join us on BBB and whenever we're done""" start="00:06:27.640" video="qanda-color" id="subtitle"]] +[[!template text="""with the questions on the pad, I'm more than happy""" start="00:06:31.040" video="qanda-color" id="subtitle"]] [[!template text="""to let you ask your questions live.""" start="00:06:33.520" video="qanda-color" id="subtitle"]] -
[[!template new="1" text="""Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps?""" start="00:06:35.982" video="qanda-color" id="subtitle"]]
[[!template text="""All right, so starting with the first question,""" start="00:06:35.982" video="qanda-color" id="subtitle"]] -[[!template text="""is there any intention to create a library""" start="00:06:37.903" video="qanda-color" id="subtitle"]] -[[!template text="""for working with more experimental color spaces, pulling""" start="00:06:37.903" video="qanda-color" id="subtitle"]] -[[!template text="""code out of Hasliberg for this purpose, perhaps? Although I""" start="00:06:35.982" video="qanda-color" id="subtitle"]] -[[!template text="""do not know. Hasliberg, you might? Yeah, Hasliberg. And to""" start="00:06:45.329" video="qanda-color" id="subtitle"]] -[[!template text="""answer the question, started the journey just for myself""" start="00:06:49.692" video="qanda-color" id="subtitle"]] -[[!template text="""and I didn't think that it would be actually useful for other""" start="00:06:52.859" video="qanda-color" id="subtitle"]] -[[!template text="""use cases and this conference talk just came about kind of""" start="00:06:52.859" video="qanda-color" id="subtitle"]] -[[!template text="""out of sheer luck really. So the idea I think I can definitely""" start="00:06:52.859" video="qanda-color" id="subtitle"]] -[[!template text="""work it out and I don't think there will be too, the original""" start="00:07:04.771" video="qanda-color" id="subtitle"]] -[[!template text="""code that I started with was I had to use some color space and I""" start="00:07:04.771" video="qanda-color" id="subtitle"]] -[[!template text="""started with sRGB and then went to HSL and then went to LCH. So""" start="00:07:15.931" video="qanda-color" id="subtitle"]] -[[!template text="""I think there has been quite a bit that I learned from it. At""" start="00:07:21.996" video="qanda-color" id="subtitle"]] -[[!template text="""the same time, I may be tempted to actually maybe perhaps""" start="00:07:25.458" video="qanda-color" id="subtitle"]] -[[!template text="""contribute back to ct.el rather than creating my own. I""" start="00:07:25.458" video="qanda-color" id="subtitle"]] -[[!template text="""think that would make more sense perhaps.""" start="00:07:34.105" video="qanda-color" id="subtitle"]] -[[!template text="""But for my own kind of taste that I thought""" start="00:07:36.607" video="qanda-color" id="subtitle"]] -[[!template text="""that it would be something I can work out in my theme,""" start="00:07:39.549" video="qanda-color" id="subtitle"]] -[[!template text="""but I don't have any I think, you know, making a""" start="00:07:42.892" video="qanda-color" id="subtitle"]] -[[!template text="""library is definitely something that I can think about, but""" start="00:07:45.813" video="qanda-color" id="subtitle"]] -[[!template text="""perhaps maybe making it too many packages isn't exactly""" start="00:07:45.813" video="qanda-color" id="subtitle"]] -[[!template text="""what I want. But for my own use case, I think I just wanted to""" start="00:07:45.813" video="qanda-color" id="subtitle"]] -[[!template text="""have something that just didn't have any external""" start="00:07:55.175" video="qanda-color" id="subtitle"]] -[[!template text="""dependency so that I can use the vanilla Emacs with my""" start="00:07:55.175" video="qanda-color" id="subtitle"]] -[[!template text="""colors. I think that's how it started, but I'm definitely up""" start="00:07:55.175" video="qanda-color" id="subtitle"]] -[[!template text="""for it if there is interest about it. Yeah, well, thank you""" start="00:08:06.757" video="qanda-color" id="subtitle"]] -[[!template text="""for this. It's always good to contribute.""" start="00:08:12.622" video="qanda-color" id="subtitle"]] -[[!template text="""I'm tempted to say""" start="00:08:16.040" video="qanda-color" id="subtitle"]] +
[[!template new="1" text="""Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps?""" start="00:06:35.320" video="qanda-color" id="subtitle"]]
[[!template text="""All right, so starting with the first question,""" start="00:06:35.320" video="qanda-color" id="subtitle"]] +[[!template text="""is there any intention to create a library""" start="00:06:37.800" video="qanda-color" id="subtitle"]] +[[!template text="""for working with more experimental color spaces, pulling""" start="00:06:40.000" video="qanda-color" id="subtitle"]] +[[!template text="""code out of Hasliberg for this purpose, perhaps? Although I""" start="00:06:42.560" video="qanda-color" id="subtitle"]] +[[!template text="""do not know. Hasliberg, you might? Yeah, Hasliberg. And to""" start="00:06:45.680" video="qanda-color" id="subtitle"]] +[[!template text="""answer the question, started the journey just for myself""" start="00:06:50.480" video="qanda-color" id="subtitle"]] +[[!template text="""and I didn't think that it would be actually useful for other""" start="00:06:55.120" video="qanda-color" id="subtitle"]] +[[!template text="""use cases and this conference talk just came about kind of""" start="00:06:58.480" video="qanda-color" id="subtitle"]] +[[!template text="""out of sheer luck really. So the idea I think I can definitely""" start="00:07:03.320" video="qanda-color" id="subtitle"]] +[[!template text="""work it out and I don't think there will be too, the original""" start="00:07:08.080" video="qanda-color" id="subtitle"]] +[[!template text="""code that I started with was I had to use some color space and I""" start="00:07:12.200" video="qanda-color" id="subtitle"]] +[[!template text="""started with sRGB and then went to HSL and then went to LCH. So""" start="00:07:17.640" video="qanda-color" id="subtitle"]] +[[!template text="""I think there has been quite a bit that I learned from it. At""" start="00:07:22.480" video="qanda-color" id="subtitle"]] +[[!template text="""the same time, I may be tempted to actually maybe perhaps""" start="00:07:25.480" video="qanda-color" id="subtitle"]] +[[!template text="""contribute back to ct.el rather than creating my own. I""" start="00:07:30.000" video="qanda-color" id="subtitle"]] +[[!template text="""think that would make more sense perhaps.""" start="00:07:34.160" video="qanda-color" id="subtitle"]] +[[!template text="""But for my own kind of taste that I thought""" start="00:07:36.280" video="qanda-color" id="subtitle"]] +[[!template text="""that it would be something I can work out in my theme,""" start="00:07:39.480" video="qanda-color" id="subtitle"]] +[[!template text="""but I don't have any I think, you know, making a""" start="00:07:42.840" video="qanda-color" id="subtitle"]] +[[!template text="""library is definitely something that I can think about, but""" start="00:07:46.880" video="qanda-color" id="subtitle"]] +[[!template text="""perhaps maybe making it too many packages isn't exactly""" start="00:07:50.000" video="qanda-color" id="subtitle"]] +[[!template text="""what I want. But for my own use case, I think I just wanted to""" start="00:07:53.680" video="qanda-color" id="subtitle"]] +[[!template text="""have something that just didn't have any external""" start="00:07:57.320" video="qanda-color" id="subtitle"]] +[[!template text="""dependency so that I can use the vanilla Emacs with my""" start="00:07:59.920" video="qanda-color" id="subtitle"]] +[[!template text="""colors. I think that's how it started, but I'm definitely up""" start="00:08:04.120" video="qanda-color" id="subtitle"]] +[[!template text="""for it if there is interest about it. Yeah, well, thank you""" start="00:08:09.640" video="qanda-color" id="subtitle"]] +[[!template text="""for this. It's always good to contribute.""" start="00:08:13.720" video="qanda-color" id="subtitle"]] +[[!template text="""I'm tempted to say""" start="00:08:15.280" video="qanda-color" id="subtitle"]] [[!template text="""that's how they get you. You know, you do something really""" start="00:08:16.400" video="qanda-color" id="subtitle"]] -[[!template text="""cool and you share it with people and they have the, you know,""" start="00:08:18.680" video="qanda-color" id="subtitle"]] -[[!template text="""they just ask you, oh, do you have your code online? And you""" start="00:08:24.800" video="qanda-color" id="subtitle"]] -[[!template text="""realize, no, I haven't pushed it. And then they start""" start="00:08:27.166" video="qanda-color" id="subtitle"]] -[[!template text="""pressing you on. well, you need to do this, this is amazing""" start="00:08:28.707" video="qanda-color" id="subtitle"]] -[[!template text="""and you need to share it. You know, I had plenty of people ask""" start="00:08:30.287" video="qanda-color" id="subtitle"]] -[[!template text="""me to share my dot files when I was tackling the org agenda""" start="00:08:33.849" video="qanda-color" id="subtitle"]] -[[!template text="""issue that I mentioned earlier. And yeah, eventually when""" start="00:08:33.849" video="qanda-color" id="subtitle"]] -[[!template text="""you get to publishing your stuff, you also feel great""" start="00:08:42.575" video="qanda-color" id="subtitle"]] -[[!template text="""because you're putting a little bit of your intelligence""" start="00:08:42.575" video="qanda-color" id="subtitle"]] -[[!template text="""into the world and it can be the start of the journey for""" start="00:08:42.575" video="qanda-color" id="subtitle"]] -[[!template text="""someone else. You know, maybe someone will find your""" start="00:08:42.575" video="qanda-color" id="subtitle"]] -[[!template text="""library at some point and realize, yeah, I wanted to do""" start="00:08:54.283" video="qanda-color" id="subtitle"]] -[[!template text="""something slightly differently. and then they either""" start="00:08:54.283" video="qanda-color" id="subtitle"]] -[[!template text="""contribute to a library or they make their own but it's a""" start="00:09:00.387" video="qanda-color" id="subtitle"]] -[[!template text="""complete journey that starts with just people taking the""" start="00:09:00.387" video="qanda-color" id="subtitle"]] -[[!template text="""time to publish the content of the brain basically. Yeah,""" start="00:09:00.387" video="qanda-color" id="subtitle"]] -[[!template text="""that's the power of open source now. It's just how we really""" start="00:09:11.894" video="qanda-color" id="subtitle"]] -[[!template text="""appreciate the open source culture being cultivated""" start="00:09:13.654" video="qanda-color" id="subtitle"]] -[[!template text="""throughout so many years. And yeah, this is something that""" start="00:09:13.654" video="qanda-color" id="subtitle"]] -[[!template text="""I'm definitely keen about. So yeah, open for suggestions.""" start="00:09:21.736" video="qanda-color" id="subtitle"]] -[[!template text="""And exactly, that's how I started with the journey. And""" start="00:09:26.618" video="qanda-color" id="subtitle"]] -[[!template text="""yeah, while this is very experimental and very personal,""" start="00:09:29.760" video="qanda-color" id="subtitle"]] -[[!template text="""yeah, I'm not, you know, tied down to one particular way""" start="00:09:33.560" video="qanda-color" id="subtitle"]] -[[!template text="""only. So yeah we'll be open to suggestions like this one""" start="00:09:38.240" video="qanda-color" id="subtitle"]] -[[!template text="""which I would definitely think about. Yeah that's amazing""" start="00:09:41.680" video="qanda-color" id="subtitle"]] -[[!template text="""and just to be clear you know this is not a there's no""" start="00:09:44.840" video="qanda-color" id="subtitle"]] -[[!template text="""incentive one. I'm not pushing you to publish your library.""" start="00:09:46.880" video="qanda-color" id="subtitle"]] -[[!template text="""You know it was very personal for you and at the end if you""" start="00:09:51.070" video="qanda-color" id="subtitle"]] -[[!template text="""believe it might be useful for others it's a nice thing to""" start="00:09:51.070" video="qanda-color" id="subtitle"]] -[[!template text="""eventually think about publishing it. But just the fact""" start="00:09:51.070" video="qanda-color" id="subtitle"]] -[[!template text="""that you showed up at EmacsConf... Sorry, I'm""" start="00:09:58.056" video="qanda-color" id="subtitle"]] -[[!template text="""starting to lose my voice on the morning""" start="00:10:01.278" video="qanda-color" id="subtitle"]] -[[!template text="""of the first day. That's""" start="00:10:02.699" video="qanda-color" id="subtitle"]] -[[!template text="""not boding well for the two next days. I mean, just one day.""" start="00:10:03.520" video="qanda-color" id="subtitle"]] -[[!template text="""But just the""" start="00:10:08.560" video="qanda-color" id="subtitle"]] -[[!template text="""fact that you're showing up at EmacsConf and sharing about""" start="00:10:10.080" video="qanda-color" id="subtitle"]] -[[!template text="""all of this, the process, how you got to it eventually, it's""" start="00:10:13.280" video="qanda-color" id="subtitle"]] -[[!template text="""also a part of sharing. And I think it's also amazing in its""" start="00:10:17.120" video="qanda-color" id="subtitle"]] -[[!template text="""own way. Absolutely. Okay, I'm going to try to read the next""" start="00:10:19.440" video="qanda-color" id="subtitle"]] +[[!template text="""cool and you share it with people and they have the, you know,""" start="00:08:18.280" video="qanda-color" id="subtitle"]] +[[!template text="""they just ask you, oh, do you have your code online? And you""" start="00:08:23.640" video="qanda-color" id="subtitle"]] +[[!template text="""realize, no, I haven't pushed it. And then they start""" start="00:08:27.240" video="qanda-color" id="subtitle"]] +[[!template text="""pressing you on. well, you need to do this, this is amazing""" start="00:08:29.400" video="qanda-color" id="subtitle"]] +[[!template text="""and you need to share it. You know, I had plenty of people ask""" start="00:08:32.360" video="qanda-color" id="subtitle"]] +[[!template text="""me to share my dot files when I was tackling the org agenda""" start="00:08:35.880" video="qanda-color" id="subtitle"]] +[[!template text="""issue that I mentioned earlier. And yeah, eventually when""" start="00:08:40.520" video="qanda-color" id="subtitle"]] +[[!template text="""you get to publishing your stuff, you also feel great""" start="00:08:44.040" video="qanda-color" id="subtitle"]] +[[!template text="""because you're putting a little bit of your intelligence""" start="00:08:47.480" video="qanda-color" id="subtitle"]] +[[!template text="""into the world and it can be the start of the journey for""" start="00:08:50.280" video="qanda-color" id="subtitle"]] +[[!template text="""someone else. You know, maybe someone will find your""" start="00:08:53.680" video="qanda-color" id="subtitle"]] +[[!template text="""library at some point and realize, yeah, I wanted to do""" start="00:08:56.240" video="qanda-color" id="subtitle"]] +[[!template text="""something slightly differently. and then they either""" start="00:08:58.680" video="qanda-color" id="subtitle"]] +[[!template text="""contribute to a library or they make their own but it's a""" start="00:09:01.240" video="qanda-color" id="subtitle"]] +[[!template text="""complete journey that starts with just people taking the""" start="00:09:04.440" video="qanda-color" id="subtitle"]] +[[!template text="""time to publish the content of the brain basically. Yeah,""" start="00:09:07.360" video="qanda-color" id="subtitle"]] +[[!template text="""that's the power of open source now. It's just how we really""" start="00:09:12.040" video="qanda-color" id="subtitle"]] +[[!template text="""appreciate the open source culture being cultivated""" start="00:09:15.520" video="qanda-color" id="subtitle"]] +[[!template text="""throughout so many years. And yeah, this is something that""" start="00:09:19.120" video="qanda-color" id="subtitle"]] +[[!template text="""I'm definitely keen about. So yeah, open for suggestions.""" start="00:09:23.160" video="qanda-color" id="subtitle"]] +[[!template text="""And exactly, that's how I started with the journey. And""" start="00:09:27.000" video="qanda-color" id="subtitle"]] +[[!template text="""yeah, while this is very experimental and very personal,""" start="00:09:30.080" video="qanda-color" id="subtitle"]] +[[!template text="""yeah, I'm not, you know, tied down to one particular way""" start="00:09:33.520" video="qanda-color" id="subtitle"]] +[[!template text="""only. So yeah we'll be open to suggestions like this one""" start="00:09:38.200" video="qanda-color" id="subtitle"]] +[[!template text="""which I would definitely think about. Yeah that's amazing""" start="00:09:41.400" video="qanda-color" id="subtitle"]] +[[!template text="""and just to be clear you know this is not a there's no""" start="00:09:44.720" video="qanda-color" id="subtitle"]] +[[!template text="""incentive one. I'm not pushing you to publish your library.""" start="00:09:47.000" video="qanda-color" id="subtitle"]] +[[!template text="""You know it was very personal for you and at the end if you""" start="00:09:50.640" video="qanda-color" id="subtitle"]] +[[!template text="""believe it might be useful for others it's a nice thing to""" start="00:09:53.800" video="qanda-color" id="subtitle"]] +[[!template text="""eventually think about publishing it. But just the fact""" start="00:09:56.200" video="qanda-color" id="subtitle"]] +[[!template text="""that you showed up at EmacsConf... Sorry, I'm""" start="00:09:58.800" video="qanda-color" id="subtitle"]] +[[!template text="""starting to lose my voice on the morning""" start="00:10:01.440" video="qanda-color" id="subtitle"]] +[[!template text="""of the first day. That's""" start="00:10:02.640" video="qanda-color" id="subtitle"]] +[[!template text="""not boding well for the two next days. I mean, just one day.""" start="00:10:03.840" video="qanda-color" id="subtitle"]] +[[!template text="""But just the""" start="00:10:07.640" video="qanda-color" id="subtitle"]] +[[!template text="""fact that you're showing up at EmacsConf and sharing about""" start="00:10:09.160" video="qanda-color" id="subtitle"]] +[[!template text="""all of this, the process, how you got to it eventually, it's""" start="00:10:13.200" video="qanda-color" id="subtitle"]] +[[!template text="""also a part of sharing. And I think it's also amazing in its""" start="00:10:17.040" video="qanda-color" id="subtitle"]] +[[!template text="""own way. Absolutely. Okay, I'm going to try to read the next""" start="00:10:19.640" video="qanda-color" id="subtitle"]] [[!template text="""question and then try to cough a little bit. So can we have...""" start="00:10:26.040" video="qanda-color" id="subtitle"]] -[[!template text="""Oh, sorry, Bala. Sorry. I was the one who asked the question.""" start="00:10:31.720" video="qanda-color" id="subtitle"]] -[[!template text="""I thought I could ask it live here rather than... Thank you.""" start="00:10:36.920" video="qanda-color" id="subtitle"]] -[[!template text="""I'll go cough a little bit. So here I am. Thanks, Ryota, for""" start="00:10:40.188" video="qanda-color" id="subtitle"]] -[[!template text="""the nice talk. This is great. I loved it. Your attention to""" start="00:10:45.050" video="qanda-color" id="subtitle"]] -[[!template text="""detail was awesome.""" start="00:10:49.531" video="qanda-color" id="subtitle"]] +[[!template text="""Oh, sorry, Bala. Sorry. I was the one who asked the question.""" start="00:10:31.640" video="qanda-color" id="subtitle"]] +[[!template text="""I thought I could ask it live here rather than... Thank you.""" start="00:10:36.760" video="qanda-color" id="subtitle"]] +[[!template text="""I'll go cough a little bit. So here I am. Thanks, Ryota, for""" start="00:10:40.280" video="qanda-color" id="subtitle"]] +[[!template text="""the nice talk. This is great. I loved it. Your attention to""" start="00:10:46.040" video="qanda-color" id="subtitle"]] +[[!template text="""detail was awesome.""" start="00:10:50.520" video="qanda-color" id="subtitle"]] -
[[!template new="1" text="""Q: Can we have a dark as well as light theme variations made from your theme?""" start="00:10:51.880" video="qanda-color" id="subtitle"]]
[[!template text="""So I was just looking at the code and I was""" start="00:10:51.880" video="qanda-color" id="subtitle"]] -[[!template text="""wondering, do you have a dark and a light theme variation""" start="00:10:55.080" video="qanda-color" id="subtitle"]] -[[!template text="""which can be made from your theme? Or do you have to customize""" start="00:10:58.840" video="qanda-color" id="subtitle"]] -[[!template text="""it every time? That was my question. And thanks for that.""" start="00:11:02.480" video="qanda-color" id="subtitle"]] -[[!template text="""Thank you very much. I appreciate your feedback and""" start="00:11:05.520" video="qanda-color" id="subtitle"]] -[[!template text="""questions. So to answer the question, the short answer is""" start="00:11:10.240" video="qanda-color" id="subtitle"]] -[[!template text="""that I do have both dark and light themes with some sorts of""" start="00:11:15.080" video="qanda-color" id="subtitle"]] -[[!template text="""standard colors that I personally liked. And there were a""" start="00:11:18.640" video="qanda-color" id="subtitle"]] +
[[!template new="1" text="""Q: Can we have a dark as well as light theme variations made from your theme?""" start="00:10:51.520" video="qanda-color" id="subtitle"]]
[[!template text="""So I was just looking at the code and I was""" start="00:10:51.520" video="qanda-color" id="subtitle"]] +[[!template text="""wondering, do you have a dark and a light theme variation""" start="00:10:54.960" video="qanda-color" id="subtitle"]] +[[!template text="""which can be made from your theme? Or do you have to customize""" start="00:10:58.760" video="qanda-color" id="subtitle"]] +[[!template text="""it every time? That was my question. And thanks for that.""" start="00:11:02.600" video="qanda-color" id="subtitle"]] +[[!template text="""Thank you very much. I appreciate your feedback and""" start="00:11:06.200" video="qanda-color" id="subtitle"]] +[[!template text="""questions. So to answer the question, the short answer is""" start="00:11:09.680" video="qanda-color" id="subtitle"]] +[[!template text="""that I do have both dark and light themes with some sorts of""" start="00:11:15.040" video="qanda-color" id="subtitle"]] +[[!template text="""standard colors that I personally liked. And there were a""" start="00:11:18.440" video="qanda-color" id="subtitle"]] [[!template text="""few things that I showed in the demo. where I showed, I think,""" start="00:11:22.200" video="qanda-color" id="subtitle"]] -[[!template text="""three different dark theme colors. So light theme is""" start="00:11:26.720" video="qanda-color" id="subtitle"]] -[[!template text="""definitely something that I can do.""" start="00:11:30.040" video="qanda-color" id="subtitle"]] -[[!template text="""And the idea around Hasliberg theme""" start="00:11:31.800" video="qanda-color" id="subtitle"]] -[[!template text="""and just my theming in general was that""" start="00:11:33.880" video="qanda-color" id="subtitle"]] -[[!template text="""when I feel like I want to work in dark theme and when I want to""" start="00:11:36.360" video="qanda-color" id="subtitle"]] -[[!template text="""work in the standard way, I would just use the standard color.""" start="00:11:39.680" video="qanda-color" id="subtitle"]] -[[!template text="""But when I feel like maybe it's just so cold that I want""" start="00:11:42.480" video="qanda-color" id="subtitle"]] -[[!template text="""to have a bit of a warm colors near me, I would use the orange""" start="00:11:44.960" video="qanda-color" id="subtitle"]] -[[!template text="""theme, without changing too much of the kind of general""" start="00:11:49.400" video="qanda-color" id="subtitle"]] -[[!template text="""feeling and experience. So that can be said for the light""" start="00:11:52.360" video="qanda-color" id="subtitle"]] -[[!template text="""theme as well. So there is something and the kind of""" start="00:11:55.680" video="qanda-color" id="subtitle"]] +[[!template text="""three different dark theme colors. So light theme is""" start="00:11:26.680" video="qanda-color" id="subtitle"]] +[[!template text="""definitely something that I can do.""" start="00:11:30.000" video="qanda-color" id="subtitle"]] +[[!template text="""And the idea around Hasliberg theme""" start="00:11:31.560" video="qanda-color" id="subtitle"]] +[[!template text="""and just my theming in general was that""" start="00:11:33.760" video="qanda-color" id="subtitle"]] +[[!template text="""when I feel like I want to work in dark theme and when I want to""" start="00:11:36.280" video="qanda-color" id="subtitle"]] +[[!template text="""work in the standard way, I would just use the standard color.""" start="00:11:39.600" video="qanda-color" id="subtitle"]] +[[!template text="""But when I feel like maybe it's just so cold that I want""" start="00:11:42.160" video="qanda-color" id="subtitle"]] +[[!template text="""to have a bit of a warm colors near me, I would use the orange""" start="00:11:44.920" video="qanda-color" id="subtitle"]] +[[!template text="""theme, without changing too much of the kind of general""" start="00:11:48.520" video="qanda-color" id="subtitle"]] +[[!template text="""feeling and experience. So that can be said for the light""" start="00:11:52.280" video="qanda-color" id="subtitle"]] +[[!template text="""theme as well. So there is something and the kind of""" start="00:11:55.640" video="qanda-color" id="subtitle"]] [[!template text="""customization isn't that difficult to extend. So I do have""" start="00:11:58.960" video="qanda-color" id="subtitle"]] -[[!template text="""both dark and light, but primarily I'm just looking at the""" start="00:12:04.920" video="qanda-color" id="subtitle"]] -[[!template text="""dark theme as my main driver. But yeah, they are both""" start="00:12:09.080" video="qanda-color" id="subtitle"]] -[[!template text="""available. Great. Thank you so much. I will definitely try""" start="00:12:10.240" video="qanda-color" id="subtitle"]] -[[!template text="""your theme out. I'm definitely on the lookout for a nice,""" start="00:12:18.208" video="qanda-color" id="subtitle"]] -[[!template text="""friendly theme. Thank you very much. As I said, this is a""" start="00:12:19.205" video="qanda-color" id="subtitle"]] -[[!template text="""personal theme. I'm not sure if it really fits everyone's""" start="00:12:25.388" video="qanda-color" id="subtitle"]] -[[!template text="""need, but it is one inspiration that I hope that can lead to""" start="00:12:29.089" video="qanda-color" id="subtitle"]] -[[!template text="""another nice theming that could work for someone""" start="00:12:29.089" video="qanda-color" id="subtitle"]] -[[!template text="""specifically for some use cases. I don't have to solve""" start="00:12:29.089" video="qanda-color" id="subtitle"]] -[[!template text="""everyone's problem. Yeah, and I mean, it was sufficient to""" start="00:12:42.996" video="qanda-color" id="subtitle"]] -[[!template text="""be inspirational to people. I mean, just Bala just""" start="00:12:46.553" video="qanda-color" id="subtitle"]] -[[!template text="""mentioned it right now, but I'm sure plenty of people who""" start="00:12:49.755" video="qanda-color" id="subtitle"]] -[[!template text="""watched live, but also people will be watching in the""" start="00:12:49.755" video="qanda-color" id="subtitle"]] -[[!template text="""future, will have the interest to speak by what you've done.""" start="00:12:49.755" video="qanda-color" id="subtitle"]] -[[!template text="""So thank you again so much for this. Yep. All right, well, I""" start="00:12:58.699" video="qanda-color" id="subtitle"]] -[[!template text="""don't see any further questions. So I suggest we move""" start="00:13:04.102" video="qanda-color" id="subtitle"]] -[[!template text="""towards closure. Ryota, do you have any last words? No, I""" start="00:13:07.083" video="qanda-color" id="subtitle"]] -[[!template text="""don't. So yeah, thank you very much for attending. And it was""" start="00:13:13.775" video="qanda-color" id="subtitle"]] -[[!template text="""great fun putting this together. And I really didn't think""" start="00:13:16.577" video="qanda-color" id="subtitle"]] -[[!template text="""that I would be talking about my personal colors and""" start="00:13:19.299" video="qanda-color" id="subtitle"]] -[[!template text="""personal favorites, like orange being my favorite color.""" start="00:13:19.299" video="qanda-color" id="subtitle"]] -[[!template text="""This wouldn't be something that I would say out in any""" start="00:13:27.845" video="qanda-color" id="subtitle"]] -[[!template text="""conference, to be honest. But it just came out to be. And""" start="00:13:27.845" video="qanda-color" id="subtitle"]] -[[!template text="""happy that I had a chance. So thank you very much for giving me""" start="00:13:33.890" video="qanda-color" id="subtitle"]] -[[!template text="""the opportunity to talk. in this amazing conference and""" start="00:13:35.651" video="qanda-color" id="subtitle"]] -[[!template text="""yeah I can't just wait to check out other talks which you know""" start="00:13:39.574" video="qanda-color" id="subtitle"]] -[[!template text="""I know that there isn't you know other talks that are""" start="00:13:39.574" video="qanda-color" id="subtitle"]] -[[!template text="""happening right now I was actually wanted to to join them and""" start="00:13:39.574" video="qanda-color" id="subtitle"]] -[[!template text="""check check that out so I will probably do that right now.""" start="00:13:39.574" video="qanda-color" id="subtitle"]] -[[!template text="""Well, sure. Well, I won't hold you any longer then. Thank""" start="00:13:53.419" video="qanda-color" id="subtitle"]] -[[!template text="""you. For me, it was just amazing to, you know, generally when""" start="00:13:56.401" video="qanda-color" id="subtitle"]] -[[!template text="""you ask someone what their favorite color, you know, they""" start="00:13:57.682" video="qanda-color" id="subtitle"]] -[[!template text="""just tell you orange or blue or whatever. They don't go then""" start="00:13:57.682" video="qanda-color" id="subtitle"]] -[[!template text="""to chat about 20 minutes about their favorite color and how""" start="00:14:03.586" video="qanda-color" id="subtitle"]] -[[!template text="""they tuned their entire editor to work exactly around their""" start="00:14:03.586" video="qanda-color" id="subtitle"]] -[[!template text="""favorite colors. So it was inspiring. And I also want to try""" start="00:14:03.586" video="qanda-color" id="subtitle"]] -[[!template text="""it out, frankly, because my theme has been utterly bad for""" start="00:14:12.912" video="qanda-color" id="subtitle"]] -[[!template text="""the last five years and I need some change into my life. All""" start="00:14:12.912" video="qanda-color" id="subtitle"]] -[[!template text="""right. Thank you so much for your time. Thank you very much,""" start="00:14:21.497" video="qanda-color" id="subtitle"]] -[[!template text="""everyone. Cheers. Bye-bye.""" start="00:14:23.629" video="qanda-color" id="subtitle"]] +[[!template text="""both dark and light, but primarily I'm just looking at the""" start="00:12:04.840" video="qanda-color" id="subtitle"]] +[[!template text="""dark theme as my main driver. But yeah, they are both""" start="00:12:09.360" video="qanda-color" id="subtitle"]] +[[!template text="""available. Great. Thank you so much. I will definitely try""" start="00:12:12.840" video="qanda-color" id="subtitle"]] +[[!template text="""your theme out. I'm definitely on the lookout for a nice,""" start="00:12:18.240" video="qanda-color" id="subtitle"]] +[[!template text="""friendly theme. Thank you very much. As I said, this is a""" start="00:12:21.720" video="qanda-color" id="subtitle"]] +[[!template text="""personal theme. I'm not sure if it really fits everyone's""" start="00:12:26.120" video="qanda-color" id="subtitle"]] +[[!template text="""need, but it is one inspiration that I hope that can lead to""" start="00:12:31.280" video="qanda-color" id="subtitle"]] +[[!template text="""another nice theming that could work for someone""" start="00:12:37.160" video="qanda-color" id="subtitle"]] +[[!template text="""specifically for some use cases. I don't have to solve""" start="00:12:40.640" video="qanda-color" id="subtitle"]] +[[!template text="""everyone's problem. Yeah, and I mean, it was sufficient to""" start="00:12:44.200" video="qanda-color" id="subtitle"]] +[[!template text="""be inspirational to people. I mean, just Bala just""" start="00:12:48.720" video="qanda-color" id="subtitle"]] +[[!template text="""mentioned it right now, but I'm sure plenty of people who""" start="00:12:50.720" video="qanda-color" id="subtitle"]] +[[!template text="""watched live, but also people will be watching in the""" start="00:12:53.760" video="qanda-color" id="subtitle"]] +[[!template text="""future, will have the interest to speak by what you've done.""" start="00:12:56.000" video="qanda-color" id="subtitle"]] +[[!template text="""So thank you again so much for this. Yep. All right, well, I""" start="00:12:58.600" video="qanda-color" id="subtitle"]] +[[!template text="""don't see any further questions. So I suggest we move""" start="00:13:05.080" video="qanda-color" id="subtitle"]] +[[!template text="""towards closure. Ryota, do you have any last words? No, I""" start="00:13:09.720" video="qanda-color" id="subtitle"]] +[[!template text="""don't. So yeah, thank you very much for attending. And it was""" start="00:13:14.280" video="qanda-color" id="subtitle"]] +[[!template text="""great fun putting this together. And I really didn't think""" start="00:13:17.080" video="qanda-color" id="subtitle"]] +[[!template text="""that I would be talking about my personal colors and""" start="00:13:20.520" video="qanda-color" id="subtitle"]] +[[!template text="""personal favorites, like orange being my favorite color.""" start="00:13:24.760" video="qanda-color" id="subtitle"]] +[[!template text="""This wouldn't be something that I would say out in any""" start="00:13:27.760" video="qanda-color" id="subtitle"]] +[[!template text="""conference, to be honest. But it just came out to be. And""" start="00:13:30.120" video="qanda-color" id="subtitle"]] +[[!template text="""happy that I had a chance. So thank you very much for giving me""" start="00:13:34.160" video="qanda-color" id="subtitle"]] +[[!template text="""the opportunity to talk. in this amazing conference and""" start="00:13:37.480" video="qanda-color" id="subtitle"]] +[[!template text="""yeah I can't just wait to check out other talks which you know""" start="00:13:41.440" video="qanda-color" id="subtitle"]] +[[!template text="""I know that there isn't you know other talks that are""" start="00:13:44.320" video="qanda-color" id="subtitle"]] +[[!template text="""happening right now I was actually wanted to to join them and""" start="00:13:46.920" video="qanda-color" id="subtitle"]] +[[!template text="""check check that out so I will probably do that right now.""" start="00:13:50.200" video="qanda-color" id="subtitle"]] +[[!template text="""Well, sure. Well, I won't hold you any longer then. Thank""" start="00:13:52.760" video="qanda-color" id="subtitle"]] +[[!template text="""you. For me, it was just amazing to, you know, generally when""" start="00:13:56.840" video="qanda-color" id="subtitle"]] +[[!template text="""you ask someone what their favorite color, you know, they""" start="00:13:59.760" video="qanda-color" id="subtitle"]] +[[!template text="""just tell you orange or blue or whatever. They don't go then""" start="00:14:01.640" video="qanda-color" id="subtitle"]] +[[!template text="""to chat about 20 minutes about their favorite color and how""" start="00:14:04.400" video="qanda-color" id="subtitle"]] +[[!template text="""they tuned their entire editor to work exactly around their""" start="00:14:07.040" video="qanda-color" id="subtitle"]] +[[!template text="""favorite colors. So it was inspiring. And I also want to try""" start="00:14:10.080" video="qanda-color" id="subtitle"]] +[[!template text="""it out, frankly, because my theme has been utterly bad for""" start="00:14:14.760" video="qanda-color" id="subtitle"]] +[[!template text="""the last five years and I need some change into my life. All""" start="00:14:18.000" video="qanda-color" id="subtitle"]] +[[!template text="""right. Thank you so much for your time. Thank you very much,""" start="00:14:20.640" video="qanda-color" id="subtitle"]] +[[!template text="""everyone. Cheers. Bye-bye.""" start="00:14:24.320" video="qanda-color" id="subtitle"]]
Questions or comments? Please e-mail [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Comment%20for%20EmacsConf%202023%20color%3A%20Colour%20your%20Emacs%20with%20ease) diff --git a/2024/info/color-before.md b/2024/info/color-before.md index ca43b9bb..89145fbd 100644 --- a/2024/info/color-before.md +++ b/2024/info/color-before.md @@ -17,16 +17,16 @@ Status: TO_CAPTION_QA 08:08.400 Hasliberg theme 11:06.240 Wrap up -"""]]
Duration: 11:48 minutes
+"""]]
Duration: 11:48 minutes
# Q&A
[[!template id="chapters" vidid="qanda-color" data=""" -01:23.733 Why colour? -03:00.535 What motivated you to learn Elisp and get into the Emacs core? -06:35.982 Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps? -10:51.880 Q: Can we have a dark as well as light theme variations made from your theme? +01:24.840 Why colour? +03:04.040 What motivated you to learn Elisp and get into the Emacs core? +06:35.320 Q: Is there any intention to create a library for working with more experimental color spaces? Pulling code out of Hasliberg for this purpose, perhaps? +10:51.520 Q: Can we have a dark as well as light theme variations made from your theme? -"""]]
Listen to just the audio:
Duration: 14:31 minutes
+"""]]
Listen to just the audio:
Duration: 14:31 minutes
# Description \ No newline at end of file diff --git a/2024/info/emacs30-before.md b/2024/info/emacs30-before.md index 144472e0..dc1141b8 100644 --- a/2024/info/emacs30-before.md +++ b/2024/info/emacs30-before.md @@ -22,7 +22,7 @@ Status: TO_CAPTION_QA 21:16.920 Reindenting 23:17.940 Wrapping up -"""]]
Duration: 24:55 minutes
+"""]]
Duration: 24:55 minutes
# Q&A @@ -35,6 +35,6 @@ Status: TO_CAPTION_QA 09:08.648 Q: I am worried about the situation on non-free systems. There was talk about the Windows and the macOS versions being as good as unmaintained. Where do we go from here? 11:35.280 Q: Is there a best practice on what Org to use when following emacs-latest? -"""]]
Listen to just the audio:
Duration: 23:36 minutes
+"""]]
Listen to just the audio:
Duration: 23:36 minutes
# Description \ No newline at end of file diff --git a/2024/info/guile-before.md b/2024/info/guile-before.md index efee2dfb..d3d7099f 100644 --- a/2024/info/guile-before.md +++ b/2024/info/guile-before.md @@ -9,7 +9,7 @@ Status: TO_CAPTION_QA # Talk -
Duration: 15:57 minutes
+
Duration: 15:57 minutes
# Q&A @@ -22,6 +22,6 @@ Status: TO_CAPTION_QA 12:30.000 Q: Do you think guile-emacs will be able to use or (collaborate with) some of the other awesome projects around Emacs Lisp? 15:04.200 Q: SBCL, ...You mentioned Robert Strandh's SICL along with SBCL---does that work help with the implementation of CL in Guile? -"""]]
Listen to just the audio:
+"""]]
Listen to just the audio:
# Description \ No newline at end of file diff --git a/2024/info/gypsum-after.md b/2024/info/gypsum-after.md index 68f4baf9..2cb0cbd8 100644 --- a/2024/info/gypsum-after.md +++ b/2024/info/gypsum-after.md @@ -379,250 +379,250 @@ Captioner: ramin

Q&A transcript (unedited)

-[[!template text="""Troy Hinckley's project that I'm talking about. I was going""" start="00:00:00.069" video="qanda-gypsum" id="subtitle"]] -[[!template text="""to mention this in my presentation, but it's possible,""" start="00:00:02.350" video="qanda-gypsum" id="subtitle"]] -[[!template text="""theoretically, that Troy Hinckley, his project could be""" start="00:00:02.350" video="qanda-gypsum" id="subtitle"]] -[[!template text="""used as a scheme of limitation that actually runs my own""" start="00:00:02.350" video="qanda-gypsum" id="subtitle"]] -[[!template text="""version of Emacs. And although, you know, This is""" start="00:00:02.350" video="qanda-gypsum" id="subtitle"]] -[[!template text="""completely theoretical, and I don't know how difficult""" start="00:00:25.478" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that would be. But if Troy Hinckley implemented enough of""" start="00:00:25.478" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the R7-RS standard in Rust, it would theoretically be""" start="00:00:30.781" video="qanda-gypsum" id="subtitle"]] -[[!template text="""possible to run the Gypsum editor in Troy Hinckley's own""" start="00:00:30.781" video="qanda-gypsum" id="subtitle"]] -[[!template text="""editor. I thought that was kind of interesting, and I""" start="00:00:30.781" video="qanda-gypsum" id="subtitle"]] -[[!template text="""thought it was worth mentioning, at least in the questions""" start="00:00:48.270" video="qanda-gypsum" id="subtitle"]] -[[!template text="""and answers.""" start="00:00:48.270" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I also mentioned this in the presentation. I wanted to see""" start="00:01:12.179" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Robin Templeton's project presentation, but""" start="00:01:14.940" video="qanda-gypsum" id="subtitle"]] -[[!template text="""unfortunately it's going to be at like four in the morning""" start="00:01:14.940" video="qanda-gypsum" id="subtitle"]] -[[!template text="""for me. So I'm going to try and watch that tomorrow, but""" start="00:01:14.940" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that's also going to be a very interesting project to keep an""" start="00:01:22.984" video="qanda-gypsum" id="subtitle"]] -[[!template text="""eye on if you're interested in Scheme. That's the project""" start="00:01:22.984" video="qanda-gypsum" id="subtitle"]] -[[!template text="""where you've got the Guylain interpreter running inside of""" start="00:01:33.149" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the Emacs process. It's dynamically linked as a library.""" start="00:01:33.149" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I'm ready for questions from anybody. You can ask or you can""" start="00:02:04.699" video="qanda-gypsum" id="subtitle"]] -[[!template text="""type. It's up to you.""" start="00:02:07.431" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Okay, let me check the etherpad.""" start="00:02:32.319" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Let's see here.""" start="00:02:37.304" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I'm not sure if I'm doing that right.""" start="00:02:41.208" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Let me check one more time. Oh, there it goes.""" start="00:02:46.373" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Let's see, so this is...""" start="00:02:54.221" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I didn't know about that first bit of history. Oh, I've heard""" start="00:03:00.151" video="qanda-gypsum" id="subtitle"]] -[[!template text="""RMS say that Scheme Guile is just a nicer Lisp, but I didn't""" start="00:03:02.332" video="qanda-gypsum" id="subtitle"]] -[[!template text="""know there were concrete talks attempts to use Guile for""" start="00:03:02.332" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs that early. Let's see, that was from janneke.""" start="00:03:02.332" video="qanda-gypsum" id="subtitle"]] +[[!template text="""...Troy Hinckley's project that I'm talking about. I was going""" start="00:00:00.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""to mention this in my presentation, but it's possible,""" start="00:00:03.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""theoretically, that Troy Hinckley, his project could be""" start="00:00:08.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""used as a scheme of limitation that actually runs my own""" start="00:00:16.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""version of Emacs. And although, you know, This is""" start="00:00:18.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""completely theoretical, and I don't know how difficult""" start="00:00:23.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that would be. But if Troy Hinckley implemented enough of""" start="00:00:30.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the R7-RS standard in Rust, it would theoretically be""" start="00:00:34.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""possible to run the Gypsum editor in Troy Hinckley's own""" start="00:00:39.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""editor. I thought that was kind of interesting, and I""" start="00:00:46.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""thought it was worth mentioning, at least in the questions""" start="00:00:50.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""and answers.""" start="00:00:59.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I also mentioned this in the presentation. I wanted to see""" start="00:01:12.160" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Robin Templeton's project presentation, but""" start="00:01:16.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""unfortunately it's going to be at like four in the morning""" start="00:01:20.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""for me. So I'm going to try and watch that tomorrow, but""" start="00:01:22.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that's also going to be a very interesting project to keep an""" start="00:01:26.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""eye on if you're interested in Scheme. That's the project""" start="00:01:29.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""where you've got the Guylain interpreter running inside of""" start="00:01:34.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the Emacs process. It's dynamically linked as a library.""" start="00:01:37.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I'm ready for questions from anybody. You can ask or you can""" start="00:02:04.680" video="qanda-gypsum" id="subtitle"]] +[[!template text="""type. It's up to you.""" start="00:02:08.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Okay, let me check the etherpad.""" start="00:02:32.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Let's see here.""" start="00:02:37.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I'm not sure if I'm doing that right.""" start="00:02:41.160" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Let me check one more time. Oh, there it goes.""" start="00:02:42.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Let's see, so this is...""" start="00:02:54.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I didn't know about that first bit of history. Oh, I've heard""" start="00:03:00.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""RMS say that Scheme Guile is just a nicer Lisp, but I didn't""" start="00:03:02.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""know there were concrete talks attempts to use Guile for""" start="00:03:06.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs that early. Let's see, that was from janneke.""" start="00:03:09.080" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: I'm curious to know how the hell guile-emacs deals with all of the dynamically scoped modules out there. Is there any effort to automatically modularize and namespace stuff?""" start="00:03:09.370" video="qanda-gypsum" id="subtitle"]]
[[!template text="""I'm curious to know how the hell Guile Emacs deals with all the""" start="00:03:09.370" video="qanda-gypsum" id="subtitle"]] -[[!template text="""dynamically scoped modules out there. Is there any effort""" start="00:03:14.318" video="qanda-gypsum" id="subtitle"]] -[[!template text="""to automatically modularize and name? Let's see.""" start="00:03:20.181" video="qanda-gypsum" id="subtitle"]] -[[!template text="""That might be a better question for Robin Templeton. In my""" start="00:03:30.523" video="qanda-gypsum" id="subtitle"]] -[[!template text="""own project,""" start="00:03:36.727" video="qanda-gypsum" id="subtitle"]] -[[!template text="""there's no module system for Emacs Lisp. There is a module""" start="00:03:36.727" video="qanda-gypsum" id="subtitle"]] -[[!template text="""system for Scheme. And the Emacs Lisp interpreter runs in""" start="00:03:46.693" video="qanda-gypsum" id="subtitle"]] -[[!template text="""its own environment. the require system or whatever module""" start="00:03:49.695" video="qanda-gypsum" id="subtitle"]] -[[!template text="""system that Emacs has, once it's implemented, all of that""" start="00:03:57.068" video="qanda-gypsum" id="subtitle"]] -[[!template text="""would just happen inside of the Emacs Lisp environment,""" start="00:03:57.068" video="qanda-gypsum" id="subtitle"]] -[[!template text="""which is inside of the Scheme environment. And""" start="00:03:57.068" video="qanda-gypsum" id="subtitle"]] -[[!template text="""environments are objects in Scheme.""" start="00:04:12.437" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I think a more difficult question is how to handle""" start="00:04:21.522" video="qanda-gypsum" id="subtitle"]] -[[!template text="""threading, and Scheme has very good threading built in, in""" start="00:04:26.420" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Serphe-18[??].""" start="00:04:26.420" video="qanda-gypsum" id="subtitle"]] -[[!template text="""But I don't think it will be easy to write Emacs Lisp form""" start="00:04:34.283" video="qanda-gypsum" id="subtitle"]] -[[!template text="""bindings to the Scheme multi-threading implementation.""" start="00:04:34.283" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs Lisp was just not cut out for that kind of thing. So I""" start="00:04:48.548" video="qanda-gypsum" id="subtitle"]] -[[!template text="""think each Emacs Lisp, you could, I suppose, have multiple""" start="00:04:51.710" video="qanda-gypsum" id="subtitle"]] -[[!template text="""threads each running their own Emacs Lisp environment.""" start="00:04:51.710" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Scheme would make that very simple to do.""" start="00:05:01.375" video="qanda-gypsum" id="subtitle"]] -[[!template text="""And then there'd just be a question of how you would get those""" start="00:05:06.018" video="qanda-gypsum" id="subtitle"]] -[[!template text="""different interpreters to communicate with each other,""" start="00:05:06.018" video="qanda-gypsum" id="subtitle"]] -[[!template text="""perhaps using the same protocol that's used by the Emacs""" start="00:05:06.018" video="qanda-gypsum" id="subtitle"]] -[[!template text="""server. But I haven't thought that far ahead yet.""" start="00:05:06.018" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: I'm curious to know how the hell guile-emacs deals with all of the dynamically scoped modules out there. Is there any effort to automatically modularize and namespace stuff?""" start="00:03:14.320" video="qanda-gypsum" id="subtitle"]]
[[!template text="""I'm curious to know how the hell Guile Emacs deals with all the""" start="00:03:14.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""dynamically scoped modules out there. Is there any effort""" start="00:03:17.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""to automatically modularize and name? Let's see.""" start="00:03:21.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""That might be a better question for Robin Templeton. In my""" start="00:03:29.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""own project,""" start="00:03:40.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""there's no module system for Emacs Lisp. There is a module""" start="00:03:44.640" video="qanda-gypsum" id="subtitle"]] +[[!template text="""system for Scheme. And the Emacs Lisp interpreter runs in""" start="00:03:49.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""its own environment. the require system or whatever module""" start="00:03:55.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""system that Emacs has, once it's implemented, all of that""" start="00:04:01.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""would just happen inside of the Emacs Lisp environment,""" start="00:04:06.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""which is inside of the Scheme environment. And""" start="00:04:09.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""environments are objects in Scheme.""" start="00:04:12.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I think a more difficult question is how to handle""" start="00:04:21.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""threading, and Scheme has very good threading built in, in""" start="00:04:26.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Serphe-18[??].""" start="00:04:33.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""But I don't think it will be easy to write Emacs Lisp form""" start="00:04:34.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""bindings to the Scheme multi-threading implementation.""" start="00:04:43.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs Lisp was just not cut out for that kind of thing. So I""" start="00:04:48.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""think each Emacs Lisp, you could, I suppose, have multiple""" start="00:04:52.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""threads each running their own Emacs Lisp environment.""" start="00:04:56.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Scheme would make that very simple to do.""" start="00:05:00.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""And then there'd just be a question of how you would get those""" start="00:05:05.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""different interpreters to communicate with each other,""" start="00:05:08.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""perhaps using the same protocol that's used by the Emacs""" start="00:05:11.680" video="qanda-gypsum" id="subtitle"]] +[[!template text="""server. But I haven't thought that far ahead yet.""" start="00:05:16.280" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Would it be possible to support a GUI toolkit other than GTK?""" start="00:05:23.646" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Would it be possible to support a GUI toolkit other than the""" start="00:05:23.646" video="qanda-gypsum" id="subtitle"]] -[[!template text="""GTK? Like, how is it still supports Lucid? Yes, this is""" start="00:05:23.646" video="qanda-gypsum" id="subtitle"]] -[[!template text="""absolutely a goal of the project. I'm trying to keep the back""" start="00:05:31.291" video="qanda-gypsum" id="subtitle"]] -[[!template text="""end separate as possible. The scheme has what you call""" start="00:05:33.873" video="qanda-gypsum" id="subtitle"]] -[[!template text="""parameters. And these are like global variables that are""" start="00:05:39.817" video="qanda-gypsum" id="subtitle"]] -[[!template text="""still somewhat thread safe. And every call to the GUI goes""" start="00:05:43.199" video="qanda-gypsum" id="subtitle"]] -[[!template text="""through a parameter. So the Emacs, the interpreter and the""" start="00:05:47.484" video="qanda-gypsum" id="subtitle"]] -[[!template text="""editor logic is all in one module. And then that module calls""" start="00:05:52.125" video="qanda-gypsum" id="subtitle"]] -[[!template text="""out into a separate GUI module. And then you can implement""" start="00:05:59.987" video="qanda-gypsum" id="subtitle"]] -[[!template text="""different GUI modules. So you could have one for GTK3, one""" start="00:06:04.989" video="qanda-gypsum" id="subtitle"]] -[[!template text="""for GTK4, if you want to write the extern C bindings around Qt""" start="00:06:08.430" video="qanda-gypsum" id="subtitle"]] -[[!template text="""or full tick, that would certainly be possible as well. It""" start="00:06:13.843" video="qanda-gypsum" id="subtitle"]] -[[!template text="""would be nice maybe to have an SDL implementation based""" start="00:06:21.185" video="qanda-gypsum" id="subtitle"]] -[[!template text="""maybe on Chikiti or some kind of immediate mode GUI,""" start="00:06:21.185" video="qanda-gypsum" id="subtitle"]] -[[!template text="""something like that. But definitely GTK3 through Guile GI""" start="00:06:21.185" video="qanda-gypsum" id="subtitle"]] -[[!template text="""is the reference implementation. Things start there. But""" start="00:06:33.808" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I'm very interested in supporting other GUIs, yes. Let's""" start="00:06:41.298" video="qanda-gypsum" id="subtitle"]] -[[!template text="""see.""" start="00:06:45.199" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Would it be possible to support a GUI toolkit other than GTK?""" start="00:05:23.640" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Would it be possible to support a GUI toolkit other than the""" start="00:05:23.640" video="qanda-gypsum" id="subtitle"]] +[[!template text="""GTK? Like, how is it still supports Lucid? Yes, this is""" start="00:05:26.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""absolutely a goal of the project. I'm trying to keep the back""" start="00:05:31.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""end separate as possible. The scheme has what you call""" start="00:05:37.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""parameters. And these are like global variables that are""" start="00:05:41.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""still somewhat thread safe. And every call to the GUI goes""" start="00:05:45.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""through a parameter. So the Emacs, the interpreter and the""" start="00:05:50.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""editor logic is all in one module. And then that module calls""" start="00:05:58.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""out into a separate GUI module. And then you can implement""" start="00:06:01.680" video="qanda-gypsum" id="subtitle"]] +[[!template text="""different GUI modules. So you could have one for GTK3, one""" start="00:06:06.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""for GTK4, if you want to write the extern C bindings around Qt""" start="00:06:11.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""or full tick, that would certainly be possible as well. It""" start="00:06:16.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""would be nice maybe to have an SDL implementation based""" start="00:06:21.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""maybe on Chikiti or some kind of immediate mode GUI,""" start="00:06:25.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""something like that. But definitely GTK3 through Guile GI""" start="00:06:31.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""is the reference implementation. Things start there. But""" start="00:06:37.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I'm very interested in supporting other GUIs, yes. Let's""" start="00:06:41.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""see.""" start="00:06:44.000" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Do you plan to provide improvements to Elisp as a language, or is the focus on a compatibility layer to facilitate doing all new extensions, etc. in Scheme?""" start="00:06:45.257" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Question, do you plan to provide improvements to ELisp""" start="00:06:45.257" video="qanda-gypsum" id="subtitle"]] -[[!template text="""as a language or focus on a compatibility layer to""" start="00:06:47.540" video="qanda-gypsum" id="subtitle"]] -[[!template text="""facilitate all new extensions in Scheme? Yeah, the second""" start="00:06:47.540" video="qanda-gypsum" id="subtitle"]] -[[!template text="""one. I want to move off to Scheme. I would like for this""" start="00:06:57.142" video="qanda-gypsum" id="subtitle"]] -[[!template text="""project to try and keep up to date with each new release of""" start="00:07:03.384" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs and Emacs Lisp. That's a difficult moving target to""" start="00:07:05.666" video="qanda-gypsum" id="subtitle"]] -[[!template text="""follow, I realize. But to the greatest extent possible, any""" start="00:07:11.850" video="qanda-gypsum" id="subtitle"]] -[[!template text="""new features to Emacs Lisp will be pulled in from GNU Emacs.""" start="00:07:15.152" video="qanda-gypsum" id="subtitle"]] -[[!template text="""If we happen to be able to implement something cool in""" start="00:07:25.419" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Scheme, and be able to port it over to Emacs Lisp, then sure,""" start="00:07:25.419" video="qanda-gypsum" id="subtitle"]] -[[!template text="""it'd be nice to be able to upload or to submit that upstream to""" start="00:07:29.437" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the GNU Emacs. But I think I would prefer to have new features""" start="00:07:29.437" video="qanda-gypsum" id="subtitle"]] -[[!template text="""written in Scheme. I would like this gypsum to be more of a""" start="00:07:38.584" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Scheme app platform that just happens to be able to also run""" start="00:07:43.989" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs Lisp. That's how I see it. Of course, this will be a""" start="00:07:43.989" video="qanda-gypsum" id="subtitle"]] -[[!template text="""community project. I'm open to debate about that if anybody""" start="00:07:54.577" video="qanda-gypsum" id="subtitle"]] -[[!template text="""wants to convince me otherwise.""" start="00:07:58.809" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Why is being able to interpret all of that EL a useful goal?""" start="00:08:08.439" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Sure, there is a lot of code written in Elisp. Can we""" start="00:08:12.464" video="qanda-gypsum" id="subtitle"]] -[[!template text="""consider... Oh, it's still being written. Please go ahead""" start="00:08:15.206" video="qanda-gypsum" id="subtitle"]] -[[!template text="""and finish writing.""" start="00:08:18.390" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Do you plan to provide improvements to Elisp as a language, or is the focus on a compatibility layer to facilitate doing all new extensions, etc. in Scheme?""" start="00:06:46.040" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Question, do you plan to provide improvements to ELisp""" start="00:06:46.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""as a language or focus on a compatibility layer to""" start="00:06:50.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""facilitate all new extensions in Scheme? Yeah, the second""" start="00:06:54.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""one. I want to move off to Scheme. I would like for this""" start="00:06:58.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""project to try and keep up to date with each new release of""" start="00:07:04.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs and Emacs Lisp. That's a difficult moving target to""" start="00:07:09.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""follow, I realize. But to the greatest extent possible, any""" start="00:07:13.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""new features to Emacs Lisp will be pulled in from GNU Emacs.""" start="00:07:18.640" video="qanda-gypsum" id="subtitle"]] +[[!template text="""If we happen to be able to implement something cool in""" start="00:07:25.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Scheme, and be able to port it over to Emacs Lisp, then sure,""" start="00:07:28.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""it'd be nice to be able to upload or to submit that upstream to""" start="00:07:31.640" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the GNU Emacs. But I think I would prefer to have new features""" start="00:07:35.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""written in Scheme. I would like this gypsum to be more of a""" start="00:07:43.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Scheme app platform that just happens to be able to also run""" start="00:07:47.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs Lisp. That's how I see it. Of course, this will be a""" start="00:07:51.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""community project. I'm open to debate about that if anybody""" start="00:07:56.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""wants to convince me otherwise.""" start="00:08:00.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Why is being able to interpret all of that EL a useful goal?""" start="00:08:02.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Sure, there is a lot of code written in Elisp. Can we""" start="00:08:11.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""consider... Oh, it's still being written. Please go ahead""" start="00:08:15.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""and finish writing.""" start="00:08:18.960" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Can we consider a translator like utility to convert elisp to scheme, once guile-emacs becomes a reality?""" start="00:08:29.673" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Can we consider a translator like utility to convert eLisp""" start="00:08:29.673" video="qanda-gypsum" id="subtitle"]] -[[!template text="""to Scheme once Guile-Emacs has become a reality?""" start="00:08:29.673" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Certainly. For the time being, I just wanted to get the""" start="00:08:36.716" video="qanda-gypsum" id="subtitle"]] -[[!template text="""interpreter running. So the actual, the Guile-Emacs Lisp,""" start="00:08:38.717" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the one that was written in 2011 that I didn't write, that""" start="00:08:44.520" video="qanda-gypsum" id="subtitle"]] -[[!template text="""actually does compile to, I think it's the tree""" start="00:08:44.520" video="qanda-gypsum" id="subtitle"]] -[[!template text="""intermediate representation It's one of the intermediate""" start="00:08:44.520" video="qanda-gypsum" id="subtitle"]] -[[!template text="""languages that Guile uses to compile Guile scheme itself.""" start="00:08:59.076" video="qanda-gypsum" id="subtitle"]] -[[!template text="""So the Emacs lisp that was written before actually does""" start="00:09:04.817" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that. It actually compiles and makes use of the entire Guile""" start="00:09:04.817" video="qanda-gypsum" id="subtitle"]] -[[!template text="""compiler tool chain and actually produces like JIT""" start="00:09:09.339" video="qanda-gypsum" id="subtitle"]] -[[!template text="""compilable binaries, which is really cool. Like I said,""" start="00:09:09.339" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that's the one that I had trouble getting to work properly.""" start="00:09:23.342" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Maybe we can follow that architecture. I'm not sure how to do""" start="00:09:29.209" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that, but I would like to be able to do some kind of""" start="00:09:33.052" video="qanda-gypsum" id="subtitle"]] -[[!template text="""translating, keeping in mind that we want to have this be""" start="00:09:33.052" video="qanda-gypsum" id="subtitle"]] -[[!template text="""portable, do various schemes. And so Guile makes this very""" start="00:09:33.052" video="qanda-gypsum" id="subtitle"]] -[[!template text="""easy, but other schemes don't. Gambit might do this pretty""" start="00:09:45.988" video="qanda-gypsum" id="subtitle"]] -[[!template text="""well as well. It compiles to C and then compiles C down to a""" start="00:09:51.549" video="qanda-gypsum" id="subtitle"]] -[[!template text="""dynamically linkable library. So yeah, I think probably""" start="00:09:53.950" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the most portable, I'm just thinking out loud right now,""" start="00:10:03.372" video="qanda-gypsum" id="subtitle"]] -[[!template text="""most portable implementation will just be able to""" start="00:10:10.652" video="qanda-gypsum" id="subtitle"]] -[[!template text="""translate Emacs Lisp directly to Scheme, which is not what""" start="00:10:10.652" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the old Guile Emacs Lisp implementation does. That goes to""" start="00:10:10.652" video="qanda-gypsum" id="subtitle"]] -[[!template text="""TreeIL, so it's very, very Guile-specific, can't be""" start="00:10:21.755" video="qanda-gypsum" id="subtitle"]] -[[!template text="""ported. But yeah, if we could somehow get Emacs Lisp""" start="00:10:21.755" video="qanda-gypsum" id="subtitle"]] -[[!template text="""translated to Scheme and then compiled, say, in Shea Scheme""" start="00:10:28.359" video="qanda-gypsum" id="subtitle"]] -[[!template text="""or Gambit or MIT Scheme or one of those other compilers, that""" start="00:10:28.359" video="qanda-gypsum" id="subtitle"]] -[[!template text="""would be very cool. And I would absolutely love to do that.""" start="00:10:28.359" video="qanda-gypsum" id="subtitle"]] -[[!template text="""And I would very quickly accept any code into the code base""" start="00:10:44.906" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that would do that.""" start="00:10:44.906" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Can we consider a translator like utility to convert elisp to scheme, once guile-emacs becomes a reality?""" start="00:08:19.440" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Can we consider a translator like utility to convert eLisp""" start="00:08:19.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""to Scheme once Guile-Emacs has become a reality?""" start="00:08:32.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Certainly. For the time being, I just wanted to get the""" start="00:08:37.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""interpreter running. So the actual, the Guile-Emacs Lisp,""" start="00:08:42.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the one that was written in 2011 that I didn't write, that""" start="00:08:47.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""actually does compile to, I think it's the tree""" start="00:08:51.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""intermediate representation It's one of the intermediate""" start="00:08:57.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""languages that Guile uses to compile Guile scheme itself.""" start="00:08:59.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""So the Emacs lisp that was written before actually does""" start="00:09:03.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that. It actually compiles and makes use of the entire Guile""" start="00:09:09.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""compiler tool chain and actually produces like JIT""" start="00:09:13.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""compilable binaries, which is really cool. Like I said,""" start="00:09:17.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that's the one that I had trouble getting to work properly.""" start="00:09:21.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Maybe we can follow that architecture. I'm not sure how to do""" start="00:09:27.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that, but I would like to be able to do some kind of""" start="00:09:34.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""translating, keeping in mind that we want to have this be""" start="00:09:37.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""portable, do various schemes. And so Guile makes this very""" start="00:09:42.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""easy, but other schemes don't. Gambit might do this pretty""" start="00:09:48.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""well as well. It compiles to C and then compiles C down to a""" start="00:09:52.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""dynamically linkable library. So yeah, I think probably""" start="00:09:57.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the most portable, I'm just thinking out loud right now,""" start="00:10:06.160" video="qanda-gypsum" id="subtitle"]] +[[!template text="""most portable implementation will just be able to""" start="00:10:09.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""translate Emacs Lisp directly to Scheme, which is not what""" start="00:10:13.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the old Guile Emacs Lisp implementation does. That goes to""" start="00:10:17.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""TreeIL, so it's very, very Guile-specific, can't be""" start="00:10:22.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""ported. But yeah, if we could somehow get Emacs Lisp""" start="00:10:26.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""translated to Scheme and then compiled, say, in Shea Scheme""" start="00:10:30.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""or Gambit or MIT Scheme or one of those other compilers, that""" start="00:10:37.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""would be very cool. And I would absolutely love to do that.""" start="00:10:40.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""And I would very quickly accept any code into the code base""" start="00:10:44.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that would do that.""" start="00:10:49.280" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Why is being able to interpret all of \`init.el\` an useful goal?""" start="00:10:54.390" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Oh, and to answer the question about init.el,""" start="00:10:54.390" video="qanda-gypsum" id="subtitle"]] -[[!template text="""It's just because people spend a lot of time on their configs""" start="00:10:59.207" video="qanda-gypsum" id="subtitle"]] -[[!template text="""and it would be nice if, you know, you're starting to use this""" start="00:10:59.207" video="qanda-gypsum" id="subtitle"]] -[[!template text="""new editor and want it to be similar to Emacs users, just the""" start="00:10:59.207" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs community in general and people who are familiar with""" start="00:10:59.207" video="qanda-gypsum" id="subtitle"]] -[[!template text="""using Emacs. It would be more useful to everybody in the""" start="00:10:59.207" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs community if this were more compatible with GNU""" start="00:11:17.715" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs. And so that's why that's, I think that's an important""" start="00:11:17.715" video="qanda-gypsum" id="subtitle"]] -[[!template text="""goal.""" start="00:11:25.679" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Question is not yet. Great. Oh, here comes another""" start="00:11:34.465" video="qanda-gypsum" id="subtitle"]] -[[!template text="""question.""" start="00:11:38.471" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Why is being able to interpret all of \`init.el\` an useful goal?""" start="00:10:50.600" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Oh, and to answer the question about init.el,""" start="00:10:50.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""It's just because people spend a lot of time on their configs""" start="00:10:59.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""and it would be nice if, you know, you're starting to use this""" start="00:11:02.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""new editor and want it to be similar to Emacs users, just the""" start="00:11:06.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs community in general and people who are familiar with""" start="00:11:14.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""using Emacs. It would be more useful to everybody in the""" start="00:11:16.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs community if this were more compatible with GNU""" start="00:11:20.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs. And so that's why that's, I think that's an important""" start="00:11:25.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""goal.""" start="00:11:36.000" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Question is not yet. Great. Oh, here comes another""" start="00:11:38.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""question.""" start="00:12:01.840" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: What is the plan to handle elisp packages that depend on 3rd party/external libraries? (libgit/magit or rg/ripgrep)?""" start="00:12:08.539" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Okay, what is the plan to handle elisp packages that depend""" start="00:12:08.539" video="qanda-gypsum" id="subtitle"]] -[[!template text="""on third-party or external libraries like git or magit""" start="00:12:08.539" video="qanda-gypsum" id="subtitle"]] -[[!template text="""or ripgrep? So that's going to be tricky. It depends on how""" start="00:12:08.539" video="qanda-gypsum" id="subtitle"]] -[[!template text="""these external packages are linked into emacs. If it's""" start="00:12:21.523" video="qanda-gypsum" id="subtitle"]] -[[!template text="""going to be a dynamic library like Robin Templeton's""" start="00:12:26.844" video="qanda-gypsum" id="subtitle"]] -[[!template text="""project which you load the libgit library into the Emacs""" start="00:12:26.844" video="qanda-gypsum" id="subtitle"]] -[[!template text="""process, that is going to be extremely difficult. So if you""" start="00:12:35.289" video="qanda-gypsum" id="subtitle"]] -[[!template text="""have an external library like, I don't know, libgit or""" start="00:12:44.032" video="qanda-gypsum" id="subtitle"]] -[[!template text="""what's the GUI thing? Cabal. No, not Cabal. Cairo, libcairo""" start="00:12:44.032" video="qanda-gypsum" id="subtitle"]] -[[!template text="""to do SVG graphics and so on.""" start="00:12:57.736" video="qanda-gypsum" id="subtitle"]] -[[!template text="""You can do that very easily with Guile, but then on top of""" start="00:13:04.483" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that, implementing Emacs list bindings to it, I mean,""" start="00:13:04.483" video="qanda-gypsum" id="subtitle"]] -[[!template text="""you've got two layers there, and that makes things pretty""" start="00:13:04.483" video="qanda-gypsum" id="subtitle"]] -[[!template text="""difficult. So it's possible. And to some degree, maybe""" start="00:13:04.483" video="qanda-gypsum" id="subtitle"]] -[[!template text="""necessary for example, Cairo, if we want to do SVG graphics""" start="00:13:21.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the way that Emacs Lisp does, we're going to have to have""" start="00:13:21.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that. So that would be necessary. We would have to have those""" start="00:13:21.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""two layers. Yes, let's do that. But if it's like for Magit,""" start="00:13:32.643" video="qanda-gypsum" id="subtitle"]] -[[!template text="""you can just call out to your git process, and then you're""" start="00:13:38.047" video="qanda-gypsum" id="subtitle"]] -[[!template text="""just using the regular process APIs that Emacs Lisp has. And""" start="00:13:38.047" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that can be, already we, like Guile has some very good""" start="00:13:51.451" video="qanda-gypsum" id="subtitle"]] -[[!template text="""implementations for process management. And so it would""" start="00:13:51.451" video="qanda-gypsum" id="subtitle"]] -[[!template text="""just be a matter of wrapping up those in the Emacs lisp form""" start="00:13:59.055" video="qanda-gypsum" id="subtitle"]] -[[!template text="""bindings. So yeah, dynamic libraries, I wanna try to avoid.""" start="00:13:59.055" video="qanda-gypsum" id="subtitle"]] -[[!template text="""And I would prefer to do things more through, you know,""" start="00:14:12.222" video="qanda-gypsum" id="subtitle"]] -[[!template text="""launching a child process in the Emacs process. and then""" start="00:14:12.222" video="qanda-gypsum" id="subtitle"]] -[[!template text="""communicating over the standard in, standard out""" start="00:14:20.956" video="qanda-gypsum" id="subtitle"]] -[[!template text="""channels.""" start="00:14:20.956" video="qanda-gypsum" id="subtitle"]] -[[!template text="""That's the easier way to do things, I think, because then you""" start="00:14:29.460" video="qanda-gypsum" id="subtitle"]] -[[!template text="""can just use the process library that Emacs already has, and""" start="00:14:29.460" video="qanda-gypsum" id="subtitle"]] -[[!template text="""you can just reuse all of that code.""" start="00:14:29.460" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I'm not sure how ripgrep works, unfortunately, but I""" start="00:14:43.969" video="qanda-gypsum" id="subtitle"]] -[[!template text="""believe that's also a process, a child process. So, we can""" start="00:14:43.969" video="qanda-gypsum" id="subtitle"]] -[[!template text="""just reuse all of the Emacs Lisp code that does that already.""" start="00:14:50.412" video="qanda-gypsum" id="subtitle"]] -[[!template text="""We just need to make sure that the process management""" start="00:14:54.014" video="qanda-gypsum" id="subtitle"]] -[[!template text="""implementation and scheme is properly bound to Emacs Lisp,""" start="00:14:54.014" video="qanda-gypsum" id="subtitle"]] -[[!template text="""and it works the same as GNU Emacs does. Once that's all set,""" start="00:14:54.014" video="qanda-gypsum" id="subtitle"]] -[[!template text="""then these porcelains, like around git, should fall into""" start="00:15:06.360" video="qanda-gypsum" id="subtitle"]] -[[!template text="""place. without too much difficulty, hopefully.""" start="00:15:06.360" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: What is the plan to handle elisp packages that depend on 3rd party/external libraries? (libgit/magit or rg/ripgrep)?""" start="00:12:02.280" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Okay, what is the plan to handle elisp packages that depend""" start="00:12:02.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""on third-party or external libraries like git or magit""" start="00:12:11.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""or ripgrep? So that's going to be tricky. It depends on how""" start="00:12:16.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""these external packages are linked into emacs. If it's""" start="00:12:22.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""going to be a dynamic library like Robin Templeton's""" start="00:12:27.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""project which you load the libgit library into the Emacs""" start="00:12:32.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""process, that is going to be extremely difficult. So if you""" start="00:12:38.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""have an external library like, I don't know, libgit or""" start="00:12:43.160" video="qanda-gypsum" id="subtitle"]] +[[!template text="""what's the GUI thing? Cabal. No, not Cabal. Cairo, libcairo""" start="00:12:49.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""to do SVG graphics and so on.""" start="00:12:59.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""You can do that very easily with Guile, but then on top of""" start="00:13:01.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that, implementing Emacs list bindings to it, I mean,""" start="00:13:09.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""you've got two layers there, and that makes things pretty""" start="00:13:14.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""difficult. So it's possible. And to some degree, maybe""" start="00:13:17.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""necessary for example, Cairo, if we want to do SVG graphics""" start="00:13:23.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the way that Emacs Lisp does, we're going to have to have""" start="00:13:27.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that. So that would be necessary. We would have to have those""" start="00:13:30.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""two layers. Yes, let's do that. But if it's like for Magit,""" start="00:13:33.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""you can just call out to your git process, and then you're""" start="00:13:39.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""just using the regular process APIs that Emacs Lisp has. And""" start="00:13:45.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that can be, already we, like Guile has some very good""" start="00:13:50.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""implementations for process management. And so it would""" start="00:13:57.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""just be a matter of wrapping up those in the Emacs lisp form""" start="00:14:08.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""bindings. So yeah, dynamic libraries, I wanna try to avoid.""" start="00:14:12.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""And I would prefer to do things more through, you know,""" start="00:14:24.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""launching a child process in the Emacs process. and then""" start="00:14:32.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""communicating over the standard in, standard out""" start="00:14:40.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""channels.""" start="00:14:47.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""That's the easier way to do things, I think, because then you""" start="00:14:47.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""can just use the process library that Emacs already has, and""" start="00:14:52.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""you can just reuse all of that code.""" start="00:14:58.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I'm not sure how ripgrep works, unfortunately, but I""" start="00:15:03.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""believe that's also a process, a child process. So, we can""" start="00:15:09.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""just reuse all of the Emacs Lisp code that does that already.""" start="00:15:15.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""We just need to make sure that the process management""" start="00:15:23.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""implementation and scheme is properly bound to Emacs Lisp,""" start="00:15:30.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""and it works the same as GNU Emacs does. Once that's all set,""" start="00:15:35.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""then these porcelains, like around git, should fall into""" start="00:15:43.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""place. without too much difficulty, hopefully.""" start="00:15:48.400" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Not really a question, but how about Schemacs as a name?""" start="00:15:21.112" video="qanda-gypsum" id="subtitle"]]
[[!template text="""How about Schemax as a name? I like the name. I like that name.""" start="00:15:21.112" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I haven't really looked into like, is that already used or is""" start="00:15:28.937" video="qanda-gypsum" id="subtitle"]] -[[!template text="""that going to be confusing? But certainly something we can""" start="00:15:28.937" video="qanda-gypsum" id="subtitle"]] -[[!template text="""discuss.""" start="00:15:33.380" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Another thing I should mention,""" start="00:15:38.243" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I should probably set up a server or something like Discord""" start="00:15:42.157" video="qanda-gypsum" id="subtitle"]] -[[!template text="""or something like that. Discourse, not Discord.""" start="00:15:42.157" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Discourse, the open source one, where we could actually""" start="00:15:51.619" video="qanda-gypsum" id="subtitle"]] -[[!template text="""chat about this stuff. For the time being, ActivityPub,""" start="00:15:51.619" video="qanda-gypsum" id="subtitle"]] -[[!template text="""mostly Mastodon, is how I communicate with people in real""" start="00:15:56.540" video="qanda-gypsum" id="subtitle"]] -[[!template text="""time, that or email. So if you want to get a hold of me, check""" start="00:15:56.540" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the notes for this presentation and just send me an email.""" start="00:16:09.809" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Any question at all is fine. If you want to contribute code,""" start="00:16:16.752" video="qanda-gypsum" id="subtitle"]] -[[!template text="""if you want to just learn how to contribute code, send me any""" start="00:16:19.633" video="qanda-gypsum" id="subtitle"]] -[[!template text="""questions. It's fine. I'm happy to answer them. And we can""" start="00:16:19.633" video="qanda-gypsum" id="subtitle"]] -[[!template text="""talk about the name as well.""" start="00:16:30.256" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Not really a question, but how about Schemacs as a name?""" start="00:15:55.280" video="qanda-gypsum" id="subtitle"]]
[[!template text="""How about Schemax as a name? I like the name. I like that name.""" start="00:15:55.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I haven't really looked into like, is that already used or is""" start="00:15:59.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""that going to be confusing? But certainly something we can""" start="00:16:03.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""discuss.""" start="00:16:09.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Another thing I should mention,""" start="00:16:10.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I should probably set up a server or something like Discord""" start="00:16:13.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""or something like that. Discourse, not Discord.""" start="00:16:18.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Discourse, the open source one, where we could actually""" start="00:16:25.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""chat about this stuff. For the time being, ActivityPub,""" start="00:16:31.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""mostly Mastodon, is how I communicate with people in real""" start="00:16:49.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""time, that or email. So if you want to get a hold of me, check""" start="00:16:52.400" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the notes for this presentation and just send me an email.""" start="00:16:57.280" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Any question at all is fine. If you want to contribute code,""" start="00:17:02.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""if you want to just learn how to contribute code, send me any""" start="00:17:09.040" video="qanda-gypsum" id="subtitle"]] +[[!template text="""questions. It's fine. I'm happy to answer them. And we can""" start="00:17:12.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""talk about the name as well.""" start="00:17:22.200" video="qanda-gypsum" id="subtitle"]] -
[[!template new="1" text="""Q: Why is it not feasible for the Emacs layer that interprets Emacs Lisp (the core in C) ot have a Scheme interpreter, instead of using Guile?""" start="00:16:45.931" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Okay, why is it not feasible for the Emacs layer that""" start="00:16:45.931" video="qanda-gypsum" id="subtitle"]] -[[!template text="""interprets Emacs Lisp, the core in C, have a Scheme""" start="00:16:45.931" video="qanda-gypsum" id="subtitle"]] -[[!template text="""interpreter instead of using Guile? Let's see, I have to,""" start="00:16:45.931" video="qanda-gypsum" id="subtitle"]] -[[!template text="""okay. Emacs layer interprets Emacs Lisp, the core in C, have""" start="00:16:55.496" video="qanda-gypsum" id="subtitle"]] -[[!template text="""a Scheme interpreter instead of using Guile. Okay, so that,""" start="00:16:57.737" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the question xlarsx is asking, xlars, x, So Lars is asking,""" start="00:17:07.362" video="qanda-gypsum" id="subtitle"]] -[[!template text="""is it not feasible for there to be an""" start="00:17:14.744" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs layer that interprets Emacs Lisp have a scheme""" start="00:17:14.744" video="qanda-gypsum" id="subtitle"]] -[[!template text="""interpreter? This is Robin Templeton's project. And""" start="00:17:14.744" video="qanda-gypsum" id="subtitle"]] -[[!template text="""they're presenting later today. So check the roster and be""" start="00:17:30.815" video="qanda-gypsum" id="subtitle"]] -[[!template text="""sure to see that presentation because that's exactly what""" start="00:17:32.697" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Robin Templeton is doing. That's not what I'm doing though.""" start="00:17:32.697" video="qanda-gypsum" id="subtitle"]] -[[!template text="""I'm trying to create something in Scheme. But yes, there is""" start="00:17:44.419" video="qanda-gypsum" id="subtitle"]] -[[!template text="""an attempt to get an Scheme interpreter to run inside of""" start="00:17:48.280" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Emacs itself. And it has its own method of binding to Emacs""" start="00:17:48.280" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Lisp functions and translating data like Lisp structures""" start="00:17:55.181" video="qanda-gypsum" id="subtitle"]] -[[!template text="""between Guile Scheme and Emacs Lisp. Robin will explain all""" start="00:17:55.181" video="qanda-gypsum" id="subtitle"]] -[[!template text="""of that in their presentation.""" start="00:18:05.943" video="qanda-gypsum" id="subtitle"]] -[[!template text="""OK, I think I've got through all the questions on Etherpad.""" start="00:18:28.519" video="qanda-gypsum" id="subtitle"]] -[[!template text="""But I'm going to hang out here for a bit longer. And yeah, feel""" start="00:18:33.620" video="qanda-gypsum" id="subtitle"]] -[[!template text="""free to do a video chat with me or send me more questions on""" start="00:18:37.621" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Etherpad or here in the big blue button. And so I'm just going""" start="00:18:37.621" video="qanda-gypsum" id="subtitle"]] -[[!template text="""to hang out. And thanks for asking all your questions. And""" start="00:18:47.002" video="qanda-gypsum" id="subtitle"]] -[[!template text="""yeah, I look forward to working with all of you if you're""" start="00:18:51.663" video="qanda-gypsum" id="subtitle"]] -[[!template text="""interested. take it easy. Thanks so much for the talk and""" start="00:18:51.663" video="qanda-gypsum" id="subtitle"]] -[[!template text="""looking forward to seeing some of your progress as this""" start="00:18:59.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""moves forward, exciting space. We'll go ahead and leave the""" start="00:18:59.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""room open for you and thanks for offering to hang out and chat""" start="00:19:09.261" video="qanda-gypsum" id="subtitle"]] -[[!template text="""with other people that come by. Feel free to throw something""" start="00:19:09.261" video="qanda-gypsum" id="subtitle"]] -[[!template text="""in the chat if you want to remind people you're still here.""" start="00:19:15.025" video="qanda-gypsum" id="subtitle"]] -[[!template text="""Meanwhile, on the stream, we have moved along to our next""" start="00:19:19.557" video="qanda-gypsum" id="subtitle"]] -[[!template text="""talk on Rust, and that is just getting started. But again,""" start="00:19:19.557" video="qanda-gypsum" id="subtitle"]] -[[!template text="""we're continuing to record this, and I'll just keep an eye on""" start="00:19:25.283" video="qanda-gypsum" id="subtitle"]] -[[!template text="""it to stop the recording. Thank you. Thank you. It was""" start="00:19:25.283" video="qanda-gypsum" id="subtitle"]] -[[!template text="""awesome.""" start="00:19:33.352" video="qanda-gypsum" id="subtitle"]] -[[!template text="""So it seems like it's slowed down here for the Q&A. I don't see""" start="00:21:47.935" video="qanda-gypsum" id="subtitle"]] -[[!template text="""anybody else on BBB, so I'm going to go ahead and stop the""" start="00:21:50.638" video="qanda-gypsum" id="subtitle"]] -[[!template text="""recording. We can start it back up. I would say, yes, there's""" start="00:21:50.638" video="qanda-gypsum" id="subtitle"]] -[[!template text="""a lot of things you can do with this. You can handle""" start="00:21:55.282" video="qanda-gypsum" id="subtitle"]] -[[!template text="""processing. Yeah, I'm going to try and join over the chat for""" start="00:21:58.926" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the next talk. I'm not sure if I can do both big blue buttons at""" start="00:22:02.029" video="qanda-gypsum" id="subtitle"]] -[[!template text="""the same time. You should be able to just watch your mute""" start="00:22:08.635" video="qanda-gypsum" id="subtitle"]] -[[!template text="""settings and mute tab settings and whatever all you have to""" start="00:22:13.206" video="qanda-gypsum" id="subtitle"]] -[[!template text="""avoid bleed through. Okay.""" start="00:22:13.206" video="qanda-gypsum" id="subtitle"]] +
[[!template new="1" text="""Q: Why is it not feasible for the Emacs layer that interprets Emacs Lisp (the core in C) ot have a Scheme interpreter, instead of using Guile?""" start="00:17:25.880" video="qanda-gypsum" id="subtitle"]]
[[!template text="""Okay, why is it not feasible for the Emacs layer that""" start="00:17:25.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""interprets Emacs Lisp, the core in C, have a Scheme""" start="00:17:30.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""interpreter instead of using Guile? Let's see, I have to,""" start="00:17:34.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""okay. Emacs layer interprets Emacs Lisp, the core in C, have""" start="00:17:39.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""a Scheme interpreter instead of using Guile. Okay, so that,""" start="00:17:48.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the question xlarsx is asking, xlars, x, So Lars is asking,""" start="00:17:54.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""is it not feasible for there to be an""" start="00:17:59.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs layer that interprets Emacs Lisp have a scheme""" start="00:18:02.320" video="qanda-gypsum" id="subtitle"]] +[[!template text="""interpreter? This is Robin Templeton's project. And""" start="00:18:06.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""they're presenting later today. So check the roster and be""" start="00:18:33.080" video="qanda-gypsum" id="subtitle"]] +[[!template text="""sure to see that presentation because that's exactly what""" start="00:18:39.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Robin Templeton is doing. That's not what I'm doing though.""" start="00:18:45.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""I'm trying to create something in Scheme. But yes, there is""" start="00:18:52.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""an attempt to get an Scheme interpreter to run inside of""" start="00:18:57.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Emacs itself. And it has its own method of binding to Emacs""" start="00:19:02.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Lisp functions and translating data like Lisp structures""" start="00:19:07.160" video="qanda-gypsum" id="subtitle"]] +[[!template text="""between Guile Scheme and Emacs Lisp. Robin will explain all""" start="00:19:11.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""of that in their presentation.""" start="00:19:14.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""OK, I think I've got through all the questions on Etherpad.""" start="00:19:15.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""But I'm going to hang out here for a bit longer. And yeah, feel""" start="00:19:18.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""free to do a video chat with me or send me more questions on""" start="00:19:23.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Etherpad or here in the big blue button. And so I'm just going""" start="00:19:28.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""to hang out. And thanks for asking all your questions. And""" start="00:19:33.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""yeah, I look forward to working with all of you if you're""" start="00:21:49.120" video="qanda-gypsum" id="subtitle"]] +[[!template text="""interested. take it easy. Thanks so much for the talk and""" start="00:21:50.840" video="qanda-gypsum" id="subtitle"]] +[[!template text="""looking forward to seeing some of your progress as this""" start="00:21:51.800" video="qanda-gypsum" id="subtitle"]] +[[!template text="""moves forward, exciting space. We'll go ahead and leave the""" start="00:21:53.200" video="qanda-gypsum" id="subtitle"]] +[[!template text="""room open for you and thanks for offering to hang out and chat""" start="00:21:54.360" video="qanda-gypsum" id="subtitle"]] +[[!template text="""with other people that come by. Feel free to throw something""" start="00:21:54.880" video="qanda-gypsum" id="subtitle"]] +[[!template text="""in the chat if you want to remind people you're still here.""" start="00:21:55.640" video="qanda-gypsum" id="subtitle"]] +[[!template text="""Meanwhile, on the stream, we have moved along to our next""" start="00:21:56.720" video="qanda-gypsum" id="subtitle"]] +[[!template text="""talk on Rust, and that is just getting started. But again,""" start="00:21:57.920" video="qanda-gypsum" id="subtitle"]] +[[!template text="""we're continuing to record this, and I'll just keep an eye on""" start="00:21:59.600" video="qanda-gypsum" id="subtitle"]] +[[!template text="""it to stop the recording. Thank you. Thank you. It was""" start="00:22:00.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""awesome.""" start="00:22:01.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""So it seems like it's slowed down here for the Q&A. I don't see""" start="00:22:01.560" video="qanda-gypsum" id="subtitle"]] +[[!template text="""anybody else on BBB, so I'm going to go ahead and stop the""" start="00:22:03.960" video="qanda-gypsum" id="subtitle"]] +[[!template text="""recording. We can start it back up. I would say, yes, there's""" start="00:22:05.440" video="qanda-gypsum" id="subtitle"]] +[[!template text="""a lot of things you can do with this. You can handle""" start="00:22:08.480" video="qanda-gypsum" id="subtitle"]] +[[!template text="""processing. Yeah, I'm going to try and join over the chat for""" start="00:22:09.520" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the next talk. I'm not sure if I can do both big blue buttons at""" start="00:22:11.240" video="qanda-gypsum" id="subtitle"]] +[[!template text="""the same time. You should be able to just watch your mute""" start="00:22:14.680" video="qanda-gypsum" id="subtitle"]] +[[!template text="""settings and mute tab settings and whatever all you have to""" start="00:22:15.760" video="qanda-gypsum" id="subtitle"]] +[[!template text="""avoid bleed through. Okay.""" start="00:22:19.160" video="qanda-gypsum" id="subtitle"]]
Questions or comments? Please e-mail [ramin.honary@gmail.com](mailto:ramin.honary@gmail.com?subject=Comment%20for%20EmacsConf%202023%20gypsum%3A%20Gypsum%3A%20my%20clone%20of%20Emacs%20and%20ELisp%20written%20in%20Scheme) diff --git a/2024/info/gypsum-before.md b/2024/info/gypsum-before.md index ae5c0975..7f437b35 100644 --- a/2024/info/gypsum-before.md +++ b/2024/info/gypsum-before.md @@ -9,20 +9,20 @@ Status: TO_CAPTION_QA # Talk -
Duration: 24:36 minutes
+
Duration: 24:36 minutes
# Q&A
[[!template id="chapters" vidid="qanda-gypsum" data=""" -03:09.370 Q: I'm curious to know how the hell guile-emacs deals with all of the dynamically scoped modules out there. Is there any effort to automatically modularize and namespace stuff? -05:23.646 Q: Would it be possible to support a GUI toolkit other than GTK? -06:45.257 Q: Do you plan to provide improvements to Elisp as a language, or is the focus on a compatibility layer to facilitate doing all new extensions, etc. in Scheme? -08:29.673 Q: Can we consider a translator like utility to convert elisp to scheme, once guile-emacs becomes a reality? -10:54.390 Q: Why is being able to interpret all of \`init.el\` an useful goal? -12:08.539 Q: What is the plan to handle elisp packages that depend on 3rd party/external libraries? (libgit/magit or rg/ripgrep)? -15:21.112 Q: Not really a question, but how about Schemacs as a name? -16:45.931 Q: Why is it not feasible for the Emacs layer that interprets Emacs Lisp (the core in C) ot have a Scheme interpreter, instead of using Guile? - -"""]]
Listen to just the audio:
Duration: 23:38 minutes
+03:14.320 Q: I'm curious to know how the hell guile-emacs deals with all of the dynamically scoped modules out there. Is there any effort to automatically modularize and namespace stuff? +05:23.640 Q: Would it be possible to support a GUI toolkit other than GTK? +06:46.040 Q: Do you plan to provide improvements to Elisp as a language, or is the focus on a compatibility layer to facilitate doing all new extensions, etc. in Scheme? +08:19.440 Q: Can we consider a translator like utility to convert elisp to scheme, once guile-emacs becomes a reality? +10:50.600 Q: Why is being able to interpret all of \`init.el\` an useful goal? +12:02.280 Q: What is the plan to handle elisp packages that depend on 3rd party/external libraries? (libgit/magit or rg/ripgrep)? +15:55.280 Q: Not really a question, but how about Schemacs as a name? +17:25.880 Q: Why is it not feasible for the Emacs layer that interprets Emacs Lisp (the core in C) ot have a Scheme interpreter, instead of using Guile? + +"""]]
Listen to just the audio:
Duration: 23:38 minutes
# Description \ No newline at end of file diff --git a/2024/info/hyperbole-before.md b/2024/info/hyperbole-before.md index 24e259b2..4f40ce4a 100644 --- a/2024/info/hyperbole-before.md +++ b/2024/info/hyperbole-before.md @@ -20,7 +20,7 @@ Status: TO_CAPTION_QA 11:19.720 Select a thing 12:33.818 Web search -"""]]
Duration: 14:10 minutes
+"""]]
Duration: 14:10 minutes
# Q&A @@ -30,6 +30,6 @@ Status: TO_CAPTION_QA 07:09.972 Q: What is a recent tool that you find exciting to think about using in combination with Hyperbole, or would like to suggest using in combination with it? 10:00.255 On Ihor as the new maintainer for Org Mode -"""]]
Listen to just the audio:
Duration: 21:56 minutes
+"""]]
Listen to just the audio:
Duration: 21:56 minutes
# Description \ No newline at end of file diff --git a/2024/info/hyperdrive-before.md b/2024/info/hyperdrive-before.md index 9b73f69f..1f1493d8 100644 --- a/2024/info/hyperdrive-before.md +++ b/2024/info/hyperdrive-before.md @@ -3,31 +3,13 @@ Format: 21-min talk ; Q&A: BigBlueButton conference room Status: TO_CAPTION_QA - - -# Talk - -
[[!template id="chapters" vidid="mainVideo-hyperdrive" data=""" -00:01.000 Welcome -01:34.700 `hyperdrive.el` quick start installation -03:23.400 open a file on a hyperdrive -04:02.559 marking a hyperdrive as trusted safe -04:30.739 giving hyperdrives petnames -05:15.259 hyperdrive peer graphs -07:19.879 explaination for blockers -09:01.839 wingsuit-flying-grand-canyon-point-of-view-NOT-CLICKBAIT.mp4 -12:57.480 how to new hyperdrive public key -14:42.359 bound keys for hyperdrive's transient menu -15:27.080 `hyperdrive-org-transclusion' installation -17:02.799 inserting link to a hyperdrive stored file -"""]]
Duration: 20:25 minutes
- +# Talk - +
Duration: 20:25 minutes
# Q&A @@ -37,6 +19,6 @@ Status: TO_CAPTION_QA 07:31.064 Q: blocklist or whitelist so I can make them containing useful information for only me while also being useful with in a public sense 11:41.024 Q: Could you comment on the "visualization" thing, (org visualization), and your experience with this type of content in buffers and the various possibilities (svg, etc.)? -"""]]
Listen to just the audio:
Duration: 22:34 minutes
+"""]]
Listen to just the audio:
Duration: 22:34 minutes
# Description - + \ No newline at end of file diff --git a/2024/info/julia-after.md b/2024/info/julia-after.md index 9a2d879c..9a498298 100644 --- a/2024/info/julia-after.md +++ b/2024/info/julia-after.md @@ -212,122 +212,122 @@

Q&A transcript (unedited)

-
[[!template new="1" text="""Q: Do you have any suggestions for interactive debugging of Julia code in Emacs?""" start="00:00:00.089" video="qanda-julia" id="subtitle"]]
[[!template text="""... answer to that. I, I think the infrastructure for an""" start="00:00:00.089" video="qanda-julia" id="subtitle"]] -[[!template text="""ecosystem in Julia in general is as mature as other""" start="00:00:01.509" video="qanda-julia" id="subtitle"]] -[[!template text="""languages, and even debugger infiltrator themselves are""" start="00:00:01.509" video="qanda-julia" id="subtitle"]] -[[!template text="""not particularly well developed. And so I don't think""" start="00:00:01.509" video="qanda-julia" id="subtitle"]] -[[!template text="""there's much we can do about that right now. I think that it's""" start="00:00:15.853" video="qanda-julia" id="subtitle"]] -[[!template text="""unfortunate that most of the development for these type of""" start="00:00:21.570" video="qanda-julia" id="subtitle"]] -[[!template text="""tools is tightly linked to VS code. But even there, I don't""" start="00:00:21.570" video="qanda-julia" id="subtitle"]] -[[!template text="""think that there's much done in terms of interactive""" start="00:00:29.218" video="qanda-julia" id="subtitle"]] -[[!template text="""debugging. So I, yeah, I think this has to be worked on mostly""" start="00:00:29.218" video="qanda-julia" id="subtitle"]] -[[!template text="""on the Julia side first. And then probably Emacs can get""" start="00:00:36.866" video="qanda-julia" id="subtitle"]] -[[!template text="""something out of that. I know that there's development in""" start="00:00:43.820" video="qanda-julia" id="subtitle"]] -[[!template text="""debugger.jl itself for future releases to make it at least""" start="00:00:49.183" video="qanda-julia" id="subtitle"]] -[[!template text="""faster and more stable. But yeah, I think we're not there as""" start="00:00:49.183" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia community itself. So let alone Emacs, integration""" start="00:00:58.809" video="qanda-julia" id="subtitle"]] -[[!template text="""with Emacs. The way I personally debug is mostly using,""" start="00:01:04.192" video="qanda-julia" id="subtitle"]] -[[!template text="""well, debugger and infiltrator with Julia REPL mode in""" start="00:01:08.286" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Do you have any suggestions for interactive debugging of Julia code in Emacs?""" start="00:00:00.000" video="qanda-julia" id="subtitle"]]
[[!template text="""... answer to that. I, I think the infrastructure for an""" start="00:00:00.000" video="qanda-julia" id="subtitle"]] +[[!template text="""ecosystem in Julia in general is as mature as other""" start="00:00:05.320" video="qanda-julia" id="subtitle"]] +[[!template text="""languages, and even debugger infiltrator themselves are""" start="00:00:08.600" video="qanda-julia" id="subtitle"]] +[[!template text="""not particularly well developed. And so I don't think""" start="00:00:12.560" video="qanda-julia" id="subtitle"]] +[[!template text="""there's much we can do about that right now. I think that it's""" start="00:00:17.520" video="qanda-julia" id="subtitle"]] +[[!template text="""unfortunate that most of the development for these type of""" start="00:00:21.520" video="qanda-julia" id="subtitle"]] +[[!template text="""tools is tightly linked to VS code. But even there, I don't""" start="00:00:26.000" video="qanda-julia" id="subtitle"]] +[[!template text="""think that there's much done in terms of interactive""" start="00:00:31.760" video="qanda-julia" id="subtitle"]] +[[!template text="""debugging. So I, yeah, I think this has to be worked on mostly""" start="00:00:35.720" video="qanda-julia" id="subtitle"]] +[[!template text="""on the Julia side first. And then probably Emacs can get""" start="00:00:42.360" video="qanda-julia" id="subtitle"]] +[[!template text="""something out of that. I know that there's development in""" start="00:00:47.520" video="qanda-julia" id="subtitle"]] +[[!template text="""debugger.jl itself for future releases to make it at least""" start="00:00:51.240" video="qanda-julia" id="subtitle"]] +[[!template text="""faster and more stable. But yeah, I think we're not there as""" start="00:00:55.560" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia community itself. So let alone Emacs, integration""" start="00:01:01.840" video="qanda-julia" id="subtitle"]] +[[!template text="""with Emacs. The way I personally debug is mostly using,""" start="00:01:06.880" video="qanda-julia" id="subtitle"]] +[[!template text="""well, debugger and infiltrator with Julia REPL mode in""" start="00:01:11.240" video="qanda-julia" id="subtitle"]] -
[[!template new="1" text="""Q: Can you call out something that Julia has that Emacs does not, and which could benefit Emacs?""" start="00:01:08.286" video="qanda-julia" id="subtitle"]]
[[!template text="""Emacs. The second question, can you call out something that""" start="00:01:08.286" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia has that Emacs does not and which could benefit Emacs?""" start="00:01:18.009" video="qanda-julia" id="subtitle"]] -[[!template text="""Nothing stands out to me except the usual multi-threading""" start="00:01:26.852" video="qanda-julia" id="subtitle"]] -[[!template text="""and things like this. I don't necessarily see something""" start="00:01:28.848" video="qanda-julia" id="subtitle"]] -[[!template text="""that Julia has going on that DMX doesn't have, but I see some""" start="00:01:33.432" video="qanda-julia" id="subtitle"]] -[[!template text="""differences and approaches that I think are important,""" start="00:01:33.432" video="qanda-julia" id="subtitle"]] -[[!template text="""like the community. I think Julia is a very active and tight""" start="00:01:33.432" video="qanda-julia" id="subtitle"]] -[[!template text="""community. Julia uses Slack and is very, very active. I""" start="00:01:47.384" video="qanda-julia" id="subtitle"]] -[[!template text="""think he might say something like that, but it's maybe more""" start="00:01:54.093" video="qanda-julia" id="subtitle"]] -[[!template text="""on Reddit, IRC. JuliaCon is big and brings together lots and""" start="00:01:54.093" video="qanda-julia" id="subtitle"]] -[[!template text="""lots of people. And I think the sense of community is really""" start="00:01:59.078" video="qanda-julia" id="subtitle"]] -[[!template text="""powerful. It's very easy to essentially meet people that""" start="00:02:03.221" video="qanda-julia" id="subtitle"]] -[[!template text="""are interested in what we're building and interested in""" start="00:02:06.364" video="qanda-julia" id="subtitle"]] -[[!template text="""what we're doing and interested in Julian, our, you know,""" start="00:02:06.364" video="qanda-julia" id="subtitle"]] -[[!template text="""hacker spirit. I think Emacs is a very strong community.""" start="00:02:06.364" video="qanda-julia" id="subtitle"]] -[[!template text="""We're here on a Saturday talking about Emacs, which again""" start="00:02:21.228" video="qanda-julia" id="subtitle"]] -[[!template text="""proves that we are doing this. But I'd like to emphasize that""" start="00:02:21.228" video="qanda-julia" id="subtitle"]] -[[!template text="""the community is a really important aspect in Julia that I""" start="00:02:27.192" video="qanda-julia" id="subtitle"]] -[[!template text="""think we should double down on our side. The next question is""" start="00:02:27.192" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Can you call out something that Julia has that Emacs does not, and which could benefit Emacs?""" start="00:01:15.200" video="qanda-julia" id="subtitle"]]
[[!template text="""Emacs. The second question, can you call out something that""" start="00:01:15.200" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia has that Emacs does not and which could benefit Emacs?""" start="00:01:21.680" video="qanda-julia" id="subtitle"]] +[[!template text="""Nothing stands out to me except the usual multi-threading""" start="00:01:26.840" video="qanda-julia" id="subtitle"]] +[[!template text="""and things like this. I don't necessarily see something""" start="00:01:31.880" video="qanda-julia" id="subtitle"]] +[[!template text="""that Julia has going on that DMX doesn't have, but I see some""" start="00:01:36.120" video="qanda-julia" id="subtitle"]] +[[!template text="""differences and approaches that I think are important,""" start="00:01:42.480" video="qanda-julia" id="subtitle"]] +[[!template text="""like the community. I think Julia is a very active and tight""" start="00:01:45.840" video="qanda-julia" id="subtitle"]] +[[!template text="""community. Julia uses Slack and is very, very active. I""" start="00:01:49.760" video="qanda-julia" id="subtitle"]] +[[!template text="""think he might say something like that, but it's maybe more""" start="00:01:54.160" video="qanda-julia" id="subtitle"]] +[[!template text="""on Reddit, IRC. JuliaCon is big and brings together lots and""" start="00:01:56.560" video="qanda-julia" id="subtitle"]] +[[!template text="""lots of people. And I think the sense of community is really""" start="00:02:01.800" video="qanda-julia" id="subtitle"]] +[[!template text="""powerful. It's very easy to essentially meet people that""" start="00:02:05.160" video="qanda-julia" id="subtitle"]] +[[!template text="""are interested in what we're building and interested in""" start="00:02:10.480" video="qanda-julia" id="subtitle"]] +[[!template text="""what we're doing and interested in Julian, our, you know,""" start="00:02:12.920" video="qanda-julia" id="subtitle"]] +[[!template text="""hacker spirit. I think Emacs is a very strong community.""" start="00:02:16.000" video="qanda-julia" id="subtitle"]] +[[!template text="""We're here on a Saturday talking about Emacs, which again""" start="00:02:21.240" video="qanda-julia" id="subtitle"]] +[[!template text="""proves that we are doing this. But I'd like to emphasize that""" start="00:02:24.280" video="qanda-julia" id="subtitle"]] +[[!template text="""the community is a really important aspect in Julia that I""" start="00:02:29.680" video="qanda-julia" id="subtitle"]] +[[!template text="""think we should double down on our side. The next question is""" start="00:02:33.640" video="qanda-julia" id="subtitle"]] -
[[!template new="1" text="""Q: Is there a way to use lisp syntax with Julia, like hy for python or lisp flavoured erlang?""" start="00:02:36.797" video="qanda-julia" id="subtitle"]]
[[!template text="""about Lisp syntax with Julia, like what we can do in Python.""" start="00:02:36.797" video="qanda-julia" id="subtitle"]] -[[!template text="""I don't think that's, I don't, I am not aware of any package""" start="00:02:48.038" video="qanda-julia" id="subtitle"]] -[[!template text="""that does that. I would bet that there's something there. I""" start="00:02:48.038" video="qanda-julia" id="subtitle"]] -[[!template text="""think that that's possible. Indeed, there used to be a Lisp""" start="00:02:56.722" video="qanda-julia" id="subtitle"]] -[[!template text="""interpreter in Julia itself until the latest release. The""" start="00:02:59.243" video="qanda-julia" id="subtitle"]] -[[!template text="""syntax parsing was done with a Lisp, it was called TemtoList""" start="00:03:07.647" video="qanda-julia" id="subtitle"]] -[[!template text="""indeed. I think this got rid, get rid of this for our more""" start="00:03:07.647" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia-based solution that is faster and with better code""" start="00:03:16.124" video="qanda-julia" id="subtitle"]] -[[!template text="""provenance. I think that it should be possible to use the""" start="00:03:16.124" video="qanda-julia" id="subtitle"]] -[[!template text="""metaprogramming features in Julia to change the structure""" start="00:03:25.430" video="qanda-julia" id="subtitle"]] -[[!template text="""of your syntax to be a Lispy syntax. I do want to emphasize""" start="00:03:25.430" video="qanda-julia" id="subtitle"]] -[[!template text="""that Julia is heavily inspired by Lisp, so I wouldn't be""" start="00:03:36.238" video="qanda-julia" id="subtitle"]] -[[!template text="""surprised if if something like this were possible.""" start="00:03:36.238" video="qanda-julia" id="subtitle"]] -[[!template text="""I have tried Julia Snail.""" start="00:03:49.309" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Is there a way to use lisp syntax with Julia, like hy for python or lisp flavoured erlang?""" start="00:02:38.160" video="qanda-julia" id="subtitle"]]
[[!template text="""about Lisp syntax with Julia, like what we can do in Python.""" start="00:02:38.160" video="qanda-julia" id="subtitle"]] +[[!template text="""I don't think that's, I don't, I am not aware of any package""" start="00:02:46.520" video="qanda-julia" id="subtitle"]] +[[!template text="""that does that. I would bet that there's something there. I""" start="00:02:52.360" video="qanda-julia" id="subtitle"]] +[[!template text="""think that that's possible. Indeed, there used to be a Lisp""" start="00:02:56.880" video="qanda-julia" id="subtitle"]] +[[!template text="""interpreter in Julia itself until the latest release. The""" start="00:03:01.520" video="qanda-julia" id="subtitle"]] +[[!template text="""syntax parsing was done with a Lisp, it was called TemtoList""" start="00:03:08.080" video="qanda-julia" id="subtitle"]] +[[!template text="""indeed. I think this got rid, get rid of this for our more""" start="00:03:12.040" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia-based solution that is faster and with better code""" start="00:03:18.680" video="qanda-julia" id="subtitle"]] +[[!template text="""provenance. I think that it should be possible to use the""" start="00:03:23.040" video="qanda-julia" id="subtitle"]] +[[!template text="""metaprogramming features in Julia to change the structure""" start="00:03:28.600" video="qanda-julia" id="subtitle"]] +[[!template text="""of your syntax to be a Lispy syntax. I do want to emphasize""" start="00:03:33.320" video="qanda-julia" id="subtitle"]] +[[!template text="""that Julia is heavily inspired by Lisp, so I wouldn't be""" start="00:03:38.160" video="qanda-julia" id="subtitle"]] +[[!template text="""surprised if if something like this were possible.""" start="00:03:43.880" video="qanda-julia" id="subtitle"]] +[[!template text="""I have tried Julia Snail.""" start="00:03:49.240" video="qanda-julia" id="subtitle"]] -
[[!template new="1" text="""Q: Have you tried the Julia Snail package for Emacs? It tries to be like SLY/SLIME for Common Lisp.""" start="00:03:51.168" video="qanda-julia" id="subtitle"]]
[[!template text="""So the next question is about Julia""" start="00:03:51.168" video="qanda-julia" id="subtitle"]] -[[!template text="""Snail. I found Julia REPL to be a little bit easier to set up""" start="00:03:51.270" video="qanda-julia" id="subtitle"]] -[[!template text="""and use. So I just settled on that. I should maybe revisit""" start="00:03:53.312" video="qanda-julia" id="subtitle"]] -[[!template text="""that. In particular, I use the Julia REPL with the vterm""" start="00:04:00.918" video="qanda-julia" id="subtitle"]] -[[!template text="""backend, which essentially makes a companion REPL to my""" start="00:04:03.720" video="qanda-julia" id="subtitle"]] -[[!template text="""scripts. And that works for me. I do think that the tooling""" start="00:04:03.720" video="qanda-julia" id="subtitle"]] -[[!template text="""uh, could be improved. I think there is definitely much room""" start="00:04:15.638" video="qanda-julia" id="subtitle"]] -[[!template text="""and I would like to see improvement in that area. Um, and, uh,""" start="00:04:17.399" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Have you tried the Julia Snail package for Emacs? It tries to be like SLY/SLIME for Common Lisp.""" start="00:03:51.240" video="qanda-julia" id="subtitle"]]
[[!template text="""So the next question is about Julia""" start="00:03:51.240" video="qanda-julia" id="subtitle"]] +[[!template text="""Snail. I found Julia REPL to be a little bit easier to set up""" start="00:03:54.400" video="qanda-julia" id="subtitle"]] +[[!template text="""and use. So I just settled on that. I should maybe revisit""" start="00:03:58.200" video="qanda-julia" id="subtitle"]] +[[!template text="""that. In particular, I use the Julia REPL with the vterm""" start="00:04:02.840" video="qanda-julia" id="subtitle"]] +[[!template text="""backend, which essentially makes a companion REPL to my""" start="00:04:06.000" video="qanda-julia" id="subtitle"]] +[[!template text="""scripts. And that works for me. I do think that the tooling""" start="00:04:10.960" video="qanda-julia" id="subtitle"]] +[[!template text="""uh, could be improved. I think there is definitely much room""" start="00:04:15.440" video="qanda-julia" id="subtitle"]] +[[!template text="""and I would like to see improvement in that area. Um, and, uh,""" start="00:04:19.240" video="qanda-julia" id="subtitle"]] -
[[!template new="1" text="""Q: Is there a data inspector for a Julia REPL available that you can use in Emacs?""" start="00:04:22.940" video="qanda-julia" id="subtitle"]]
[[!template text="""so we have data inspector for Julia REPL.""" start="00:04:22.940" video="qanda-julia" id="subtitle"]] -[[!template text="""I don't think so. I don't, is there any data inspector""" start="00:04:32.043" video="qanda-julia" id="subtitle"]] -[[!template text="""in for, for the Julia REPL that we can use in Emacs?""" start="00:04:34.804" video="qanda-julia" id="subtitle"]] -[[!template text="""I'm not sure. I don't think so.""" start="00:04:43.223" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Is there a data inspector for a Julia REPL available that you can use in Emacs?""" start="00:04:26.080" video="qanda-julia" id="subtitle"]]
[[!template text="""so we have data inspector for Julia REPL.""" start="00:04:26.080" video="qanda-julia" id="subtitle"]] +[[!template text="""I don't think so. I don't, is there any data inspector""" start="00:04:31.640" video="qanda-julia" id="subtitle"]] +[[!template text="""in for, for the Julia REPL that we can use in Emacs?""" start="00:04:37.280" video="qanda-julia" id="subtitle"]] +[[!template text="""I'm not sure. I don't think so.""" start="00:04:40.440" video="qanda-julia" id="subtitle"]] [[!template text="""I think the way I look at data is""" start="00:04:44.840" video="qanda-julia" id="subtitle"]] -[[!template text="""essentially ignoring Emacs when encoded. It's just using the""" start="00:04:47.840" video="qanda-julia" id="subtitle"]] +[[!template text="""essentially ignoring Emacs when encoded. It's just using the""" start="00:04:47.800" video="qanda-julia" id="subtitle"]] [[!template text="""REPL. And again, with Julia REPL. So I'm not aware of any""" start="00:04:50.520" video="qanda-julia" id="subtitle"]] -[[!template text="""specialized tool And again, maybe this is, again, a good""" start="00:04:54.760" video="qanda-julia" id="subtitle"]] -[[!template text="""moment to emphasize that tooling, the Julia community""" start="00:04:58.652" video="qanda-julia" id="subtitle"]] -[[!template text="""clusters around VS Code. And there is tools like the, pretty""" start="00:04:58.652" video="qanda-julia" id="subtitle"]] -[[!template text="""much all the work with VS Code, unfortunately. And while""" start="00:05:06.315" video="qanda-julia" id="subtitle"]] -[[!template text="""there's a very, very decent Julia mode and Julia repo mode""" start="00:05:12.578" video="qanda-julia" id="subtitle"]] -[[!template text="""and Julia snail, there's definitely, definitely room for""" start="00:05:12.578" video="qanda-julia" id="subtitle"]] -[[!template text="""improvement.""" start="00:05:12.578" video="qanda-julia" id="subtitle"]] +[[!template text="""specialized tool And again, maybe this is, again, a good""" start="00:04:56.840" video="qanda-julia" id="subtitle"]] +[[!template text="""moment to emphasize that tooling, the Julia community""" start="00:05:00.480" video="qanda-julia" id="subtitle"]] +[[!template text="""clusters around VS Code. And there is tools like the, pretty""" start="00:05:04.280" video="qanda-julia" id="subtitle"]] +[[!template text="""much all the work with VS Code, unfortunately. And while""" start="00:05:09.080" video="qanda-julia" id="subtitle"]] +[[!template text="""there's a very, very decent Julia mode and Julia repo mode""" start="00:05:14.200" video="qanda-julia" id="subtitle"]] +[[!template text="""and Julia snail, there's definitely, definitely room for""" start="00:05:17.760" video="qanda-julia" id="subtitle"]] +[[!template text="""improvement.""" start="00:05:21.440" video="qanda-julia" id="subtitle"]] -
[[!template new="1" text="""Q: Have you tried literate programming Julia (using Org babel or some other means) in Emacs?""" start="00:05:24.443" video="qanda-julia" id="subtitle"]]
[[!template text="""Next, we have a question about literate programming in""" start="00:05:24.443" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia. I haven't done much of it with Org Babel or""" start="00:05:24.443" video="qanda-julia" id="subtitle"]] -[[!template text="""anything else. I haven't done much of it. I can say that Julia""" start="00:05:29.505" video="qanda-julia" id="subtitle"]] -[[!template text="""has developed a new iteration of notebooks called Pluto.""" start="00:05:35.827" video="qanda-julia" id="subtitle"]] -[[!template text="""Here I'm thinking about Jupyter notebooks. The Pluto""" start="00:05:46.090" video="qanda-julia" id="subtitle"]] -[[!template text="""notebooks for Julia try to remove a bunch of the pain points""" start="00:05:51.021" video="qanda-julia" id="subtitle"]] -[[!template text="""that Jupyter notebooks have, meaning you cannot easily""" start="00:05:51.021" video="qanda-julia" id="subtitle"]] -[[!template text="""commit them to Git or things like this.""" start="00:05:51.021" video="qanda-julia" id="subtitle"]] -[[!template text="""I haven't used them, but I know some people are very fond of""" start="00:06:06.450" video="qanda-julia" id="subtitle"]] -[[!template text="""them. And so I think that that's what some of the Julia""" start="00:06:06.450" video="qanda-julia" id="subtitle"]] -[[!template text="""community would use for notebooks. And I think they can""" start="00:06:09.872" video="qanda-julia" id="subtitle"]] -[[!template text="""interact with Emacs with no problem. And that would be a form""" start="00:06:15.315" video="qanda-julia" id="subtitle"]] -[[!template text="""of later programming. But if you can do it in Python, you can""" start="00:06:20.974" video="qanda-julia" id="subtitle"]] -[[!template text="""do it in Julia. I think there is no reason. And actually, you""" start="00:06:24.015" video="qanda-julia" id="subtitle"]] -[[!template text="""can take advantage of all this just-in-time or""" start="00:06:30.617" video="qanda-julia" id="subtitle"]] -[[!template text="""just-out-of-time compilation by keeping the same""" start="00:06:30.617" video="qanda-julia" id="subtitle"]] -[[!template text="""session. So I think it will be definitely a nice use case. So""" start="00:06:30.617" video="qanda-julia" id="subtitle"]] -[[!template text="""these are the questions that I see here. I'm going to scroll""" start="00:06:44.681" video="qanda-julia" id="subtitle"]] -[[!template text="""through the comments and see if there's something that I""" start="00:06:48.561" video="qanda-julia" id="subtitle"]] -[[!template text="""should say about comments. I'm excited people want to learn""" start="00:06:48.561" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia. I have to say that if I want to do GPU computing""" start="00:06:56.228" video="qanda-julia" id="subtitle"]] -[[!template text="""nowadays, I find it much easier to do it with Julia than with""" start="00:06:58.990" video="qanda-julia" id="subtitle"]] -[[!template text="""CUDA. So I encourage people to look into that. And I do,""" start="00:06:58.990" video="qanda-julia" id="subtitle"]] -[[!template text="""again, I would like to share what makes me excited about""" start="00:07:11.758" video="qanda-julia" id="subtitle"]] -[[!template text="""Emacs, about this being open, being collaborative, being""" start="00:07:11.758" video="qanda-julia" id="subtitle"]] -[[!template text="""respectable with documentation is something that I find in""" start="00:07:11.758" video="qanda-julia" id="subtitle"]] -[[!template text="""Julia. So I think people that are excited about the same""" start="00:07:11.758" video="qanda-julia" id="subtitle"]] -[[!template text="""features will find a little bit of joy in working with Julia.""" start="00:07:27.367" video="qanda-julia" id="subtitle"]] -[[!template text="""I think I addressed what I have here. I don't know if there's""" start="00:07:38.214" video="qanda-julia" id="subtitle"]] -[[!template text="""anything else that I should add.""" start="00:07:40.189" video="qanda-julia" id="subtitle"]] -[[!template text="""It took me a minute to unmute there.""" start="00:07:51.718" video="qanda-julia" id="subtitle"]] -[[!template text="""No, I think that was awesome. And thank you so much.""" start="00:07:54.040" video="qanda-julia" id="subtitle"]] -[[!template text="""I guess I thought it would""" start="00:07:58.400" video="qanda-julia" id="subtitle"]] -[[!template text="""collapse that shared area on BBB, my mistake, on the stream,""" start="00:08:00.400" video="qanda-julia" id="subtitle"]] -[[!template text="""or I would have left it open. But in any case, no, I thought""" start="00:08:06.560" video="qanda-julia" id="subtitle"]] -[[!template text="""that was great. You did a great job of responding to all the""" start="00:08:12.400" video="qanda-julia" id="subtitle"]] +
[[!template new="1" text="""Q: Have you tried literate programming Julia (using Org babel or some other means) in Emacs?""" start="00:05:24.360" video="qanda-julia" id="subtitle"]]
[[!template text="""Next, we have a question about literate programming in""" start="00:05:24.360" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia. I haven't done much of it with Org Babel or""" start="00:05:27.760" video="qanda-julia" id="subtitle"]] +[[!template text="""anything else. I haven't done much of it. I can say that Julia""" start="00:05:32.440" video="qanda-julia" id="subtitle"]] +[[!template text="""has developed a new iteration of notebooks called Pluto.""" start="00:05:37.080" video="qanda-julia" id="subtitle"]] +[[!template text="""Here I'm thinking about Jupyter notebooks. The Pluto""" start="00:05:40.720" video="qanda-julia" id="subtitle"]] +[[!template text="""notebooks for Julia try to remove a bunch of the pain points""" start="00:05:47.120" video="qanda-julia" id="subtitle"]] +[[!template text="""that Jupyter notebooks have, meaning you cannot easily""" start="00:05:55.360" video="qanda-julia" id="subtitle"]] +[[!template text="""commit them to Git or things like this.""" start="00:06:00.440" video="qanda-julia" id="subtitle"]] +[[!template text="""I haven't used them, but I know some people are very fond of""" start="00:06:03.640" video="qanda-julia" id="subtitle"]] +[[!template text="""them. And so I think that that's what some of the Julia""" start="00:06:09.280" video="qanda-julia" id="subtitle"]] +[[!template text="""community would use for notebooks. And I think they can""" start="00:06:13.560" video="qanda-julia" id="subtitle"]] +[[!template text="""interact with Emacs with no problem. And that would be a form""" start="00:06:16.880" video="qanda-julia" id="subtitle"]] +[[!template text="""of later programming. But if you can do it in Python, you can""" start="00:06:22.240" video="qanda-julia" id="subtitle"]] +[[!template text="""do it in Julia. I think there is no reason. And actually, you""" start="00:06:26.880" video="qanda-julia" id="subtitle"]] +[[!template text="""can take advantage of all this just-in-time or""" start="00:06:32.120" video="qanda-julia" id="subtitle"]] +[[!template text="""just-out-of-time compilation by keeping the same""" start="00:06:35.840" video="qanda-julia" id="subtitle"]] +[[!template text="""session. So I think it will be definitely a nice use case. So""" start="00:06:38.240" video="qanda-julia" id="subtitle"]] +[[!template text="""these are the questions that I see here. I'm going to scroll""" start="00:06:45.200" video="qanda-julia" id="subtitle"]] +[[!template text="""through the comments and see if there's something that I""" start="00:06:49.200" video="qanda-julia" id="subtitle"]] +[[!template text="""should say about comments. I'm excited people want to learn""" start="00:06:52.760" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia. I have to say that if I want to do GPU computing""" start="00:06:57.320" video="qanda-julia" id="subtitle"]] +[[!template text="""nowadays, I find it much easier to do it with Julia than with""" start="00:07:02.520" video="qanda-julia" id="subtitle"]] +[[!template text="""CUDA. So I encourage people to look into that. And I do,""" start="00:07:06.400" video="qanda-julia" id="subtitle"]] +[[!template text="""again, I would like to share what makes me excited about""" start="00:07:11.760" video="qanda-julia" id="subtitle"]] +[[!template text="""Emacs, about this being open, being collaborative, being""" start="00:07:19.360" video="qanda-julia" id="subtitle"]] +[[!template text="""respectable with documentation is something that I find in""" start="00:07:23.800" video="qanda-julia" id="subtitle"]] +[[!template text="""Julia. So I think people that are excited about the same""" start="00:07:26.400" video="qanda-julia" id="subtitle"]] +[[!template text="""features will find a little bit of joy in working with Julia.""" start="00:07:31.000" video="qanda-julia" id="subtitle"]] +[[!template text="""I think I addressed what I have here. I don't know if there's""" start="00:07:35.280" video="qanda-julia" id="subtitle"]] +[[!template text="""anything else that I should add.""" start="00:07:42.000" video="qanda-julia" id="subtitle"]] +[[!template text="""It took me a minute to unmute there.""" start="00:07:43.560" video="qanda-julia" id="subtitle"]] +[[!template text="""No, I think that was awesome. And thank you so much.""" start="00:07:52.880" video="qanda-julia" id="subtitle"]] +[[!template text="""I guess I thought it would""" start="00:07:57.520" video="qanda-julia" id="subtitle"]] +[[!template text="""collapse that shared area on BBB, my mistake, on the stream,""" start="00:08:00.120" video="qanda-julia" id="subtitle"]] +[[!template text="""or I would have left it open. But in any case, no, I thought""" start="00:08:06.280" video="qanda-julia" id="subtitle"]] +[[!template text="""that was great. You did a great job of responding to all the""" start="00:08:12.360" video="qanda-julia" id="subtitle"]] [[!template text="""questions and comments. And thank you again so much for your""" start="00:08:15.080" video="qanda-julia" id="subtitle"]] -[[!template text="""talk and getting us all excited to learn Julia. Thank you.""" start="00:08:17.880" video="qanda-julia" id="subtitle"]] -[[!template text="""Enjoy EmacsConf. And again, thanks so much for attending,""" start="00:08:24.094" video="qanda-julia" id="subtitle"]] -[[!template text="""for being EmacsConf. Thank you.""" start="00:08:25.335" video="qanda-julia" id="subtitle"]] +[[!template text="""talk and getting us all excited to learn Julia. Thank you.""" start="00:08:17.840" video="qanda-julia" id="subtitle"]] +[[!template text="""Enjoy EmacsConf. And again, thanks so much for attending,""" start="00:08:23.200" video="qanda-julia" id="subtitle"]] +[[!template text="""for being EmacsConf. Thank you.""" start="00:08:27.760" video="qanda-julia" id="subtitle"]]
Questions or comments? Please e-mail [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Comment%20for%20EmacsConf%202023%20julia%3A%20Exploring%20shared%20philosophies%20in%20Julia%20and%20Emacs) diff --git a/2024/info/julia-before.md b/2024/info/julia-before.md index cbab3774..e9d43975 100644 --- a/2024/info/julia-before.md +++ b/2024/info/julia-before.md @@ -9,18 +9,18 @@ Status: TO_CAPTION_QA # Talk -
Duration: 09:17 minutes
+
Duration: 09:17 minutes
# Q&A
[[!template id="chapters" vidid="qanda-julia" data=""" -00:00.089 Q: Do you have any suggestions for interactive debugging of Julia code in Emacs? -01:08.286 Q: Can you call out something that Julia has that Emacs does not, and which could benefit Emacs? -02:36.797 Q: Is there a way to use lisp syntax with Julia, like hy for python or lisp flavoured erlang? -03:51.168 Q: Have you tried the Julia Snail package for Emacs? It tries to be like SLY/SLIME for Common Lisp. -04:22.940 Q: Is there a data inspector for a Julia REPL available that you can use in Emacs? -05:24.443 Q: Have you tried literate programming Julia (using Org babel or some other means) in Emacs? - -"""]]
Listen to just the audio:
+00:00.000 Q: Do you have any suggestions for interactive debugging of Julia code in Emacs? +01:15.200 Q: Can you call out something that Julia has that Emacs does not, and which could benefit Emacs? +02:38.160 Q: Is there a way to use lisp syntax with Julia, like hy for python or lisp flavoured erlang? +03:51.240 Q: Have you tried the Julia Snail package for Emacs? It tries to be like SLY/SLIME for Common Lisp. +04:26.080 Q: Is there a data inspector for a Julia REPL available that you can use in Emacs? +05:24.360 Q: Have you tried literate programming Julia (using Org babel or some other means) in Emacs? + +"""]]
Listen to just the audio:
# Description \ No newline at end of file diff --git a/2024/info/learning-before.md b/2024/info/learning-before.md index 09dcd728..432d6c2d 100644 --- a/2024/info/learning-before.md +++ b/2024/info/learning-before.md @@ -28,13 +28,13 @@ Status: TO_CAPTION_QA 18:36.957 Summary 19:03.210 References -"""]]
Duration: 19:39 minutes
+"""]]
Duration: 19:39 minutes
# Q&A
[[!template id="chapters" vidid="qanda-learning" data=""" 00:00.000 -"""]]
Listen to just the audio:
Duration: 24:41 minutes
+"""]]
Listen to just the audio:
Duration: 24:41 minutes
# Description \ No newline at end of file diff --git a/2024/info/links-before.md b/2024/info/links-before.md index 29d08889..fadd060a 100644 --- a/2024/info/links-before.md +++ b/2024/info/links-before.md @@ -15,6 +15,6 @@ Status: TO_FOLLOW_UP 08:26.000 Exposing notes outside Emacs 10:38.000 Future Directions and Potential Improvements -"""]]
Duration: 11:21 minutes
+"""]]
Duration: 11:21 minutes
# Description \ No newline at end of file diff --git a/2024/info/literate-before.md b/2024/info/literate-before.md index 27e4caff..78a10476 100644 --- a/2024/info/literate-before.md +++ b/2024/info/literate-before.md @@ -26,7 +26,7 @@ Status: TO_CAPTION_QA 14:23.166 LP prose isn't comments 14:55.800 Summary -"""]]
Duration: 15:51 minutes
+"""]]
Duration: 15:51 minutes
# Q&A @@ -48,6 +48,6 @@ Status: TO_CAPTION_QA 18:38.936 Q: Have you used Cucumber/Gherkin/BDD and do you think it has a strong overlap to what you talked about here? 19:54.600 Q: What granularity are you looking for re your org files and contents, with respect to a codebase that it tangles to, or in non-coding contexts? -"""]]
Listen to just the audio:
Duration: 22:48 minutes
+"""]]
Listen to just the audio:
Duration: 22:48 minutes
# Description \ No newline at end of file diff --git a/2024/info/maxima-before.md b/2024/info/maxima-before.md index acbda4a4..84d8dad2 100644 --- a/2024/info/maxima-before.md +++ b/2024/info/maxima-before.md @@ -9,7 +9,7 @@ Status: TO_FOLLOW_UP # Talk -
Duration: 30:34 minutes
+
Duration: 30:34 minutes
# Q&A diff --git a/2024/info/mcclim-before.md b/2024/info/mcclim-before.md index 02efd13d..70b4798e 100644 --- a/2024/info/mcclim-before.md +++ b/2024/info/mcclim-before.md @@ -15,7 +15,7 @@ Status: TO_CAPTION_QA 19:12.802 Inferior Lisp and McCLIM 29:10.964 Putting things together -"""]]
Duration: 34:29 minutes
+"""]]
Duration: 34:29 minutes
# Q&A @@ -27,6 +27,6 @@ Status: TO_CAPTION_QA 10:43.600 IELM 12:32.880 Q: Are we going to get a McCLIM LambdaMOO client? -"""]]
Listen to just the audio:
+"""]]
Listen to just the audio:
# Description \ No newline at end of file diff --git a/2024/info/org-update-before.md b/2024/info/org-update-before.md index a5151606..dbd9884e 100644 --- a/2024/info/org-update-before.md +++ b/2024/info/org-update-before.md @@ -39,7 +39,7 @@ Status: TO_CAPTION_QA 38:30.440 Got no free time, but still want to help? 39:12.997 Thank you -"""]]
Duration: 39:35 minutes
+"""]]
Duration: 39:35 minutes
# Q&A @@ -54,6 +54,6 @@ Status: TO_CAPTION_QA 26:08.840 microemacs 29:31.920 Q: Is there/could there be a resource with which to recommend particularly well written codebases for review by others? -"""]]
Listen to just the audio:
Duration: 30:39 minutes
+"""]]
Listen to just the audio:
Duration: 30:39 minutes
# Description \ No newline at end of file diff --git a/2024/info/p-search-before.md b/2024/info/p-search-before.md index 50d1b382..fc7c8c39 100644 --- a/2024/info/p-search-before.md +++ b/2024/info/p-search-before.md @@ -23,7 +23,7 @@ Status: TO_CAPTION_QA 20:40.405 Importance 21:38.560 Complement or inverse -"""]]
Duration: 22:42 minutes
+"""]]
Duration: 22:42 minutes
# Q&A @@ -53,6 +53,6 @@ Status: TO_CAPTION_QA 40:04.120 Q: Do you think the Emacs being kinda slow will get in the way of being able to run a lot of scoring algorithms? 43:08.640 Boundary conditions -"""]]
Listen to just the audio:
+"""]]
Listen to just the audio:
# Description \ No newline at end of file diff --git a/2024/info/papers-before.md b/2024/info/papers-before.md index 7a55a409..46876d15 100644 --- a/2024/info/papers-before.md +++ b/2024/info/papers-before.md @@ -23,7 +23,7 @@ Status: TO_CAPTION_QA 07:09.720 Examples 07:41.240 Tags -"""]]
Duration: 10:07 minutes
+"""]]
Duration: 10:07 minutes
# Q&A @@ -37,6 +37,6 @@ Status: TO_CAPTION_QA 14:21.160 Q: Are you using zotra or org-ref? 14:45.120 Q: How much of this is tied to org-roam specifically? -"""]]
Listen to just the audio:
Duration: 19:01 minutes
+"""]]
Listen to just the audio:
Duration: 19:01 minutes
# Description \ No newline at end of file diff --git a/2024/info/pgmacs-before.md b/2024/info/pgmacs-before.md index b08174a2..1770f8ee 100644 --- a/2024/info/pgmacs-before.md +++ b/2024/info/pgmacs-before.md @@ -22,7 +22,7 @@ Status: TO_CAPTION_QA 09:36.250 Extending pgmacs 11:49.400 Conclusion -"""]]
Duration: 13:17 minutes
+"""]]
Duration: 13:17 minutes
# Q&A @@ -35,6 +35,6 @@ Status: TO_CAPTION_QA 16:53.850 Q: What do you use for the in-buffer tables? Vtable? 18:16.640 Integrating with Emacs 30? -"""]]
Listen to just the audio:
Duration: 20:02 minutes
+"""]]
Listen to just the audio:
Duration: 20:02 minutes
# Description \ No newline at end of file diff --git a/2024/info/project-before.md b/2024/info/project-before.md index 10db6b6a..dd34cb38 100644 --- a/2024/info/project-before.md +++ b/2024/info/project-before.md @@ -30,7 +30,7 @@ Status: TO_CAPTION_QA 19:49.640 Conclusions 20:34.520 Acknowledgements -"""]]
Duration: 21:38 minutes
+"""]]
Duration: 21:38 minutes
# Q&A @@ -47,6 +47,6 @@ Status: TO_CAPTION_QA 52:48.680 Org Mode versus Markdown 56:28.560 Raku -"""]]
Listen to just the audio:
Duration: 1:02:41 minutes
+"""]]
Listen to just the audio:
Duration: 1:02:41 minutes
# Description \ No newline at end of file diff --git a/2024/info/regex-before.md b/2024/info/regex-before.md index 83e05a1e..b8bf89db 100644 --- a/2024/info/regex-before.md +++ b/2024/info/regex-before.md @@ -7,6 +7,6 @@ Status: TO_FOLLOW_UP -
Duration: 24:56 minutes
+
Duration: 24:56 minutes
# Description \ No newline at end of file diff --git a/2024/info/rust-before.md b/2024/info/rust-before.md index 303796ae..fcd31ab7 100644 --- a/2024/info/rust-before.md +++ b/2024/info/rust-before.md @@ -41,7 +41,7 @@ Status: TO_CAPTION_QA 19:07.247 Next directions 19:22.739 How to get involved -"""]]
Duration: 20:06 minutes
+"""]]
Duration: 20:06 minutes
# Q&A @@ -61,6 +61,6 @@ Status: TO_CAPTION_QA 14:20.100 Q: Is it possible to bootstrap with just the bytecode interpreter? 17:03.960 What would it take to bootstrap Guile in Rune? -"""]]
Listen to just the audio:
Duration: 19:15 minutes
+"""]]
Listen to just the audio:
Duration: 19:15 minutes
# Description \ No newline at end of file diff --git a/2024/info/sat-open-before.md b/2024/info/sat-open-before.md index b6bd7c01..e0edf012 100644 --- a/2024/info/sat-open-before.md +++ b/2024/info/sat-open-before.md @@ -20,6 +20,6 @@ Status: TO_FOLLOW_UP 04:37.333 emacsconf-discuss updates 04:42.249 Let's go! -"""]]
Duration: 04:50 minutes
+"""]]
Duration: 04:50 minutes
# Description \ No newline at end of file diff --git a/2024/info/sharing-before.md b/2024/info/sharing-before.md index ab783b78..e3154751 100644 --- a/2024/info/sharing-before.md +++ b/2024/info/sharing-before.md @@ -28,6 +28,6 @@ Status: TO_FOLLOW_UP 18:06.166 Your secret sauce 19:04.933 Cons of YouTube -"""]]
Duration: 21:40 minutes
+"""]]
Duration: 21:40 minutes
# Description \ No newline at end of file diff --git a/2024/info/shell-before.md b/2024/info/shell-before.md index 18b88f61..6003d0e5 100644 --- a/2024/info/shell-before.md +++ b/2024/info/shell-before.md @@ -23,6 +23,6 @@ Status: TO_FOLLOW_UP 34:21.128 Login shell 36:36.980 Resources -"""]]
Duration: 37:13 minutes
+"""]]
Duration: 37:13 minutes
# Description \ No newline at end of file diff --git a/2024/info/students-before.md b/2024/info/students-before.md index 3fb83974..9358f56c 100644 --- a/2024/info/students-before.md +++ b/2024/info/students-before.md @@ -9,7 +9,7 @@ Status: TO_CAPTION_QA # Talk -
Duration: 08:27 minutes
+
Duration: 08:27 minutes
# Q&A @@ -25,6 +25,6 @@ Status: TO_CAPTION_QA 15:21.920 Q: Has using emacs led to expanded interest in programming/computer science? 16:40.672 Q: How does interaction with others work in technical terms? -"""]]
Listen to just the audio:
+"""]]
Listen to just the audio:
# Description \ No newline at end of file diff --git a/2024/info/sun-open-before.md b/2024/info/sun-open-before.md index e5461c70..ed155b5e 100644 --- a/2024/info/sun-open-before.md +++ b/2024/info/sun-open-before.md @@ -7,6 +7,6 @@ Status: All done -
Duration: 04:37 minutes
+
Duration: 04:37 minutes
# Description \ No newline at end of file diff --git a/2024/info/theme-before.md b/2024/info/theme-before.md index 7d8e7874..8a945375 100644 --- a/2024/info/theme-before.md +++ b/2024/info/theme-before.md @@ -20,7 +20,7 @@ Status: TO_CAPTION_QA 07:19.780 How to pick a random color palette 08:12.070 XYZ -"""]]
Duration: 11:28 minutes
+"""]]
Duration: 11:28 minutes
# Q&A @@ -30,6 +30,6 @@ Status: TO_CAPTION_QA 02:43.720 Q: One area I see emacs able to do themes that is "underused?" is changing the font 08:53.461 Q: Have you ever kept any of the random themes that were thrown up? -"""]]
Listen to just the audio:
Duration: 09:51 minutes
+"""]]
Listen to just the audio:
Duration: 09:51 minutes
# Description \ No newline at end of file diff --git a/2024/info/transducers-after.md b/2024/info/transducers-after.md index 8dbe9101..3995e5c1 100644 --- a/2024/info/transducers-after.md +++ b/2024/info/transducers-after.md @@ -397,7 +397,7 @@ Captioner: sachac [[!template text="""Hopefully the internet goes well. It's a nice Monday""" start="00:00:00.000" video="qanda-transducers" id="subtitle"]] [[!template text="""morning here in Tokyo.""" start="00:00:07.560" video="qanda-transducers" id="subtitle"]] [[!template text="""Are we connected all right?""" start="00:00:32.000" video="qanda-transducers" id="subtitle"]] -[[!template text="""Okay, I seem to be struggling still with my audio. 1 2nd""" start="00:00:37.880" video="qanda-transducers" id="subtitle"]] +[[!template text="""Okay, I seem to be struggling still with my audio. One second...""" start="00:00:37.880" video="qanda-transducers" id="subtitle"]] [[!template text="""calling. Yeah, you were muted for a moment there. Okay,""" start="00:00:40.880" video="qanda-transducers" id="subtitle"]] [[!template text="""there we are. Okay. All right. Sorry about that. I got a mute""" start="00:00:44.520" video="qanda-transducers" id="subtitle"]] [[!template text="""out my, my back office chatter. That's kind of distracting""" start="00:00:49.960" video="qanda-transducers" id="subtitle"]] diff --git a/2024/info/transducers-before.md b/2024/info/transducers-before.md index 01347152..bd531257 100644 --- a/2024/info/transducers-before.md +++ b/2024/info/transducers-before.md @@ -23,7 +23,7 @@ Status: TO_CAPTION_QA 20:00.520 Transducers in the wild - CSV 26:03.240 Issues and next steps -"""]]
Duration: 26:51 minutes
+"""]]
Duration: 26:51 minutes
# Q&A @@ -31,7 +31,7 @@ Status: TO_CAPTION_QA 01:09.920 Q: When I tried comparing transducers.el to cl-lib and dash (benchmark-compiled), I got the following results 05:40.840 Q: Do you know of any theoretical texts on transducers? 07:04.720 Q: Did you think about [compiler features, macros] viz your cl, fennel, elisp, porting of your transducers? -08:16.579 Q: Does t-buffer-read provide a lazy stream that\'s linewise, or charwise, or do something else entirely? +08:16.579 Q: Does t-buffer-read provide a lazy stream that's linewise, or charwise, or do something else entirely? 09:09.424 Q: Can the Elisp library be combined with the stream.el API or seq in general? 11:47.543 Q: How does one debug a t-comp expression? Can you single step and see intermediate results of the different statements you declare? 14:42.495 Q: Is there a path for transducers to enable elisp processing of otherwise overly large datasets as if just normal Emacs \"buffers\" (i.e. just pulling one thing at a time so essentially stream-like under the hood but buffer-like in interface), with none of the usual perf issues with a traditional buffer structure? @@ -39,7 +39,9 @@ Status: TO_CAPTION_QA 17:50.520 Q: Is the common lisp version ready for 'production' use? Is it complete enough and the API stable enough? 18:17.477 Q: Do we need a pre-written \"t-\" version for every already existing reducing function like + or is there a function to construct them from already defined reducer 2-arg functions? 20:26.320 Q: Is the compelling argument for transducers is that it's a better abstraction? +22:31.960 Q: Question about how the transducers video was made? Did you use Reveal.js? Do you have a pointer to the html hosted presentation? How did you generate the content for Reveal? +24:20.160 Q: From your investigations and tests so far, do you think there would be the necessity of transducers to eventually go down into the C level code for things like using them to solve "infinitely-big" buffer-like interfaces and such? -"""]]
Listen to just the audio:
Duration: 25:24 minutes
+"""]]
Listen to just the audio:
Duration: 25:24 minutes
# Description \ No newline at end of file diff --git a/2024/info/water-before.md b/2024/info/water-before.md index 8a53bd65..cf11c56d 100644 --- a/2024/info/water-before.md +++ b/2024/info/water-before.md @@ -17,6 +17,6 @@ Status: TO_FOLLOW_UP 09:05.724 Managing the plant 13:09.560 Conclusion -"""]]
Duration: 13:50 minutes
+"""]]
Duration: 13:50 minutes
# Description \ No newline at end of file diff --git a/2024/info/writing-before.md b/2024/info/writing-before.md index c9ac9ad6..62663ff7 100644 --- a/2024/info/writing-before.md +++ b/2024/info/writing-before.md @@ -20,6 +20,6 @@ Status: TO_FOLLOW_UP 10:05.920 The project file 12:18.720 Conclusions -"""]]
Duration: 13:31 minutes
+"""]]
Duration: 13:31 minutes
# Description \ No newline at end of file diff --git a/2024/schedule-details.md b/2024/schedule-details.md index 34db3ccc..a769e01b 100644 --- a/2024/schedule-details.md +++ b/2024/schedule-details.md @@ -15,7 +15,7 @@ Jump to: Development [[!template id=sched resources="""
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (21MB)
    • """ title="""Unlocking linked data: replacing specialized apps with an Org-based semantic wiki""" url="""/2024/talks/links""" speakers="""Abhinav Tushar""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""links""" note="""captioned, video posted, video: 11:21"""]] [[!template id=sched resources="""
  • Download --intro.webm
  • Download --main.vtt
  • Download --main.webm (199MB)
  • Download --slides.pdf
    • """ title="""Emacs regex compilation and future directions for expressive pattern matching""" url="""/2024/talks/regex""" speakers="""Danny McClanahan""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""regex""" note="""captioned, video posted, video: 24:56"""]] [[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers--edited.opus (20MB)
  • Download --answers.opus (11MB)
  • Download --answers.vtt (unedited)
  • Download --answers.webm (57MB)
  • Download --edited.webm (57MB)
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (137MB)
  • Download --slides.pdf (9.5MB)
    • """ title="""Survival of the skillest: Thriving in the learning jungle""" url="""/2024/talks/learning""" speakers="""Bala Ramadurai""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""learning""" note="""captioned, video posted, Q&A posted, video: 19:39, answers: 24:41"""]] -[[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers.opus (8.9MB)
  • Download --answers.vtt (unedited)
  • Download --answers.webm (41MB)
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (110MB)
    • """ title="""About Blee: enveloping our own autonomy directed digital ecosystem with Emacs""" url="""/2024/talks/blee""" speakers="""Mohsen BANAN""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""blee""" note="""captioned, video posted, Q&A posted, video: 45:30, answers: 18:11"""]] +[[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers.opus (8.9MB)
  • Download --answers.vtt
  • Download --answers.webm (41MB)
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (110MB)
    • """ title="""About Blee: enveloping our own autonomy directed digital ecosystem with Emacs""" url="""/2024/talks/blee""" speakers="""Mohsen BANAN""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""blee""" note="""captioned, video posted, Q&A posted, video: 45:30, answers: 18:11"""]] [[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers.opus (8.1MB)
  • Download --answers.vtt (unedited)
  • Download --answers.webm (30MB)
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (47MB)
    • """ title="""Fun things with GNU Hyperbole""" url="""/2024/talks/hyperbole""" speakers="""Mats Lidell""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""hyperbole""" note="""captioned, video posted, Q&A posted, video: 14:10, answers: 21:56"""]] [[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers.opus (12MB)
  • Download --answers.vtt (unedited)
  • Download --answers.webm (38MB)
  • Download --intro.vtt
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (43MB)
    • """ title="""PGmacs: browsing and editing PostgreSQL databases from Emacs""" url="""/2024/talks/pgmacs""" speakers="""Eric Marsden""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""pgmacs""" note="""captioned, video posted, Q&A posted, video: 13:17, answers: 20:02"""]] [[!template id=sched resources="""
  • Download --answers--chapters.vtt
  • Download --answers.opus (12MB)
  • Download --answers.vtt (unedited)
  • Download --answers.webm (56MB)
  • Download --intro.webm
  • Download --main--chapters.vtt
  • Download --main.vtt
  • Download --main.webm (42MB)
    • """ title="""Literate programming for the 21st Century""" url="""/2024/talks/literate""" speakers="""Howard Abrams""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""literate""" note="""captioned, video posted, Q&A posted, video: 15:51, answers: 22:48"""]] -- cgit v1.2.3