WEBVTT 00:00.000 --> 00:07.200 Okay, so we are live now. So hi, everyone. Sorry, we were doing some last minute verification 00:07.200 --> 00:12.720 with Blaine. We wanted to share screens, but somehow the Firefox gods are not in our favor 00:12.720 --> 00:15.640 today. So hi, Blaine. How are you doing? 00:15.640 --> 00:21.480 I'm doing great, Will. This has been a great conference. I've seen some talks this morning 00:21.480 --> 00:27.100 that are going to change my life. I just can't wait to start applying some of the packages 00:27.100 --> 00:28.100 I've learned about. 00:28.100 --> 00:33.240 That's amazing. And it's only day one. We've got more of this coming today, too. 00:33.240 --> 00:34.240 Exactly. 00:34.240 --> 00:38.000 So, Blaine, we haven't had the chance to tell you, but do you have the pad open on 00:38.000 --> 00:39.000 your end? 00:39.000 --> 00:40.000 Let's see. 00:40.000 --> 00:45.040 Oh, yes, because I asked you to close Firefox, so you don't have it. Do you need the URL, 00:45.040 --> 00:46.040 maybe? 00:46.040 --> 00:48.080 Yeah, that would be great. 00:48.080 --> 00:52.280 I will put it into BBB, the chat right on your left. 00:52.280 --> 00:58.200 Okay. I see it. So if I click on this and open a new window? 00:58.200 --> 01:00.520 Yes, don't worry about it. 01:00.520 --> 01:05.600 Okay. So I have some questions. Oh, that's fantastic. This is kind of a silly question, 01:05.600 --> 01:10.560 but I'm curious. Do you have a favorite color theme? 01:10.560 --> 01:21.120 So I do. I've been using a color theme that is sort of light green. It's from a set of 01:21.120 --> 01:29.760 themes that Prot put together and made available this fall on Melpa, and in some of the slides 01:29.760 --> 01:36.880 you'll see that I have this, like, white background, but I'm currently using a sort of a mint green 01:36.880 --> 01:45.240 color, which I find actually has great contrast, and I had to install some fonts for the Mac 01:45.240 --> 01:52.360 to be able to use that theme, but Prot provides detailed instructions, and it was pretty easy 01:52.360 --> 01:54.360 to do. 01:54.360 --> 02:03.960 Okay. Let's see. To your knowledge, so the second question is, to your knowledge, are 02:03.960 --> 02:09.000 recent coming security changes in Chrome going to impact browser extension? 02:09.000 --> 02:16.560 Oh, that's a great question. I, to be honest, I don't know. I'm not aware of that issue 02:16.560 --> 02:23.400 because I ran and I installed some extension I probably shouldn't have installed in Chrome 02:23.400 --> 02:30.120 a couple weeks ago, and I've been getting pop-up ads, and so I switched to Firefox, 02:30.120 --> 02:39.960 but so far I have used GhostText in a number of browsers. I can vouch that it works in 02:39.960 --> 02:50.120 Safari, Chrome, obviously Firefox, Brave, and then amongst the Firefox family of browsers 02:50.120 --> 02:56.240 there's WaterFox and IceCat. It works in those two. 02:56.240 --> 03:02.400 So if Chrome's security issues become a problem, then there are other browsers for which maybe 03:02.400 --> 03:07.960 that problem won't be an issue. 03:07.960 --> 03:14.580 Is this, a third question is, is this browser, is this browser agnostic, or do you have to 03:14.580 --> 03:17.760 use Chrome? 03:17.760 --> 03:25.460 That's a good question. So obviously, as you've seen that, or just heard, it works in a number 03:25.460 --> 03:30.480 of other browsers. There's probably at least ten other browsers in which it will work. 03:30.480 --> 03:35.840 So there's sort of three families of extensions, one for Safari, one for Firefox, and one for 03:35.840 --> 03:47.580 Chrome, and often one of those extensions will work in a different browser. 03:47.580 --> 03:53.060 You mentioned, fourth question is, you mentioned a couple other solutions to allow Emacs editing 03:53.060 --> 04:02.600 of text areas, pointers. Well, unfortunately, I didn't do my due diligence in researching 04:02.600 --> 04:07.000 those other solutions. I'm aware that there's something called Emacs Everywhere that's supposed 04:07.000 --> 04:13.840 to have a similar capability, but I haven't dug into using it, so I can't say anything 04:13.840 --> 04:14.840 about it. 04:14.840 --> 04:27.040 I'll have to say that. So because you're setting up a server from an editor, and you have this 04:27.040 --> 04:35.520 extension in a browser, things don't always mesh. You may have port 4001 occupied by some 04:35.520 --> 04:43.720 other server from Emacs or another application, and so you have to sort that out. That can 04:43.720 --> 04:49.360 happen from time to time. I've had trouble with the Emacs server sometimes using that 04:49.360 --> 04:57.800 port, but I think you can redirect that Emacs server to another port to avoid that issue. 04:57.800 --> 05:02.240 That would be the greatest difficulty is just getting the two sides talking to each other 05:02.240 --> 05:10.160 through the web socket, but once that's going, I use it every day, and I'll go for weeks 05:10.160 --> 05:16.560 without any issue, and then, of course, I'll be changing something about Emacs configuration 05:16.560 --> 05:22.520 where I'm turning on some new server that fires up when I start Emacs, and then I break 05:22.520 --> 05:28.760 it there, or something along those lines, but the great hazard of fiddling with your 05:28.760 --> 05:49.520 Emacs configuration, just a hazard of being an Emacs user. Let's see. Why not save text? 05:49.520 --> 05:56.120 So I have a fifth question, which is why not save text from Emacs? I would like to hear 05:56.120 --> 06:04.560 some solution to the issue I ran into. So if I am editing a document in a web browser 06:04.560 --> 06:13.200 and then via Emacs, and I save that to a document on disk, then I, okay, that's great if I'm 06:13.200 --> 06:19.020 not going to make any more changes, everything's fine, that works great, but if I then decide 06:19.020 --> 06:27.200 to make more changes in the browser, and then I try to save those changes, the copy on disk 06:27.200 --> 06:32.280 is out of sync with the copy in the browser, and I've had the connection break when I do 06:32.280 --> 06:42.080 that. So I heard that there might be a way of solving that problem. I'm not, but I have 06:42.080 --> 06:48.040 not implemented the solution. I forget what the suggestion was. Maybe somebody in the 06:48.040 --> 06:51.840 audience has an idea. 06:51.840 --> 06:56.760 Speaking of the audience, we have opened up the chat now, so if you want to join the current 06:56.760 --> 07:02.200 BBB Discord room in which we are and ask questions directly to Blaine, feel free to do so, otherwise 07:02.200 --> 07:05.840 we're still taking questions on the pad as long as we have them, although right now I 07:05.840 --> 07:10.120 think we have answered all of them. Am I wrong, Blaine, or did we answer all of them already? 07:10.120 --> 07:13.200 You're correct, we've answered all of them. 07:13.200 --> 07:18.120 So we're going to still discuss for about 2-3 minutes. If people want to add last questions 07:18.120 --> 07:23.360 to the pad, feel free to do so. If you want to join us in BBB, the link is at the top 07:23.360 --> 07:28.140 of the talk of Blaine, Euclid Maxco 2022. You know everything now. We are at the end 07:28.140 --> 07:33.640 of the day, and you can tell it's the end of the day because my accent is getting significantly 07:33.640 --> 07:40.840 Frencher as a result. It's not getting any better since last year, I think. I wish I 07:40.840 --> 07:44.760 could contribute, Blaine, more to your talk, but I feel like I'm way out of my league. 07:44.760 --> 07:50.280 I'm the guy who plays with Org on the side, and I tune into your talks every year, and 07:50.280 --> 07:54.840 I see molecules, and I see stuff that I can barely comprehend, and I feel very humbled 07:54.840 --> 07:56.840 as a result. 07:56.840 --> 08:03.320 Well, I'm just trying to make my talks kind of unique. 08:03.320 --> 08:07.960 You are succeeding amazingly well. It reminds me, have you been talking with John Kinchin 08:07.960 --> 08:15.680 or something? Because you seem to be evolving in seminal fields, in a way, with Emacs. 08:15.680 --> 08:26.160 I have been. I'm a fan of his. I have installed CyMax and his configuration for Emacs, but 08:26.160 --> 08:33.960 I haven't. I've just started poking around with it, and I've used his configuration. 08:33.960 --> 08:43.280 I've got it up and running, and I've used GhostText with it, and I was trying to tap 08:43.280 --> 08:49.880 into his OrgRef package, which is super powerful for managing bibliographies. 08:49.880 --> 08:50.880 Yeah. 08:50.880 --> 08:53.880 Yeah, he's very inspiring. 08:53.880 --> 08:59.880 I'm glad to hear you're very much inspired. Go on, please. 08:59.880 --> 09:05.280 He's very amazing. He's very accomplished in Emacs and a very accomplished teacher, 09:05.280 --> 09:11.160 and he has now, as you probably know, a series of videos on YouTube that he's been putting 09:11.160 --> 09:18.920 together about programming. So he's teaching students at Carnegie Mellon University how 09:18.920 --> 09:26.200 to program in Python via Emacs, and he has been sharing these videos on YouTube, and 09:26.200 --> 09:30.720 they're like just 20-minute videos, kind of short snippets, but you can learn a lot from 09:30.720 --> 09:33.480 them. It's really fantastic. 09:33.480 --> 09:39.240 It's an amazing journey, isn't it? You start from a field that has nothing to do whatsoever 09:39.240 --> 09:43.800 with Emacs, and yet you find yourself so attracted to the idea of programming and making your 09:43.800 --> 09:49.620 workflow easier that you end up actually transitioning into a little bit of a programming role or 09:49.620 --> 09:54.900 teaching programming role. I mean, I was studying literature. I was all well and good in my 09:54.900 --> 10:00.040 English faculty, and then I decided to say, oh yeah, let's try Emacs, and 10 years later 10:00.040 --> 10:06.160 I find myself spending more time working on Emacs than working on my literature papers. 10:06.160 --> 10:12.920 My history is that I developed a dozen years ago, started teaching students how to do molecular 10:12.920 --> 10:17.960 graphics, and then I got into Python programming to develop tools to make it easier for them 10:17.960 --> 10:22.680 to use molecular graphics, and then evolved into making these snippets available for a 10:22.680 --> 10:29.680 wide range of text editors that meant learning about – so I prepared these snippets for 10:29.680 --> 10:35.440 about 20 different text editors, leading ones, and of course I saved for the end Emacs. First 10:35.440 --> 10:42.800 I went through Vim and the month of hell of rewiring your brain to do the Vim key bindings 10:42.800 --> 10:51.920 and then on to Emacs, which I call the ultimate text editor, because there is no other text 10:51.920 --> 10:56.040 editor beyond Emacs. It's the end of the line. 10:56.040 --> 11:01.360 I absolve you for your herrings with Vim as a result of the last comment you just made. 11:01.360 --> 11:05.680 Actually, no, I have new write of that solution. I can agree to your solution. You'll have 11:05.680 --> 11:09.200 to ask RMS tomorrow. 11:09.200 --> 11:16.800 Well, I spent a year in evil mode, but I switched about half a year ago to just Emacs key bindings 11:16.800 --> 11:24.840 and bye-bye Vim. I use Vim when I log into remote servers and have to edit something 11:24.840 --> 11:30.720 really quick, but I've probably forgotten most of the key bindings. There's only about 11:30.720 --> 11:36.560 a dozen you really need to know to get the essential work done. But yeah, it's been 11:36.560 --> 11:37.560 quite a journey. 11:37.560 --> 11:45.160 Sorry for the interruption. We do have one question, a very simple question about what 11:45.160 --> 11:51.200 was the key binding for Linux Firefox. Do you have it on top of your mind? 11:51.200 --> 11:52.200 So Linux Firefox. 11:52.200 --> 11:57.240 I'm not sure what they're referring to as well, which is why I threw you this purple, 11:57.240 --> 11:59.240 hoping that it would make sense for you. 11:59.240 --> 12:00.240 It's Control-Shift-H. 12:00.240 --> 12:14.120 I hope this answers your questions. So I think Control-Shift-H, yes. Well Blaine, I see some 12:14.120 --> 12:18.120 people have joined on BBB, but no one with a microphone still. I will tide you at the 12:18.120 --> 12:21.560 end. We are reaching the end of the day. We are reaching closing remarks and I will be 12:21.560 --> 12:26.720 making a plea for more people to join with a microphone. Last year we had pretty much 12:26.720 --> 12:30.440 the same setting. We were opening the room afterwards and people were showing up with 12:30.440 --> 12:33.760 the microphones and we had lovely discussions. So in this year, it feels like everyone's 12:33.760 --> 12:38.940 a little shy, shouldn't you know? That's the whole point is for you to talk and for 12:38.940 --> 12:43.160 us all to listen. Well Blaine, that was very insightful. Thank you so much for both the 12:43.160 --> 12:44.960 presentation and the questions. Go on. 12:44.960 --> 12:51.200 We have a question in the panel on the left and blue button. So how long have I been using 12:51.200 --> 13:03.520 Emacs? I made a commitment to use it full-time about 18 months ago, maybe 20 months ago. 13:03.520 --> 13:09.240 So I'm a newbie. I'm still in the steep part of the learning curve. 13:09.240 --> 13:13.640 You just have to provide context for the people. Blaine presented something at the last year's 13:13.640 --> 13:19.440 EmacsConf and it was as impressive as this year's presentation. And afterwards he told 13:19.440 --> 13:23.760 us, oh yeah, I've been using Emacs for six months or so. And that's where everyone's 13:23.760 --> 13:28.920 jewels dropped to the floor because some people have been using Emacs for 10 years and we 13:28.920 --> 13:31.960 couldn't even imagine doing some of the stuff you're doing with it. 13:31.960 --> 13:33.960 Thank you. 13:33.960 --> 13:40.880 Do we have any other questions? I think that's pretty much it. I'm not seeing anything appear 13:40.880 --> 13:48.520 on the other screen. I think we're pretty much good. So Blaine, I'm not going to keep 13:48.520 --> 13:52.880 you any longer. We are probably going to bring this Q&A to a close. Thank you so much for 13:52.880 --> 13:59.880 all the answers. What are we going to do for the stream? We still have a talk going on 13:59.880 --> 14:05.960 on the dev channel currently. And then we'll be going to the closing remarks for the day 14:05.960 --> 14:10.680 at about 55 of the current hour. So we are going on a break for 20 to 25 minutes. So 14:10.680 --> 14:14.040 Blaine, sorry for keeping you off stage as I'm making the announcement, but it's the 14:14.040 --> 14:16.520 best way for people to see my face as I do it. 14:16.520 --> 14:20.800 Thank you very much, Leo. I appreciate it. 14:20.800 --> 14:26.720 And thank you so much for all your time and all your answers. I will be closing BBB now 14:26.720 --> 14:31.600 and we will put some music on and some announcements and see you at the top of the hour for the 14:31.600 --> 14:57.720 others or 55 rather than top of the hour. All right. Bye bye everyone. Bye bye Blaine.