WEBVTT NOTE Introduction 00:00:00.000 --> 00:00:06.799 Yes. Okay. Hi, everyone. We are back now, and I'm with Mats. Hi, Mats. 00:00:06.800 --> 00:00:09.559 Hi. How are you doing? 00:00:09.560 --> 00:00:11.879 I'm fine. How are you? 00:00:11.880 --> 00:00:15.239 I'm doing great as well. As the talk goes by, 00:00:15.240 --> 00:00:20.119 I keep warming up, and this is a very nice feeling. I look absolutely big 00:00:20.120 --> 00:00:23.639 with this down jacket, but it works, and I'm not going to question it. 00:00:23.640 --> 00:00:27.039 You do know, for the people coming every year to AMX Conf, that I do try 00:00:27.040 --> 00:00:30.999 to look dashing, but I also need to be warm, because this year, 00:00:31.000 --> 00:00:33.359 we are doing it in December and not in November. 00:00:33.360 --> 00:00:36.639 Okay. So, Mats, 00:00:36.640 --> 00:00:40.599 how about you start reading questions? I believe you've got one already. NOTE So with one line of code you can create custom hyperbutton types that are live in any Emacs buffer. Is that right? 00:00:40.600 --> 00:00:45.719 I got one question already. Yes. The question is, so with one line of code, 00:00:45.720 --> 00:00:50.279 you can create custom hyper button types that are live in an AMX buffer. 00:00:50.280 --> 00:00:55.959 Is that right? Yes. The short answer is yes. 00:00:55.960 --> 00:01:01.599 Maybe I should use the presentation and go into here. 00:01:01.600 --> 00:01:09.759 Let's see if I can find it. 00:01:09.760 --> 00:01:17.839 No. Read it wrong. So, here, the field macro allows you, in principle, to, 00:01:17.840 --> 00:01:22.759 in one line, define a hyper button, starting with the starting delimiter 00:01:22.760 --> 00:01:25.519 and an end delimiter, and then there's this mapping 00:01:25.520 --> 00:01:36.319 to whatever functionality should sort of come out of pressing that button. 00:01:36.320 --> 00:01:39.199 So, that was significantly more than just a yes. Thank you. 00:01:39.200 --> 00:01:42.479 I'll be glad we put your screen up so that you can answer this. 00:01:42.480 --> 00:01:45.479 So, people, just to remind you, so we do have the pad to answer the pad 00:01:45.480 --> 00:01:49.039 to ask you questions over there. We are, let me check 00:01:49.040 --> 00:01:54.799 how much time we have for this Q&A. We have until 15 of the next hour, 00:01:54.800 --> 00:02:00.719 which leaves about 20 minutes, but right now we only have one question. 00:02:00.720 --> 00:02:07.519 So, people on ISE, if you could place questions in the pad. Right. 00:02:07.520 --> 00:02:10.679 Sorry, I'm managing multiple things at the same time. 00:02:10.680 --> 00:02:12.839 Is there anything else you wanted to talk about? Anything else? 00:02:12.840 --> 00:02:16.479 Because, you know, to let people know, 00:02:16.480 --> 00:02:19.719 we do ask speakers to submit pre-recordings to us 00:02:19.720 --> 00:02:21.639 because it makes our life much easier on the day 00:02:21.640 --> 00:02:25.519 of the recording at EmacsConf, on the day of the conference at EmacsConf, 00:02:25.520 --> 00:02:29.479 because this way we can get away with not having 00:02:29.480 --> 00:02:33.559 to worry about live presentation catching fires and not, oh, 00:02:33.560 --> 00:02:36.039 I cannot share my screen, my microphone is not working. 00:02:36.040 --> 00:02:40.439 So, not only is everything working today inside the BBBO room, 00:02:40.440 --> 00:02:44.159 but Matt also sent a pre-recording. So, that's great. 00:02:44.160 --> 00:02:50.079 I got another question. Oh yes, go, but please, I'm down in the background. 00:02:50.080 --> 00:02:53.319 Let me jump over to the second question. NOTE Is there a good way to share common patterns for links other than the ones that you shared? shall those be PRs to your repository? 00:02:53.320 --> 00:02:56.639 The second question is, is there a good way to share common patterns 00:02:56.640 --> 00:03:00.399 for links other than the ones that you shared? 00:03:00.400 --> 00:03:05.599 Shall those be pull requests to your repository? 00:03:05.600 --> 00:03:16.919 Okay, let me think. Those should not be pull requests to our repository 00:03:16.920 --> 00:03:19.999 because these are your patterns, your links. 00:03:20.000 --> 00:03:23.959 That's something you would share like that I'm showing here. 00:03:23.960 --> 00:03:27.239 Could even be like you're sharing maybe the pattern, how this 00:03:27.240 --> 00:03:31.599 button looks, but maybe the implementation could in principle be different. 00:03:31.600 --> 00:03:36.359 So, the one you're sharing with might put their information 00:03:36.360 --> 00:03:41.719 in some other storage that might be accessed using the same information, 00:03:41.720 --> 00:03:46.439 or maybe just placed in some other part of the file system. 00:03:46.440 --> 00:03:53.239 So, the only good way to share it would be like to send it over email 00:03:53.240 --> 00:03:57.519 or some other message to someone else. Share it some way. 00:03:57.520 --> 00:04:02.639 First question. I like the link to evaluate calc expressions. 00:04:02.640 --> 00:04:07.879 Any way to get the outcome into the buffer and not just in the message window? 00:04:07.880 --> 00:04:13.999 I mean, that will be up to the sort of the implementation of the function 00:04:14.000 --> 00:04:19.519 that you would use in the bottom. I mean, the function that 00:04:19.520 --> 00:04:25.999 is evaluated could do anything really. So, that was just an example 00:04:26.000 --> 00:04:30.519 to show that you could, you don't have to be a link that you actually go 00:04:30.520 --> 00:04:34.399 to some new place. It can just be some computation or whatever. So, 00:04:34.400 --> 00:04:39.519 that's just trying to show that you shouldn't be limiting yourself 00:04:39.520 --> 00:04:44.399 to just thinking about links. It can be computing anything. 00:04:44.400 --> 00:04:49.959 It's really the thing about Elisp really. It's just when people ask you, 00:04:49.960 --> 00:04:53.439 you know, when they come from outside of Emacs and they ask you, 00:04:53.440 --> 00:04:56.759 can your function do this? The answer is more often than not, yes. 00:04:56.760 --> 00:04:59.159 Can you write it in Elisp? Yeah, I might need 00:04:59.160 --> 00:05:01.839 to look at the documentation a little bit, but I'll be able to do it. 00:05:01.840 --> 00:05:06.239 And, you know, calc does have the ability to paste the result 00:05:06.240 --> 00:05:10.879 when you're not calc used as a library, but calc the node. 00:05:10.880 --> 00:05:13.319 When you type something in it and you press Y, 00:05:13.320 --> 00:05:17.119 it will paste it into the buffer, which means that there is the ability 00:05:17.120 --> 00:05:19.799 to communicate between calc and the buffer you're currently in. So, 00:05:19.800 --> 00:05:24.439 it's probably just a matter of doing Ctrl-H-K-Y inside the calc mode, 00:05:24.440 --> 00:05:27.719 checking which function is running, and just putting this at the end 00:05:27.720 --> 00:05:29.319 of the button, and voila, there you go. 00:05:29.320 --> 00:05:34.079 So, Matt, I don't think you have any questions at the moment. 00:05:34.080 --> 00:05:37.559 We're going to leave some time for people to gather more questions, 00:05:37.560 --> 00:05:41.839 but I think, if I'm not mistaken, I might be wrong with the, 00:05:41.840 --> 00:05:42.919 we changed the schedule a little bit, 00:05:42.920 --> 00:05:46.719 but you're the first Hyperbole talk for today, 00:05:46.720 --> 00:05:52.319 and as such, you are introducing people to the concept of buttons, 00:05:52.320 --> 00:05:56.719 which is very instrumental to Hyperbole. Hyperbole? 00:05:56.720 --> 00:06:00.639 I'm going to go with Hyperbole, actually. 00:06:00.680 --> 00:06:03.919 So, could you maybe, I know it's a big task, 00:06:03.920 --> 00:06:07.639 and you've also touched upon what Hyperbole was, but a lot 00:06:07.640 --> 00:06:10.599 of people always ask, you know, Hyperbole, Org Mode, 00:06:10.600 --> 00:06:13.559 I see both of them sometimes crop up at the top of the subreddit, 00:06:13.560 --> 00:06:16.519 and I'm not exactly sure which one is doing which. 00:06:16.520 --> 00:06:22.239 You're using the term links, and this speaks to me as someone who works 00:06:22.240 --> 00:06:24.359 in Zettelkasten Methods, so maybe 00:06:24.360 --> 00:06:27.479 could you, I'm asking you with a very difficult question now, NOTE Could you differentiate Hyperbole and Org? 00:06:27.480 --> 00:06:32.359 could you differentiate maybe Hyperbole and Org, or try your best, 00:06:32.360 --> 00:06:38.119 knowing that we'll have more Hyperbole talks later in the conference? 00:06:38.120 --> 00:06:45.959 Well, I will not try to get into that sort of wormhole, 00:06:45.960 --> 00:06:56.919 because I don't think they should be compared, they're more companions, so yeah. 00:06:56.920 --> 00:07:00.479 It's the best way you could have answered this question, and you know, 00:07:00.480 --> 00:07:04.799 I'm going to remove you from this tricky situation in which I put you, 00:07:04.800 --> 00:07:08.999 so yes, they are complementary tool, they do some of the same thing, 00:07:09.000 --> 00:07:11.639 they do have different philosophy, and at the end, 00:07:11.640 --> 00:07:13.079 if they allow you to take notes, 00:07:13.080 --> 00:07:15.999 if they allow you to relate notes in different places, 00:07:16.000 --> 00:07:19.239 you know, it's a good note-taking system. Let's put it at this, 00:07:19.240 --> 00:07:23.519 let's not concern ourselves with comparison, at least Org, you know, 00:07:23.520 --> 00:07:26.559 the best thing about comparing is cross-pollination, 00:07:26.560 --> 00:07:29.639 which is made all the more easier with something like Emacs, 00:07:29.640 --> 00:07:33.399 because ideas from one mode can be taken and applied in another mode. 00:07:33.400 --> 00:07:36.799 Now, maybe not straightforwardly between Hyperbole and Org, 00:07:36.800 --> 00:07:39.439 but the idea can be translated at the very least. 00:07:39.440 --> 00:07:42.959 You did have a question, I'll answer this one very quick, 00:07:42.960 --> 00:07:44.639 because it's a quick one. 00:07:44.640 --> 00:07:46.919 Yeah, yes, you want to take it? 00:07:46.920 --> 00:07:51.079 I just want to quickly follow up on what you said there, 00:07:51.080 --> 00:07:56.399 that, ah, now I lost, I lost it, maybe come back, 00:07:56.400 --> 00:07:59.039 so let's jump into the question instead, 00:07:59.040 --> 00:08:08.239 because I got an answer, so thank you for everybody who wrote the answer, 00:08:08.240 --> 00:08:13.359 great, and the next question was, this talk is really straightforward, 00:08:13.360 --> 00:08:16.119 so that's probably why there aren't many questions, 00:08:16.120 --> 00:08:19.959 maybe Mats could talk about Hyperbole in general, while he was, aha, okay, 00:08:19.960 --> 00:08:24.279 that's maybe what you were trying to do here, so maybe I should, 00:08:24.280 --> 00:08:27.719 and the last one is, second question, last question is, NOTE How did you present the right buffer with shortcuts at the right of your buffer? 00:08:27.720 --> 00:08:30.719 how did you present the lossage bar at the right of your buffer? 00:08:30.720 --> 00:08:36.639 A lot of people are wondering, the lossage bar, oh, well, you have 00:08:36.640 --> 00:08:41.399 to elaborate on what the lossage bar is. I can, although 00:08:41.400 --> 00:08:45.199 I do have a slight problem, my daily backup is running, 00:08:45.200 --> 00:08:48.639 so if my voice is crackly, I'm sorry, I can't do anything about it, 00:08:48.640 --> 00:08:49.279 can you hear me? 00:08:49.280 --> 00:08:51.719 Yeah, you're shopping up, 00:08:51.720 --> 00:08:57.319 but I can understand what you're saying, so that's great. 00:08:57.320 --> 00:09:01.719 So lossage is the stuff that you have on the right side of your screen, 00:09:01.720 --> 00:09:05.399 it's the commands that you're running and the key binding that you're using 00:09:05.400 --> 00:09:08.719 to run them, and yes, this is a mode that we ask, 00:09:08.720 --> 00:09:12.159 or that we provide Emacs on speakers with, 00:09:12.160 --> 00:09:16.599 and it's called interactive log mode, which is available on GitHub, 00:09:16.600 --> 00:09:21.079 which will allow you to have this pretty print on the right side of your screen, 00:09:21.080 --> 00:09:22.279 or whatever really, it's just a buffer. 00:09:22.280 --> 00:09:30.159 Yeah, and I haven't used it before doing this presentation, so it was a news 00:09:30.160 --> 00:09:38.559 to me, so I'm very new to using it, but it works. Well, if you move around, 00:09:38.560 --> 00:09:40.199 you see that, yeah. 00:09:40.200 --> 00:09:46.519 So for the people, we did open up the BBB chat room now, 00:09:46.520 --> 00:09:50.199 which means that again, if you go to the talk page for Matz, 00:09:50.200 --> 00:09:56.839 where this was Button, you will be able to join the BBB by clicking on the link, 00:09:56.840 --> 00:09:59.199 and you'll be able to ask questions right away to Matz. 00:09:59.200 --> 00:10:03.439 We've started a nice question about org hyperbole and stuff like this, 00:10:03.440 --> 00:10:06.559 but maybe we should, yes, I'm trying to save you here, 00:10:06.560 --> 00:10:09.679 maybe we should re-center on the buttons and what they can do, 00:10:09.680 --> 00:10:13.679 especially what we talked about Elisp, allowing buttons to be whatever, 00:10:13.680 --> 00:10:17.839 and since Matz, you have your Emacs available, 00:10:17.840 --> 00:10:21.279 it might be a good opportunity for you to show some of the buttons 00:10:21.280 --> 00:10:24.119 that you're using as well, maybe some different ones that you've presented. 00:10:24.120 --> 00:10:27.199 So if people want to join, that would be a great opportunity 00:10:27.200 --> 00:10:32.359 to ask your questions. We have about 20 more minutes of Q&A, 00:10:32.360 --> 00:10:36.199 and if we don't have any more people showing up 00:10:36.200 --> 00:10:40.319 and no more questions on the pad, we can also go on a little break, 00:10:40.320 --> 00:10:44.719 and I would appreciate this, but I'm also happy to stay. 00:10:44.720 --> 00:10:52.479 Yeah, I understand the interest, but there are more talks coming up 00:10:52.480 --> 00:10:58.199 in related to hyperbole, and I haven't prepared any cool stuff. NOTE Working with different support systems 00:10:58.200 --> 00:11:02.639 What I could mention that I think is cool, I will not demo that, 00:11:02.640 --> 00:11:09.919 but I work as a programmer, and then I have different support systems, 00:11:09.920 --> 00:11:16.719 which have these strings, identifiers that may be linked 00:11:16.720 --> 00:11:23.799 to different information, like a ticketing system, for instance, 00:11:23.800 --> 00:11:29.199 that would do bugs. It could be like a novel text string 00:11:29.200 --> 00:11:38.639 that identify your bug or your ticket, and it's an internal tool, 00:11:38.640 --> 00:11:42.799 so no one else can support that, but by using hyperbole, 00:11:42.800 --> 00:11:46.839 I can write my own interpretation of that string 00:11:46.840 --> 00:11:49.999 and get that to work as a button, so I can easily 00:11:50.000 --> 00:11:56.279 from the code or from some notes link directly into that ticketing system. 00:11:56.280 --> 00:12:03.919 So that's the point I'm trying to make with this talk is 00:12:03.920 --> 00:12:07.839 that it's useful for setting up your own environment 00:12:07.840 --> 00:12:11.719 that only you really know about and how you want to navigate 00:12:11.720 --> 00:12:20.599 with your information, and it's not about trying to force some type 00:12:20.600 --> 00:12:25.719 of work stream upon anybody. It's more like giving you the opportunity 00:12:25.720 --> 00:12:28.319 to streamline your own workflow instead. 00:12:28.320 --> 00:12:33.479 I think the remaining talks about hyperbole will be more focused 00:12:33.480 --> 00:12:38.199 on all the features. It's a multi-functional package 00:12:38.200 --> 00:12:40.119 with a lot of different stuff in it, 00:12:40.120 --> 00:12:46.999 so I could not give justice to it in just doing some quick demos. 00:12:47.000 --> 00:12:49.119 It won't show all the things you can do. 00:12:49.120 --> 00:12:52.639 Yeah, but I'm going to say for someone saying 00:12:52.640 --> 00:12:54.839 that you couldn't do justice to the topic, 00:12:54.840 --> 00:12:58.079 you've done a very fine job, so do not worry about this. 00:12:58.080 --> 00:13:01.759 It's funny, I was listening to you describe this, the 00:13:01.760 --> 00:13:03.759 buttons really, but when 00:13:03.760 --> 00:13:06.839 you think about it, you could have forgotten about the buttons 00:13:06.840 --> 00:13:11.239 and really remembered about Emacs and would make as much sense as well, 00:13:11.240 --> 00:13:14.799 because Emacs as a whole, the Elisp stuff behind it allows you 00:13:14.800 --> 00:13:17.039 to do whatever interface you want very easily, 00:13:17.040 --> 00:13:23.759 and the buttons really enshrines the interface type of things really, 00:13:23.760 --> 00:13:26.399 because you just have a button that is running code. 00:13:26.400 --> 00:13:27.799 It's no longer, oh, you need to go to 00:13:27.800 --> 00:13:30.079 the end of the parenthesis, the end of the sex, 00:13:30.080 --> 00:13:32.879 and you need to evaluate it. There's something more interactive about it, 00:13:32.880 --> 00:13:35.879 which feels closer to your user interface as a result to this, 00:13:35.880 --> 00:13:37.959 but I've already blabbered enough. 00:13:37.960 --> 00:13:40.639 We do have someone with a microphone in the VBB chat, 00:13:40.640 --> 00:13:43.399 so does this person want to unmute themselves 00:13:43.400 --> 00:13:44.279 and ask a question, maybe? 00:13:44.280 --> 00:13:52.879 I think I have some very knowledgeable person about hyperbole in the chat. 00:13:52.880 --> 00:13:57.639 Yes, I didn't want to spoil it, but I'm not sure if they're going 00:13:57.640 --> 00:14:00.759 to unmute themselves, so I don't want to put too much pressure on them. 00:14:00.760 --> 00:14:03.519 Can you guys hear me? We can, yes. 00:14:03.520 --> 00:14:09.879 Hi, Bob. Hi, long time fan of hyperbole. 00:14:09.880 --> 00:14:12.919 You might want to cue people in on a joke here, 00:14:12.920 --> 00:14:14.599 because I'm not sure if anyone knows who you are. NOTE Bob Weiner 00:14:14.600 --> 00:14:19.879 I wrote hyperbole, and Matt's my co-maintainer on it, 00:14:19.880 --> 00:14:23.159 so really exciting to have the first talk here. 00:14:23.160 --> 00:14:26.879 I think I just wanted to mention two things. 00:14:26.880 --> 00:14:28.879 Maybe you could show a little key series, 00:14:28.880 --> 00:14:33.879 just type one out dynamically and show how simple that is, 00:14:33.880 --> 00:14:39.639 and then talk about the UKIPA daily journal, 00:14:39.640 --> 00:14:45.479 right? Time-stamped journal that was originally org mode, 00:14:45.480 --> 00:14:49.479 and I think you're now using Hyperbole's K-outliner, 00:14:49.480 --> 00:14:56.319 so maybe mention doing that. Okay. 00:14:56.320 --> 00:14:59.959 Something that's more than one key sequence, please. 00:14:59.960 --> 00:15:09.199 Do a couple operations that you do a lot of or that are interesting, 00:15:09.200 --> 00:15:10.839 all in one. 00:15:10.840 --> 00:15:15.719 So the key series is like a keyboard macro, 00:15:15.720 --> 00:15:20.879 so it's not limited to one key sequence, 00:15:20.880 --> 00:15:27.199 but any series of key sequences can be strung together 00:15:27.200 --> 00:15:28.879 just like that with nothing else, 00:15:28.880 --> 00:15:35.399 and then you activate it the same way as any other button, right? 00:15:35.400 --> 00:15:38.079 Yes, but you're putting me on the spot here, 00:15:38.080 --> 00:15:41.199 because now I have to remember, actually, how to write these things. 00:15:41.200 --> 00:15:46.079 You just write it the way you would type it. 00:15:46.080 --> 00:15:49.479 Yeah, I see it. 00:15:49.480 --> 00:16:00.079 Okay, so let's see. So the key series is between these braces and... 00:16:00.080 --> 00:16:05.159 And you could leave out the quote marks if you don't... 00:16:05.160 --> 00:16:07.639 Maybe I can skip that as well. 00:16:07.640 --> 00:16:09.559 So here's the key series. 00:16:09.560 --> 00:16:10.919 Let's see what's happening. 00:16:10.920 --> 00:16:12.999 Do I go to the 10th folder or not? 00:16:13.000 --> 00:16:16.119 Boom, I got there. Yeah, it worked. 00:16:16.120 --> 00:16:23.159 Bob, great. So you can name them and then reuse them, 00:16:23.160 --> 00:16:29.119 and so it's sort of like you've got this toolkit that you can embed 00:16:29.120 --> 00:16:31.919 in all these different modes that you have in Emacs, 00:16:31.920 --> 00:16:34.639 and you just carry it with you. 00:16:34.640 --> 00:16:38.759 It's not like a whole mode unto itself that you always have to use. 00:16:38.760 --> 00:16:46.599 Yeah, so in this example here with the field, you can, 00:16:46.600 --> 00:16:52.119 instead of having like this path string here, 00:16:52.120 --> 00:16:54.359 you can have a key series as well. 00:16:54.360 --> 00:17:01.399 But to the other point, also, Elisp is available, 00:17:01.400 --> 00:17:02.959 but this is even more available 00:17:02.960 --> 00:17:05.959 because you don't even have to code using Elisp. 00:17:05.960 --> 00:17:09.079 So that's the point also with this, the fill and the file macros. 00:17:09.080 --> 00:17:11.879 You should make it even simpler. 00:17:11.880 --> 00:17:15.519 And if you just know how to type some command, 00:17:15.520 --> 00:17:18.679 you can use the key series together with this 00:17:18.680 --> 00:17:21.359 to get some functionality out of this. 00:17:21.360 --> 00:17:26.399 I think one of the things we've taken to saying about Hyperbole 00:17:26.400 --> 00:17:31.239 is it's kind of the lightest hypertext markup 00:17:31.240 --> 00:17:35.159 that you can have, as you saw there, right? 00:17:35.160 --> 00:17:37.519 I mean, there were just braces, and all of a sudden, 00:17:37.520 --> 00:17:40.999 it's a live hyper button. So we've tried to strip away 00:17:41.000 --> 00:17:44.879 having to write stuff like HTML or even all the drawers 00:17:44.880 --> 00:17:47.519 and stuff like that, and we've tried to make it so that you know, 00:17:47.520 --> 00:17:51.439 even all the like drawers and the property markup in org mode, 00:17:51.440 --> 00:17:57.679 and just provide very, very simple sort of syntactical things similar 00:17:57.680 --> 00:18:01.679 to what Elisp does, so that you can get a lot of power 00:18:01.680 --> 00:18:07.999 and put buttons everywhere, but not have to recognize a lot of syntax 00:18:08.000 --> 00:18:11.639 or use a whole bunch of keys on your buttons. 00:18:11.640 --> 00:18:16.039 It's pretty interesting, 00:18:16.040 --> 00:18:16.679 by the way. 00:18:16.680 --> 00:18:17.959 I'm sorry I have to do this, 00:18:17.960 --> 00:18:20.519 but we only have about five more minutes in the Q&A before we need 00:18:20.520 --> 00:18:24.039 to move on to the next talk. But don't worry, you've had a little test 00:18:24.040 --> 00:18:27.079 of Hyperbole right there, and you'll have more over the weekend. 00:18:27.080 --> 00:18:30.319 We've had a lot of Hyperbole talk this year, which is amazing. 00:18:30.320 --> 00:18:33.559 You know, we usually have a lot of talk about org, but this year 00:18:33.560 --> 00:18:37.479 is truly the one where we also have a similar amount of Hyperbole talk, 00:18:37.480 --> 00:18:42.399 which is amazing to see. Obviously, I am more of an org guy, 00:18:42.400 --> 00:18:45.679 but I see so many parallels between the two, so many bridges 00:18:45.680 --> 00:18:50.319 that could be built as well, and it's amazing to see the amount of passion 00:18:50.320 --> 00:18:53.439 that goes into this. Usually I deal with people who are passionate about org, 00:18:53.440 --> 00:18:56.719 but to see that there's a similar amount of passion on the Hyperbole side 00:18:56.720 --> 00:18:58.279 of things is truly amazing to me. 00:18:58.280 --> 00:19:04.799 I think we had one more question in the pad, if you can take it, Matt. NOTE Do the links/buttons created in hyperbole (like that one with the url) get exported on org-mode files too? (like when exported to html) 00:19:04.800 --> 00:19:10.639 Yeah, the last here is, does the links buttons create in Hyperbole, 00:19:10.640 --> 00:19:16.159 like the one with the URL get exported on org mode files too, 00:19:16.160 --> 00:19:18.999 like when exported to HTML? 00:19:19.000 --> 00:19:21.039 Oh, tricky question. 00:19:21.040 --> 00:19:31.519 I mean, these implicit buttons, they are just like the patterns. 00:19:31.520 --> 00:19:35.319 So the pattern will of course be exported to HTML, 00:19:35.320 --> 00:19:37.439 but you will not be able maybe 00:19:37.440 --> 00:19:43.519 to do something there unless you're watching the HTML within Emacs, 00:19:43.520 --> 00:19:50.199 so the sort of Hyperbole machinery would be available, if that makes sense. 00:19:50.200 --> 00:19:58.359 I mean, yeah, it's possible. It depends what the encoding is, 00:19:58.360 --> 00:20:03.999 what the encoding is, but we do have an outliner mode, the K outliner 00:20:04.000 --> 00:20:10.439 in Hyperbole as well, and that has a single command export to HTML. 00:20:10.440 --> 00:20:13.879 So if you've embedded URLs in there, 00:20:13.880 --> 00:20:19.519 you would see them just like if you embedded them in org mode, 00:20:19.520 --> 00:20:25.559 and potentially the org exporter, if you just write a raw URL, 00:20:25.560 --> 00:20:30.119 will also encode it for you when you export it. 00:20:30.120 --> 00:20:35.039 There's other Hyperbole buttons in there. Yeah, but the functionality that 00:20:35.040 --> 00:20:38.159 is by clicking on that button will not be exported. 00:20:38.160 --> 00:20:44.079 Well, it's like you can try printing the button, I'm not sure. No amount 00:20:44.080 --> 00:20:46.479 of clicking on it is actually going to trigger an action. 00:20:46.480 --> 00:20:51.639 I might be wrong though. Sorry, I mean printing on paper, 00:20:51.640 --> 00:20:55.799 it's a very confusing terminology that we're using right there, not printing 00:20:55.800 --> 00:20:56.759 in a terminal. 00:20:56.760 --> 00:21:02.359 One cool thing if you use the Hyperbole export to HTML is 00:21:02.360 --> 00:21:07.519 that you can expand and collapse your trees in the HTML. 00:21:07.520 --> 00:21:10.439 I don't think you can do that with the org export right now. 00:21:10.440 --> 00:21:15.999 But Bob, you're going to show something about that tomorrow, right? 00:21:16.000 --> 00:21:21.319 I don't think it's in this presentation because I'm- Oh, it's not 00:21:21.320 --> 00:21:25.079 in the presentation, okay. On the org side of the house this time, 00:21:25.080 --> 00:21:32.879 but it'll be in a different one about Hyperbole some other time. All right, 00:21:32.880 --> 00:21:36.199 so we have about two minutes until we need to go to the next talk, 00:21:36.200 --> 00:21:38.479 but thank you so much, Matz, and thank you so much, Bob, 00:21:38.480 --> 00:21:41.839 also for showing up and giving us a taste of what is probably going 00:21:41.840 --> 00:21:44.759 to follow up tomorrow. I can't remember, I think your talk is 00:21:44.760 --> 00:21:51.599 in the afternoon, right, Bob? Correct, about 1 p.m. EST. Yeah, so 00:21:51.600 --> 00:21:56.959 in about 22 hours, 23 hours. I'm trying my best to give you times 00:21:56.960 --> 00:21:59.119 which are time zone independence, 00:21:59.120 --> 00:22:01.839 so I'm sorry if I'm missing the mark a little bit, 00:22:01.840 --> 00:22:04.679 but hopefully this would be useful for many people. But otherwise, 00:22:04.680 --> 00:22:07.719 just check the schedule and you'll be able to get everything. All right, well, 00:22:07.720 --> 00:22:09.999 thank you so much, Matz, for answering so many questions 00:22:10.000 --> 00:22:12.839 and for your presentation as well. I feel like it was good 00:22:12.840 --> 00:22:16.599 to have your presentation before Bob's one tomorrow, 00:22:16.600 --> 00:22:22.039 because focusing on the one aspect of Hyperbole, the buttons, and linking it 00:22:22.040 --> 00:22:26.119 to Elisp, linking it to interactivity, linking it to UI, I think is going 00:22:26.120 --> 00:22:29.239 to prime people to then understand fully what Hyperbole, 00:22:29.240 --> 00:22:34.319 or what are the capabilities of Hyperbole, beyond this, or inspired by this. 00:22:34.320 --> 00:22:37.199 So thank you so much. Thanks, Matz. Thank you. 00:22:37.200 --> 00:22:38.599 Great. 00:22:38.600 --> 00:22:42.519 All right, and we are going live with the next talk in about 30 seconds. 00:22:42.520 --> 00:22:45.519 I think we're going to close the BBB room, 00:22:45.520 --> 00:22:49.759 because nobody has showed up otherwise. So I will see you both later. 00:22:49.760 --> 00:22:50.599 Bye-bye. 00:22:50.600 --> 00:22:54.000 Bye-bye.