diff options
Diffstat (limited to '2022/captions/emacsconf-2022-rde--rde-emacs-introduction--andrew-tropin--answers.vtt')
| -rw-r--r-- | 2022/captions/emacsconf-2022-rde--rde-emacs-introduction--andrew-tropin--answers.vtt | 1133 |
1 files changed, 1133 insertions, 0 deletions
diff --git a/2022/captions/emacsconf-2022-rde--rde-emacs-introduction--andrew-tropin--answers.vtt b/2022/captions/emacsconf-2022-rde--rde-emacs-introduction--andrew-tropin--answers.vtt new file mode 100644 index 00000000..7365f8e9 --- /dev/null +++ b/2022/captions/emacsconf-2022-rde--rde-emacs-introduction--andrew-tropin--answers.vtt @@ -0,0 +1,1133 @@ +WEBVTT + +00:00:00.000 --> 00:00:02.160 + We'll hit start recording. + +00:00:02.160 --> 00:00:03.400 + All right, everyone. + +00:00:03.400 --> 00:00:05.840 + Thanks, Andrew, for the great talk. + +00:00:05.840 --> 00:00:06.840 + Super cool. + +00:00:06.840 --> 00:00:09.240 + So now we have the live Q&A with Andrew. + +00:00:09.240 --> 00:00:12.440 + Folks, you can start by asking your questions on the pad. + +00:00:12.440 --> 00:00:14.680 + And we will also open up this big blue button + +00:00:14.680 --> 00:00:17.160 + room in a few minutes for folks who + +00:00:17.160 --> 00:00:19.920 + want to join here and ask questions here directly + +00:00:19.920 --> 00:00:21.320 + to Andrew. + +00:00:21.320 --> 00:00:24.080 + Thanks again, and take it away, Andrew. + +00:00:24.080 --> 00:00:26.400 + OK, thank you. + +00:00:26.400 --> 00:00:29.720 + Let's start from pod questions. + +00:00:29.720 --> 00:00:35.560 + The first one, do I use this to have multiple configs + +00:00:35.560 --> 00:00:35.880 + running + +00:00:35.880 --> 00:00:39.560 + side by side for deep comparison? + +00:00:39.560 --> 00:00:43.920 + Actually, I have two configurations primary here. + +00:00:43.920 --> 00:00:46.640 + The first one is my main configuration + +00:00:46.640 --> 00:00:51.600 + for the whole environment, which manages all the dot files. + +00:00:51.600 --> 00:00:55.080 + And the second one is virtualenv-like. + +00:00:55.080 --> 00:00:59.600 + It creates a new shell with some environment variables. + +00:00:59.600 --> 00:01:01.000 + It's set inside it. + +00:01:01.000 --> 00:01:05.920 + And it includes Emacs load path and other things + +00:01:05.920 --> 00:01:10.240 + to make Emacs able to explore packages + +00:01:10.240 --> 00:01:13.040 + inside this small environment. + +00:01:13.040 --> 00:01:18.120 + And it removes all unnecessary environment variables, + +00:01:18.120 --> 00:01:20.160 + which pollutes the environment. + +00:01:20.160 --> 00:01:25.800 + So we have quite a small scope on which only Emacs + +00:01:25.800 --> 00:01:28.480 + and a few other packages are available. + +00:01:28.480 --> 00:01:31.280 + And as you saw at the end of the talk, + +00:01:31.280 --> 00:01:33.880 + it was the example of such small environment + +00:01:33.880 --> 00:01:38.500 + where I set up Emacs and all the dependencies from ground + +00:01:38.500 --> 00:01:38.920 + up. + +00:01:38.920 --> 00:01:40.760 + And actually, the similar thing I + +00:01:40.760 --> 00:01:43.760 + use for development of my projects, + +00:01:43.760 --> 00:01:45.440 + I have their project environments + +00:01:45.440 --> 00:01:47.640 + made in the same way. + +00:01:47.640 --> 00:01:52.400 + But usually, I use my primary Emacs instance. + +00:01:52.400 --> 00:01:55.880 + But sometimes, it can be kind of mixed. + +00:01:55.880 --> 00:01:59.080 + I have a few talks on my YouTube channel. + +00:01:59.080 --> 00:02:03.630 + And you can check them out to get more information about it + +00:02:03.630 --> 00:02:04.000 +. + +00:02:04.000 --> 00:02:04.560 + The second-- + +00:02:04.560 --> 00:02:05.060 + Sorry. + +00:02:05.060 --> 00:02:06.320 + One quick request, Andrew. + +00:02:06.320 --> 00:02:08.780 + People are saying if you could maybe speak up a little bit + +00:02:08.780 --> 00:02:11.170 + more so that they could hear you better, that would be + +00:02:11.170 --> 00:02:11.760 + great. + +00:02:11.760 --> 00:02:12.840 + OK, sure. + +00:02:12.840 --> 00:02:14.560 + Thank you. + +00:02:14.560 --> 00:02:16.760 + The second question. + +00:02:16.760 --> 00:02:20.080 + Are you using Gix system or Gix on top of another distro? + +00:02:20.080 --> 00:02:22.480 + If system, any tips? + +00:02:22.480 --> 00:02:24.920 + I tried Gix system, but found getting started + +00:02:24.920 --> 00:02:27.760 + was very difficult due to lack of Wi-Fi firmware + +00:02:27.760 --> 00:02:31.640 + and incomplete documentation. + +00:02:31.640 --> 00:02:35.280 + Personally, I use Gix system, Gix home, + +00:02:35.280 --> 00:02:38.200 + Gix as a package manager, and also as a deployment tool + +00:02:38.200 --> 00:02:40.880 + for a few services. + +00:02:40.880 --> 00:02:44.700 + I started from very basic setup where I didn't have + +00:02:44.700 --> 00:02:45.360 + anything + +00:02:45.360 --> 00:02:49.080 + and build it piece by piece, including + +00:02:49.080 --> 00:02:52.400 + building Gix home project. + +00:02:52.400 --> 00:02:56.680 + So yeah, I use Gix system and all the things. + +00:02:56.680 --> 00:03:02.040 + And talking about Wi-Fi, first option + +00:03:02.040 --> 00:03:04.680 + is to buy a Wi-Fi adapter, which doesn't + +00:03:04.680 --> 00:03:07.080 + require proprietary firmware. + +00:03:07.080 --> 00:03:11.040 + And another option is finding the firmware and installing + +00:03:11.040 --> 00:03:12.000 + it. + +00:03:12.000 --> 00:03:13.760 + So it's up to you. + +00:03:13.760 --> 00:03:17.840 + Everything actually is relatively easy, + +00:03:17.840 --> 00:03:23.600 + and you can relatively easy find the way to do it. + +00:03:23.600 --> 00:03:25.560 + The third question. + +00:03:25.560 --> 00:03:29.360 + One of the issues I have had managing Emacs packages + +00:03:29.360 --> 00:03:32.360 + with Gix is a conflict between Gix package + +00:03:32.360 --> 00:03:35.160 + attest read-only and the Emacs package + +00:03:35.160 --> 00:03:37.840 + attest hackable in real time. + +00:03:37.840 --> 00:03:40.680 + Any suggestions to resolve this? + +00:03:40.680 --> 00:03:45.600 + Yes, I have suggestions to resolve this. + +00:03:45.600 --> 00:03:46.600 + Actually, it's true. + +00:03:46.600 --> 00:03:50.560 + Everything which is in GNU store is read-only. + +00:03:50.560 --> 00:03:55.680 + Everything which is built with Gix is almost set in stone, + +00:03:55.680 --> 00:04:00.720 + and you can't edit it in real time. + +00:04:00.720 --> 00:04:02.720 + But what I do-- + +00:04:02.720 --> 00:04:03.760 + can I share my screen? + +00:04:03.760 --> 00:04:09.160 + One second. + +00:04:09.160 --> 00:04:14.140 + I will press a few buttons, and I hope you will see it soon + +00:04:14.140 --> 00:04:14.360 +. + +00:04:16.360 --> 00:04:16.360 + + +00:04:16.360 --> 00:04:18.080 + Or maybe not so soon. + +00:04:18.080 --> 00:04:26.600 + What I basically do, I take parts of the ELISP, + +00:04:26.600 --> 00:04:30.240 + and I have them inside my scheme file + +00:04:30.240 --> 00:04:36.640 + that I use to define my home environment and other things. + +00:04:36.640 --> 00:04:38.560 + I don't know-- oh, OK. + +00:04:38.560 --> 00:04:39.640 + That's it. + +00:04:39.640 --> 00:04:43.560 + For example, here, this part is a scheme code. + +00:04:43.560 --> 00:04:46.640 + But this part is pure ELISP code. + +00:04:46.640 --> 00:04:56.400 + And I can use a direct region and use Emacs ELISP mode here + +00:04:56.400 --> 00:04:56.440 +. + +00:04:56.440 --> 00:05:01.160 + I will need parts, edit those parts, and select. + +00:05:01.160 --> 00:05:05.520 + And when I'm fine with all the edits I did here-- + +00:05:05.520 --> 00:05:08.400 + for example, I can evaluate this form using + +00:05:08.400 --> 00:05:10.760 + Control-X, Control-E, and so on. + +00:05:10.760 --> 00:05:13.300 + And when I'm good with the results, + +00:05:13.300 --> 00:05:16.920 + I can just save it and rebuild my whole home environment + +00:05:16.920 --> 00:05:21.360 + and see it on a fresh Emacs instance load + +00:05:21.360 --> 00:05:26.760 + from the new configuration and see if everything + +00:05:26.760 --> 00:05:28.880 + works here as well. + +00:05:28.880 --> 00:05:32.760 + So it's a little less interactive + +00:05:32.760 --> 00:05:35.000 + than the usual Emacs configuration, + +00:05:35.000 --> 00:05:36.480 + but still works quite well. + +00:05:40.800 --> 00:05:43.540 + A question-- what is next for RD? + +00:05:43.540 --> 00:05:48.420 + Actually, I have short-term plans and a little more + +00:05:48.420 --> 00:05:49.660 + long-term plans. + +00:05:49.660 --> 00:05:52.580 + Short-term plan is to make a first release + +00:05:52.580 --> 00:05:54.740 + by the end of this year. + +00:05:54.740 --> 00:05:58.860 + And this release-- actually, RD is quite usable currently, + +00:05:58.860 --> 00:06:02.220 + but there is not much documentation and not + +00:06:02.220 --> 00:06:04.620 + so many examples. + +00:06:04.620 --> 00:06:09.060 + So I would like to prepare a documentation + +00:06:09.060 --> 00:06:15.500 + getting started guide, live CD that you can use + +00:06:15.500 --> 00:06:23.020 + for exploration purpose and for installation. + +00:06:23.020 --> 00:06:31.380 + And also, I would like to find one or two maintainers which + +00:06:31.380 --> 00:06:37.260 + will help with upcoming patches, because it's already + +00:06:37.260 --> 00:06:40.300 + at least a few people who use it on a daily basis, + +00:06:40.300 --> 00:06:42.860 + and they send a lot of patches. + +00:06:42.860 --> 00:06:46.860 + And sometimes I have a hard time keeping up + +00:06:46.860 --> 00:06:49.660 + with the speed of creating patches. + +00:06:49.660 --> 00:06:53.540 + So the short-term plans is to make a first release + +00:06:53.540 --> 00:06:54.860 + by the end of the year. + +00:06:54.860 --> 00:07:00.140 + The long-term plans we can discuss later, I think. + +00:07:00.140 --> 00:07:03.580 + And I will share them in RD announced mailing list. + +00:07:06.220 --> 00:07:12.980 + OK, I think that's it for patterns. + +00:07:12.980 --> 00:07:14.580 + Let me check RC. + +00:07:14.580 --> 00:07:30.060 + I have-- OK, it seems that I answered all questions + +00:07:30.060 --> 00:07:31.540 + that I found. + +00:07:31.540 --> 00:07:33.180 + Let me know if something appears. + +00:07:33.180 --> 00:07:39.580 + [AUDIO OUT] + +00:07:39.580 --> 00:07:40.580 + Cool, thanks, Andrew. + +00:07:40.580 --> 00:07:44.820 + And yeah, I think we still have over 10 minutes, maybe + +00:07:44.820 --> 00:07:49.460 + 12 minutes or so of live Q&A time on the stream. + +00:07:49.460 --> 00:07:51.180 + So if people still have more questions, + +00:07:51.180 --> 00:07:53.180 + please feel free to either add them on the pad, + +00:07:53.180 --> 00:07:54.540 + or I think you should now also be + +00:07:54.540 --> 00:08:00.020 + able to join this big blue button room to ask directly. + +00:08:00.020 --> 00:08:04.100 + OK, I see one more question. + +00:08:04.100 --> 00:08:08.100 + But I'm not sure what does it mean. + +00:08:08.100 --> 00:08:10.380 + Do you use Emacs without this? + +00:08:10.380 --> 00:08:13.940 + If so, for what purpose? + +00:08:13.940 --> 00:08:17.780 + And how does it feel compared to RD? + +00:08:17.780 --> 00:08:20.980 + OK, it's a question in general. + +00:08:20.980 --> 00:08:24.020 + No, I don't use Emacs without RD. + +00:08:24.020 --> 00:08:28.700 + Actually, all the Emacs configurations I use + +00:08:28.700 --> 00:08:33.340 + is based on RD and built from that. + +00:08:33.340 --> 00:08:43.580 + There is a way to add almost everything + +00:08:43.580 --> 00:08:45.940 + you have in your basic Emacs configuration + +00:08:45.940 --> 00:08:52.540 + to your RD Emacs configuration by creating a file + +00:08:52.540 --> 00:08:56.780 + in your usual .config/emacsd directory + +00:08:56.780 --> 00:09:01.740 + and loading it from your .init/el directory. + +00:09:01.740 --> 00:09:07.940 + So you actually can have a very usual Emacs configuration + +00:09:07.940 --> 00:09:12.420 + workflow in addition to RD. + +00:09:12.420 --> 00:09:16.500 + But I don't use it because it's not a reproducible way + +00:09:16.500 --> 00:09:20.940 + to do things because such workflow means + +00:09:20.940 --> 00:09:25.220 + that I need to install packages separately somehow, + +00:09:25.220 --> 00:09:31.740 + either with gix install or maybe some other package manager + +00:09:31.740 --> 00:09:31.740 +, + +00:09:31.740 --> 00:09:37.610 + or maybe this package manager, like package.al or straight. + +00:09:37.610 --> 00:09:37.860 +al. + +00:09:37.860 --> 00:09:44.060 + And it doesn't work well in the long term + +00:09:44.060 --> 00:09:46.620 + because if I move such configuration, which + +00:09:46.620 --> 00:09:52.700 + partially RD and partially usual Emacs configuration, + +00:09:52.700 --> 00:09:58.980 + it will break on the new machine or maybe somewhere else + +00:09:58.980 --> 00:10:03.700 + where I would like to move this configuration later. + +00:10:03.700 --> 00:10:23.700 + OK. + +00:10:23.700 --> 00:10:27.700 + We have a last slot for Q and A in the pad. + +00:10:27.700 --> 00:10:39.380 + [LAUGHS] + +00:10:39.380 --> 00:10:43.940 + Thank you, everyone, for joining this talk. + +00:10:43.940 --> 00:10:46.820 + It was a pleasure to interview you. + +00:10:46.820 --> 00:10:52.780 + I will be here for at least an hour or so + +00:10:52.780 --> 00:10:56.340 + before I will go preparing to sleep. + +00:10:56.340 --> 00:11:02.740 + So you can reach me by email, RC, here in big blue button + +00:11:02.740 --> 00:11:07.220 + or some other way, probably. + +00:11:07.220 --> 00:11:09.660 + Are there any plans to push things + +00:11:09.660 --> 00:11:12.660 + from RD to gix main channel? + +00:11:12.660 --> 00:11:16.420 + Actually, I have a commit access to gix, + +00:11:16.420 --> 00:11:20.300 + and I try to upstream everything that + +00:11:20.300 --> 00:11:25.060 + can be beneficial for both RD and gix to gix + +00:11:25.060 --> 00:11:30.740 + and use it from the upstream. + +00:11:30.740 --> 00:11:35.320 + But sometimes on some question, we didn't reach an + +00:11:35.320 --> 00:11:35.900 + agreement, + +00:11:35.900 --> 00:11:40.660 + or sometimes it's much easier to implement it + +00:11:40.660 --> 00:11:46.500 + in a more rapid way, which probably I + +00:11:46.500 --> 00:11:52.380 + wouldn't like to add to gix because it will require + +00:11:52.380 --> 00:11:56.340 + too much time trying to fit to some gix. + +00:11:56.340 --> 00:11:59.140 + So I keep it only in RD. + +00:11:59.140 --> 00:12:04.020 + But the things that I see beneficial for both projects, + +00:12:04.020 --> 00:12:07.460 + I try to share and to move them to gix. + +00:12:21.500 --> 00:12:22.220 + Sounds great. + +00:12:22.220 --> 00:12:23.780 + And another reminder for the folks + +00:12:23.780 --> 00:12:26.460 + that you can join big blue button also directly. + +00:12:26.460 --> 00:12:29.340 + If you want to type your questions into chat here + +00:12:29.340 --> 00:12:32.580 + or just ask them over mic or with a microphone, + +00:12:32.580 --> 00:12:33.540 + you can do that as well. + +00:12:33.540 --> 00:12:46.260 + I think we still have about actually 10 or 12 more minutes. + +00:12:46.260 --> 00:12:48.100 + I think I underestimated what we had. + +00:12:48.100 --> 00:12:50.100 + So we still have plenty of time for questions. + +00:12:50.100 --> 00:12:56.500 + [AUDIO OUT] + +00:12:56.500 --> 00:13:01.540 + Added one more slot for Gondi in case someone + +00:13:01.540 --> 00:13:05.180 + would like to fill it. + +00:13:05.180 --> 00:13:06.740 + Thanks. + +00:13:06.740 --> 00:13:34.220 + [AUDIO OUT] + +00:13:34.220 --> 00:13:39.260 + How difficult is to add support for new packages to gix? + +00:13:39.260 --> 00:13:44.020 + Have you found that's burdensome versus package L + +00:13:44.020 --> 00:13:48.540 + or other in Emacs package management approach? + +00:13:48.540 --> 00:13:53.940 + Actually, I find it quite easy to create packages for gix. + +00:13:53.940 --> 00:13:59.460 + Maybe because I'm quite familiar with gix source code. + +00:13:59.460 --> 00:14:03.580 + But maybe because it's not that difficult, + +00:14:03.580 --> 00:14:11.660 + you just open a respective model like rd packages or gnu + +00:14:11.660 --> 00:14:13.540 + packages in gix repository. + +00:14:13.540 --> 00:14:15.660 + And you define the package you want. + +00:14:15.660 --> 00:14:19.100 + And you define the dependencies you want. + +00:14:19.100 --> 00:14:25.540 + Actually, a lot of packages already here in gix. + +00:14:25.540 --> 00:14:29.580 + And some of the packages I package in rd + +00:14:29.580 --> 00:14:31.660 + and later move to the gix. + +00:14:31.660 --> 00:14:37.300 + So it's not hard to reference the dependencies + +00:14:37.300 --> 00:14:40.780 + and find the dependencies already declared for you. + +00:14:40.780 --> 00:14:46.420 + But what's more important, you can use dependencies not + +00:14:46.420 --> 00:14:46.780 + only + +00:14:46.780 --> 00:14:49.660 + on Emacs packages, but also on system packages. + +00:14:49.660 --> 00:14:53.300 + For example, in my git package, you + +00:14:53.300 --> 00:14:55.700 + can use a reference to git binary + +00:14:55.700 --> 00:14:58.820 + and predefine the path to the git binary + +00:14:58.820 --> 00:15:03.540 + inside a package configuration by fetching the source code + +00:15:03.540 --> 00:15:04.860 + or something like that. + +00:15:04.860 --> 00:15:11.220 + So any package that requires some system package to work + +00:15:11.220 --> 00:15:14.180 + can use the system package as a dependency. + +00:15:14.180 --> 00:15:18.780 + And it is a big benefit comparing + +00:15:18.780 --> 00:15:21.500 + to other packaging solutions, which + +00:15:21.500 --> 00:15:25.460 + can depend only on Elisp packages. + +00:15:25.460 --> 00:15:36.340 + [AUDIO OUT] + +00:15:36.340 --> 00:15:40.060 + Do you reckon rd is currently opinionated, + +00:15:40.060 --> 00:15:44.180 + or is it a one-size-fits-all framework? + +00:15:44.180 --> 00:15:49.020 + I would say it's quite opinionated. + +00:15:49.020 --> 00:15:52.620 + I started from really bare-bone Emacs. + +00:15:52.620 --> 00:15:55.100 + And I suffered for a while. + +00:15:55.100 --> 00:15:58.620 + And I did features one by one very carefully, + +00:15:58.620 --> 00:16:02.500 + crafting the current state of rd-emacs. + +00:16:02.500 --> 00:16:08.180 + And it's, as I already said, vanilla flavored. + +00:16:08.180 --> 00:16:12.180 + I try to stick with Emacs key bindings + +00:16:12.180 --> 00:16:15.700 + to use built-in packages over external packages, + +00:16:15.700 --> 00:16:21.460 + or use packages which are in the same way, + +00:16:21.460 --> 00:16:26.100 + work in a similar manner to built-in packages. + +00:16:26.100 --> 00:16:29.740 + So it's not usual. + +00:16:29.740 --> 00:16:37.060 + It's not that user-friendly as Doom Emacs or Space Emacs. + +00:16:37.060 --> 00:16:45.580 + It's more like a Prelude, or even more vanilla flavored + +00:16:45.580 --> 00:16:47.380 + than Prelude. + +00:16:47.380 --> 00:16:50.420 + But the good thing is that you can declare a feature + +00:16:50.420 --> 00:16:51.340 + yourself. + +00:16:51.340 --> 00:16:55.260 + And if you don't like something about rd-emacs provided + +00:16:55.260 --> 00:16:59.860 + by features created by me or other contributors, + +00:16:59.860 --> 00:17:03.500 + you can use the features declared by yourself + +00:17:03.500 --> 00:17:06.060 + or by other people. + +00:17:06.060 --> 00:17:11.140 + And one of the plans that I have according to rd, + +00:17:11.140 --> 00:17:13.940 + which we are discussing on mailing list right now, + +00:17:13.940 --> 00:17:20.140 + is contrib directory, which can include features provided + +00:17:20.140 --> 00:17:21.660 + by different people. + +00:17:21.660 --> 00:17:28.500 + For example, it's quite often asked to add evils support. + +00:17:28.500 --> 00:17:31.540 + But I don't use evils. + +00:17:31.540 --> 00:17:35.460 + And I don't want to maintain this package. + +00:17:35.460 --> 00:17:38.140 + But I understand that many people + +00:17:38.140 --> 00:17:43.140 + use such a way of interacting with text editor. + +00:17:43.140 --> 00:17:45.660 + So it would be cool if someone who actually + +00:17:45.660 --> 00:17:48.420 + using this feature will be maintaining it + +00:17:48.420 --> 00:17:51.020 + in contrib directory. + +00:17:51.020 --> 00:17:55.180 + And this feature will be sound with all other features + +00:17:55.180 --> 00:17:55.460 + which + +00:17:55.460 --> 00:17:58.340 + provided by rd itself. + +00:17:58.340 --> 00:18:05.100 + And I think this way, it can cover more people needs + +00:18:05.100 --> 00:18:07.940 + that it can cover right now. + +00:18:07.940 --> 00:18:11.260 + So it will fit more people. + +00:18:11.260 --> 00:18:17.820 + But the core rd won't be expanding its scope. + +00:18:17.820 --> 00:18:19.020 + It will be quite focused. + +00:18:19.020 --> 00:18:27.940 + How to get into rd is already documentation + +00:18:27.940 --> 00:18:31.060 + and getting started guide. + +00:18:31.060 --> 00:18:34.740 + There is a repository on source hut, + +00:18:34.740 --> 00:18:42.700 + github.com/github/sourcehut/abcdw/rd. + +00:18:42.700 --> 00:18:47.620 + And here you can see a very small readme, + +00:18:47.620 --> 00:18:52.540 + which probably doesn't give you too much understanding of + +00:18:52.540 --> 00:18:52.780 + what + +00:18:52.780 --> 00:18:53.580 + is going on. + +00:18:53.580 --> 00:18:56.860 + But it has all the necessary links. + +00:18:56.860 --> 00:18:58.740 + It has a link to manual. + +00:18:58.740 --> 00:19:02.860 + It has information of mailing lists, + +00:19:02.860 --> 00:19:05.940 + which you can use to get help. + +00:19:05.940 --> 00:19:14.620 + It has information about IRC channel in manual. + +00:19:14.620 --> 00:19:18.540 + And you can join this channel and ask questions here. + +00:19:18.540 --> 00:19:22.060 + And of course, you can take the source code + +00:19:22.060 --> 00:19:23.860 + and take a look at it. + +00:19:23.860 --> 00:19:29.500 + And currently, we have examples. + +00:19:29.500 --> 00:19:37.380 + And here in examples, my whole configuration of my team + +00:19:37.380 --> 00:19:38.340 + is present. + +00:19:38.340 --> 00:19:43.580 + It's a little bit drafty. + +00:19:43.580 --> 00:19:47.380 + I would like to reorganize this a little + +00:19:47.380 --> 00:19:50.340 + to make it easier to follow. + +00:19:50.340 --> 00:19:55.140 + And before first release, I hope I will do so. + +00:19:55.140 --> 00:20:04.140 + But you can use it as an example, build on [INAUDIBLE] + +00:20:04.140 --> 00:20:09.700 + Unfortunately, the documentation + +00:20:09.700 --> 00:20:12.180 + is not very extensive. + +00:20:12.180 --> 00:20:17.740 + So you can find it a little hard to follow. + +00:20:17.740 --> 00:20:24.140 + Or maybe you can find it missing some important things. + +00:20:24.140 --> 00:20:29.140 + But before first release, I hope the situation + +00:20:29.140 --> 00:20:30.900 + will become a little better. + +00:20:30.900 --> 00:20:33.860 + But anyway, you can always ask questions + +00:20:33.860 --> 00:20:35.420 + until the documentation is ready. + +00:20:35.420 --> 00:20:44.060 + Can you mix RD with custom Emacs init file? + +00:20:44.060 --> 00:20:45.220 + Yes, you can. + +00:20:45.220 --> 00:20:47.780 + I already mentioned it. + +00:20:47.780 --> 00:20:53.220 + You can just define in your init.el + +00:20:53.220 --> 00:20:57.100 + the statement that you load some other file + +00:20:57.100 --> 00:21:02.860 + and use this file as your usual init.el file. + +00:21:02.860 --> 00:21:06.460 + It will work completely OK. + +00:21:06.460 --> 00:21:13.780 + And you can partially migrate to RD by using such approach. + +00:21:13.780 --> 00:21:17.540 + But I don't recommend this approach in long term. + +00:21:17.540 --> 00:21:19.020 + I already mentioned it. + +00:21:19.020 --> 00:21:24.140 + But having usual init.el file and managing your + +00:21:24.140 --> 00:21:25.340 + dependencies + +00:21:25.340 --> 00:21:29.580 + using package.el or straight.el doesn't + +00:21:29.580 --> 00:21:33.140 + cover system dependencies and other stuff, which + +00:21:33.140 --> 00:21:38.900 + will lead to maybe irreproducible configurations. + +00:21:38.900 --> 00:21:49.780 + [AUDIO OUT] + +00:21:49.780 --> 00:21:51.700 + It's the heads up that we have about two more + +00:21:51.700 --> 00:21:53.180 + minutes of live Q&A time. + +00:21:53.180 --> 00:21:55.100 + And then after that, the stream will move on. + +00:21:55.100 --> 00:21:58.300 + But people are welcome to continue asking questions, + +00:21:58.300 --> 00:22:01.460 + either on the pad or IRC or by joining the Speakable button + +00:22:01.460 --> 00:22:02.380 + room directly. + +00:22:02.380 --> 00:22:04.380 + Thanks again, Andrew. + +00:22:04.380 --> 00:22:23.700 + [AUDIO OUT] + +00:22:23.700 --> 00:22:27.660 + Actually, I didn't expect so much questions. + +00:22:27.660 --> 00:22:33.340 + And when I first took a look at the pad + +00:22:33.340 --> 00:22:38.700 + and thought, OK, those six slots for Q&A will be enough. + +00:22:38.700 --> 00:22:45.100 + Yeah, it's always a nice surprise, I guess. + +00:22:45.100 --> 00:23:04.140 + [AUDIO OUT] + +00:23:04.140 --> 00:23:07.780 + I hope everyone will be OK with jumping windows around, + +00:23:07.780 --> 00:23:10.420 + because I switch between workspaces. + +00:23:10.420 --> 00:23:12.660 + And it may be a little too noisy. + +00:23:12.660 --> 00:23:16.780 + [AUDIO OUT] + +00:23:16.780 --> 00:23:18.660 + Yeah, I think it's fine for the most part. + +00:23:18.660 --> 00:23:20.380 + It was a bit of an interesting thing + +00:23:20.380 --> 00:23:23.500 + trying to keep up the stream with it, because by default, + +00:23:23.500 --> 00:23:26.020 + we maximize the speaker's webcam. + +00:23:26.020 --> 00:23:27.900 + But then you're also sharing your screen + +00:23:27.900 --> 00:23:29.180 + and sharing important details. + +00:23:29.180 --> 00:23:32.780 + So we were also trying to get that on the stream as well. + +00:23:32.780 --> 00:23:33.660 + But yeah, it was fine. + +00:23:33.660 --> 00:23:41.260 + [AUDIO OUT] + +00:23:41.260 --> 00:23:46.780 + OK, I think that there's no more questions. + +00:23:46.780 --> 00:23:53.980 + And we can finish in this section. + +00:23:53.980 --> 00:23:55.580 + All right, sounds good. + +00:23:55.580 --> 00:23:58.020 + Thanks again, Andrew, for the great talk. + +00:23:58.020 --> 00:24:02.780 + As a fellow Tiling Window Manager user and GNU gigs-- + +00:24:02.780 --> 00:24:06.180 + well, former committer, but still very much enthusiast, + +00:24:06.180 --> 00:24:07.540 + I'm very much interested in this. + +00:24:07.540 --> 00:24:09.820 + So I know I'll definitely be checking your work out. + +00:24:09.820 --> 00:24:11.660 + So thanks again. + +00:24:11.660 --> 00:24:13.860 + Thank you very much for organization + +00:24:13.860 --> 00:24:15.820 + and all your contributions. + +00:24:15.820 --> 00:24:17.540 + Very much appreciated. + +00:24:17.540 --> 00:24:18.100 + Thank you. + +00:24:18.100 --> 00:24:18.600 + Thank you. + +00:24:18.600 --> 00:24:19.340 + Appreciate it. + +00:24:19.340 --> 00:24:20.140 + All right, take care. + +00:24:20.140 --> 00:24:22.580 + And we'll see you around. + +00:24:22.580 --> 00:24:23.580 + Bye-bye. + +00:24:23.580 --> 00:24:25.140 + Bye. + +00:24:25.140 --> 00:24:28.500 + [AUDIO OUT] + +00:24:30.500 --> 00:24:30.500 + + |