diff options
Diffstat (limited to '')
| -rw-r--r-- | 2022/captions/emacsconf-2022-science--writing-and-organizing-literature-notes-for-scientific-writing--vidianos--answers.vtt | 1232 |
1 files changed, 1232 insertions, 0 deletions
diff --git a/2022/captions/emacsconf-2022-science--writing-and-organizing-literature-notes-for-scientific-writing--vidianos--answers.vtt b/2022/captions/emacsconf-2022-science--writing-and-organizing-literature-notes-for-scientific-writing--vidianos--answers.vtt new file mode 100644 index 00000000..6ad95d62 --- /dev/null +++ b/2022/captions/emacsconf-2022-science--writing-and-organizing-literature-notes-for-scientific-writing--vidianos--answers.vtt @@ -0,0 +1,1232 @@ +WEBVTT + +00:00:00.000 --> 00:00:06.000 + I'm fine. So we can start, right? + +00:00:06.000 --> 00:00:09.100 + Yeah, sure. I mean, you pretty much know the drill. + +00:00:09.100 --> 00:00:11.050 + Everyone watching the show now already knows the drill. V + +00:00:11.050 --> 00:00:13.090 +idianus is going to read the questions. If you want to read + +00:00:13.090 --> 00:00:16.000 + the questions on your own, you can open up the pad. + +00:00:16.000 --> 00:00:18.080 + Otherwise, Vidianus will be reading the questions and + +00:00:18.080 --> 00:00:20.210 + answering them in line. And I'll be making jazz in the + +00:00:20.210 --> 00:00:22.780 + background whenever something doesn't work. So Vidianus, + +00:00:22.780 --> 00:00:24.000 + the floor is yours. + +00:00:24.000 --> 00:00:32.310 + Okay. So do you use flitting notes as well? Do you keep + +00:00:32.310 --> 00:00:33.780 + them in the org room? And flitting notes are a very + +00:00:33.780 --> 00:00:35.580 + interesting subject. In the initial draft of this talk, I + +00:00:35.580 --> 00:00:37.330 + wanted to include flitting notes as well, but it would take + +00:00:37.330 --> 00:00:40.000 + a bit too long. So I said, let's not do it. + +00:00:40.000 --> 00:00:43.980 + I'm going to add a link here to my .files in the section + +00:00:43.980 --> 00:00:48.350 + for flitting notes. But I can very quickly share my screen + +00:00:48.350 --> 00:00:52.970 + for a moment and show you something about it. So give me a + +00:00:52.970 --> 00:00:54.000 + moment. + +00:00:54.000 --> 00:01:00.000 + Yes, you can do this. + +00:01:00.000 --> 00:01:05.000 + Okay. So you see the screen now, I think? + +00:01:05.000 --> 00:01:08.000 + Yes, I can see it. + +00:01:08.000 --> 00:01:13.590 + So I have a key binding which opens my daily note. I have + +00:01:13.590 --> 00:01:17.490 + some notes from other talks in EmacsConf and talks that I'm + +00:01:17.490 --> 00:01:21.400 + going to miss due to the two tracks. Don't mind them. So I + +00:01:21.400 --> 00:01:28.000 + write, for example, flitting note. + +00:01:28.000 --> 00:01:31.890 + And I have a command down here which will automatically + +00:01:31.890 --> 00:01:35.760 + give it a to do value. So let's say, for example, I'm + +00:01:35.760 --> 00:01:40.000 + crossing it. It adds a tag to the current projects node, + +00:01:40.000 --> 00:01:44.840 + which is essentially a node I have for things I want to do + +00:01:44.840 --> 00:01:46.000 + right now. + +00:01:46.000 --> 00:01:52.590 + It makes it an org-rem node. And then I can write something + +00:01:52.590 --> 00:01:59.360 + here, blah, blah, blah. And if I go on org-rem node find, + +00:01:59.360 --> 00:02:04.000 + actually, I need to save it first. It will appear here. + +00:02:04.000 --> 00:02:10.720 + And then once I say it's done, it is not a node anymore. It + +00:02:10.720 --> 00:02:16.470 + is removed here. This allows me to archive things. I can + +00:02:16.470 --> 00:02:21.320 + stop the sharing now. This allows me to archive flitting + +00:02:21.320 --> 00:02:22.000 + notes. + +00:02:22.000 --> 00:02:26.860 + So I don't need -- because flitting notes are not something + +00:02:26.860 --> 00:02:31.740 + that needs to remain my shell custom. I want them for some + +00:02:31.740 --> 00:02:34.000 + point and then deleting them. + +00:02:34.000 --> 00:02:38.140 + And this is done with org-journal and not org-rem-dailys + +00:02:38.140 --> 00:02:41.960 + because with org-journal I can have this -- I make it a + +00:02:41.960 --> 00:02:45.000 + node and then I remove it from a node. + +00:02:45.000 --> 00:02:48.620 + While I don't think you can do that with org-rem-dailys, + +00:02:48.620 --> 00:02:52.020 + the code for all of this is in the section I pasted on the + +00:02:52.020 --> 00:02:57.000 + etherpad. And if you have any questions, you can email me. + +00:02:57.000 --> 00:03:11.240 + >> Okay. >> Sorry, just to specify, all the contact + +00:03:11.240 --> 00:03:11.560 + information will be available on the talk page. So be it + +00:03:11.560 --> 00:03:12.020 + the email to Vidianos, also the pads, the recording, + +00:03:12.020 --> 00:03:14.590 + everything will be available after the conference as soon + +00:03:14.590 --> 00:03:16.000 + as we have the bandwidth for this. + +00:03:16.000 --> 00:03:18.950 + So that's where you'll be able to find contact information. + +00:03:18.950 --> 00:03:21.000 + Okay. You can keep going, Vidianos. Sorry for the inter + +00:03:21.000 --> 00:03:21.000 +ruption. + +00:03:21.000 --> 00:03:25.630 + >> Okay. So the second question is if it works for PDFs + +00:03:25.630 --> 00:03:31.400 + only or Word and Excel or EPUB, websites, CWW and YouTube. + +00:03:31.400 --> 00:03:37.520 + So I'm not sure. Give me a moment to look at OrgNotor and + +00:03:37.520 --> 00:03:41.400 + see if it says -- because I said I didn't remember. Use it + +00:03:41.400 --> 00:03:43.000 + with PDFs typically. + +00:03:43.000 --> 00:03:48.370 + >> Yes. From the top of my mind, I think OrgNotor works + +00:03:48.370 --> 00:03:53.580 + with EPUB file via the package that is managed I think by + +00:03:53.580 --> 00:03:57.250 + -- was it by Wasamasa? I can't remember actually now. But + +00:03:57.250 --> 00:03:59.000 + at some point it was managed by Wasamasa. + +00:03:59.000 --> 00:04:07.550 + He was probably watching right now and probably yelling at + +00:04:07.550 --> 00:04:16.000 + me in the background. So I'll keep you posted on this. But + +00:04:16.000 --> 00:04:16.000 + yes, the OrgNotor allows you mostly to take notes on PDF + +00:04:16.000 --> 00:04:16.000 + via PDFView, but it also allows you to take notes on EPUB. + +00:04:16.000 --> 00:04:16.000 + And they're working relatively well. + +00:04:16.000 --> 00:04:19.000 + But as for the other -- yeah, go on, Vidianos. + +00:04:19.000 --> 00:04:22.840 + >> I opened OrgNotor and it says it also is compatible with + +00:04:22.840 --> 00:04:27.000 + DocView for Office, so Word, Excel and things like that. + +00:04:27.000 --> 00:04:30.430 + >> Yeah. And otherwise, if you really want to take notes on + +00:04:30.430 --> 00:04:33.760 + such documents, you can probably use either OrgConvert or + +00:04:33.760 --> 00:04:37.210 + Pandoc to generate a document that would be editable within + +00:04:37.210 --> 00:04:40.200 + OrgNotor. It shouldn't be too difficult to do so. And + +00:04:40.200 --> 00:04:43.400 + usually it's mostly PDFs when you're working on research + +00:04:43.400 --> 00:04:45.000 + stuff or stuff like this. + +00:04:45.000 --> 00:04:47.110 + Anyway, sorry for interrupting. This is a topic very dear + +00:04:47.110 --> 00:04:49.570 + to my heart as well because as you know, I have worked a + +00:04:49.570 --> 00:04:52.000 + little bit in OrgGram and OrgNotor especially. + +00:04:52.000 --> 00:04:58.560 + >> Yeah. So I think you should be able to do Word, Excel + +00:04:58.560 --> 00:05:03.000 + and EPUB. I don't think it works with websites and it + +00:05:03.000 --> 00:05:07.240 + definitely doesn't work with videos. Not sure if there's + +00:05:07.240 --> 00:05:09.000 + other solutions for those. + +00:05:09.000 --> 00:05:11.950 + >> I believe there is one. Sorry, I keep inserting myself + +00:05:11.950 --> 00:05:15.070 + into the discussion. This is a very interesting topic. I + +00:05:15.070 --> 00:05:18.290 + think Alfred Papa developed an Org package to capture a + +00:05:18.290 --> 00:05:21.570 + webpage. So it's like an OrgCapture, you know, Org protocol + +00:05:21.570 --> 00:05:24.000 + that allows you to capture stuff from your browser. + +00:05:24.000 --> 00:05:27.410 + It allows you to capture a page and basically Pandocs the + +00:05:27.410 --> 00:05:31.050 + results into an HTML, sorry, it Pandocs from HTML to an Org + +00:05:31.050 --> 00:05:34.860 + document with a structure and a hierarchy. And this way you + +00:05:34.860 --> 00:05:38.030 + can actually take notes on the documents and just have all + +00:05:38.030 --> 00:05:41.000 + the features you would expect in an Org document. + +00:05:41.000 --> 00:05:49.460 + >> I'll shut up now. This is your talk, not mine. If I + +00:05:49.460 --> 00:05:58.280 + really wanted to talk about this, I should have made a talk + +00:05:58.280 --> 00:06:00.000 +. Anyway, back to you. + +00:06:00.000 --> 00:06:04.160 + >> Okay. So next one. I used Take Notes on PDF with OrgNot + +00:06:04.160 --> 00:06:08.500 +er, but Zotero PDF Reader is also very nice. So, okay. Yeah, + +00:06:08.500 --> 00:06:12.280 + I have seen the Zotero PDF Reader. It does look nice as + +00:06:12.280 --> 00:06:16.000 + well, I would agree, but I have two problems with it. + +00:06:16.000 --> 00:06:21.310 + One, Emacs key bindings don't work, and two, it's not Emacs + +00:06:21.310 --> 00:06:26.330 +. Basically, I think it's nice, but I want to use things + +00:06:26.330 --> 00:06:31.790 + that are outside Emacs for as little as possible. And I use + +00:06:31.790 --> 00:06:36.310 + it there because I haven't found a way in Emacs to save the + +00:06:36.310 --> 00:06:41.000 + article somewhere and download the PDF automatically. + +00:06:41.000 --> 00:06:46.170 + I know there is DOI Utils, which was mentioned by RC a few + +00:06:46.170 --> 00:06:51.610 + moments ago as well, but it hasn't worked perfectly for me + +00:06:51.610 --> 00:06:56.730 + in the past when I tried it, so I use Zotero for that, but + +00:06:56.730 --> 00:07:01.900 + I wouldn't use it for the PDF Reader as well because I want + +00:07:01.900 --> 00:07:04.000 + to use it in Emacs. + +00:07:04.000 --> 00:07:07.590 + Next one. Thanks for saying that it was a great + +00:07:07.590 --> 00:07:12.500 + presentation. My thoughts on the future of Zelle Casten. I + +00:07:12.500 --> 00:07:18.980 + think Zelle Casten has a bright future, personally, because + +00:07:18.980 --> 00:07:24.000 + it is plain text. Plain text will never go away, basically. + +00:07:24.000 --> 00:07:28.610 + You will be able to use it forever, and also, Orgrom is + +00:07:28.610 --> 00:07:33.630 + open source with a very vibrant community, so that won't go + +00:07:33.630 --> 00:07:39.640 + away either anytime soon, I think. So, it probably has a + +00:07:39.640 --> 00:07:44.000 + future, if you mean it that way. + +00:07:44.000 --> 00:07:49.480 + And I think that, in general, it is a noting method that is + +00:07:49.480 --> 00:07:55.040 + very efficient. I have used it for university the past few + +00:07:55.040 --> 00:08:01.300 + years, and I have right now like 850 notes on it, and they + +00:08:01.300 --> 00:08:05.000 + will probably only keep increasing. + +00:08:05.000 --> 00:08:11.250 + So, I don't think it's going away. If you want to ask + +00:08:11.250 --> 00:08:16.000 + anything else, we can talk more about it. + +00:08:16.000 --> 00:08:19.970 + Actually, I do have something to add to this particular + +00:08:19.970 --> 00:08:24.010 + point, because on the topic of Zelle Casten and how useful + +00:08:24.010 --> 00:08:27.470 + it can be. Now, it's been a little while since Zelle Casten + +00:08:27.470 --> 00:08:32.630 + really started exploding. I think in 2020, right when COVID + +00:08:32.630 --> 00:08:35.200 + started, a lot of people started getting interested in Z + +00:08:35.200 --> 00:08:36.000 +elle Casten methods. + +00:08:36.000 --> 00:08:39.570 + And ever since, we have a lot of software that were + +00:08:39.570 --> 00:08:43.940 + released, including the ones we have in Orgrom. I'm going + +00:08:43.940 --> 00:08:47.940 + to use Orgrom because it's the one I'm most familiar with + +00:08:47.940 --> 00:08:51.700 + as a commentator, but we also have D-Notes by Prot and + +00:08:51.700 --> 00:08:54.000 + other solutions as well. + +00:08:54.000 --> 00:08:58.310 + And one thing that I'm currently working on, and a key area + +00:08:58.310 --> 00:09:02.240 + of interest for me, is how do we use the concept of Zelle + +00:09:02.240 --> 00:09:06.700 + Casten, a collection of notes. Generally, when you think of + +00:09:06.700 --> 00:09:10.280 + Zelle Casten, it's a really individual collection of notes, + +00:09:10.280 --> 00:09:11.000 + right? + +00:09:11.000 --> 00:09:14.550 + It's something that you have, it's the stuff that you find + +00:09:14.550 --> 00:09:18.280 + during your research, during the paper that you read. But + +00:09:18.280 --> 00:09:21.700 + how about trying to have a slipbox for a group of people, + +00:09:21.700 --> 00:09:25.060 + so that they could start sharing notes on research that + +00:09:25.060 --> 00:09:26.000 + they do. + +00:09:26.000 --> 00:09:29.190 + It wouldn't be the same thing as a personal slipbox, but + +00:09:29.190 --> 00:09:32.100 + you can think of it as the knowledge bank for a group of + +00:09:32.100 --> 00:09:35.420 + people, where they keep track of the concept that they use + +00:09:35.420 --> 00:09:38.810 + within their organization, the patterns that they like to + +00:09:38.810 --> 00:09:41.000 + use when they work together. + +00:09:41.000 --> 00:09:44.390 + So, we actually wanted to do a talk this year on some of + +00:09:44.390 --> 00:09:47.960 + those adjacent topics, but sadly, we were a little taken by + +00:09:47.960 --> 00:09:51.600 + time, and you'll have to wait for next year. But I will + +00:09:51.600 --> 00:09:55.540 + agree with you, Vidianos, there's a lot of very interesting + +00:09:55.540 --> 00:09:59.380 + stuff abound for Zelle Casten method, and especially Zelle + +00:09:59.380 --> 00:10:01.000 + Casten inside Emacs. + +00:10:01.000 --> 00:10:03.000 + All right, back to you now. + +00:10:03.000 --> 00:10:06.850 + Thanks for the additions, I like them as well, and I think + +00:10:06.850 --> 00:10:10.240 + that what you said about collaboration, it would be very + +00:10:10.240 --> 00:10:12.000 + interesting, really. + +00:10:12.000 --> 00:10:14.000 + Great. + +00:10:14.000 --> 00:10:18.070 + The only problem is having other people using the same + +00:10:18.070 --> 00:10:19.000 + methods with you. + +00:10:19.000 --> 00:10:24.420 + Sorry, Vidianos, I'm not sure if you asked me a question, I + +00:10:24.420 --> 00:10:29.740 + was at a health, whispering my ear in the background at the + +00:10:29.740 --> 00:10:31.000 + same time. + +00:10:31.000 --> 00:10:34.870 + I just said that I really like the idea that you said about + +00:10:34.870 --> 00:10:36.000 + collaboration. + +00:10:36.000 --> 00:10:38.830 + Yeah, because it is really something that is missing when + +00:10:38.830 --> 00:10:42.200 + you think about it. Like, the good thing about Emacs, and + +00:10:42.200 --> 00:10:44.900 + the philosophy of Emacs generally, is that we have + +00:10:44.900 --> 00:10:48.390 + different modes working together, and they do one thing, or + +00:10:48.390 --> 00:10:51.000 + multiple things, and they do it very well. + +00:10:51.000 --> 00:10:54.890 + We have org mode for editing structured documents, we have + +00:10:54.890 --> 00:10:58.200 + maggots to manage repositories, we have calc to do + +00:10:58.200 --> 00:11:02.000 + calculations with a polished notation and whatnot. + +00:11:02.000 --> 00:11:04.960 + It feels like we have a great tool for collaboration, + +00:11:04.960 --> 00:11:08.050 + editing a singular buffer, which is CRDT, which we've + +00:11:08.050 --> 00:11:10.000 + already talked about before. + +00:11:10.000 --> 00:11:13.420 + I'm not sure if we did have a presentation on Emacs about + +00:11:13.420 --> 00:11:17.130 + CRDT. I think, if you're more interested in this, go back + +00:11:17.130 --> 00:11:20.410 + to the talk I did last year with Joe Connelly and Noura El + +00:11:20.410 --> 00:11:24.000 + Hassan on Emacs Research Group. + +00:11:24.000 --> 00:11:26.000 + We did demonstrate what CRDT was. + +00:11:26.000 --> 00:11:28.890 + So, we have a very good tool for working on a buffer, and + +00:11:28.890 --> 00:11:31.000 + we have a very good way to take notes. + +00:11:31.000 --> 00:11:34.220 + Why not try to combine the two tools, like Emacs is so good + +00:11:34.220 --> 00:11:36.660 + at doing? We take one mode, we take another mode, we clash + +00:11:36.660 --> 00:11:38.580 + them together and we do something very interesting with + +00:11:38.580 --> 00:11:39.000 + them. + +00:11:39.000 --> 00:11:42.430 + Well, we should probably be doing something similar with + +00:11:42.430 --> 00:11:46.140 + note-taking, so that people can actually start building + +00:11:46.140 --> 00:11:47.000 + notes together. + +00:11:47.000 --> 00:11:51.190 + I think that would be a really key step in the future. But + +00:11:51.190 --> 00:11:54.330 + anyway, I think I'm repeating myself a little bit, and I + +00:11:54.330 --> 00:11:57.000 + don't want to say too much right now. + +00:11:57.000 --> 00:11:59.210 + You'll see it in the future, it's coming month or coming + +00:11:59.210 --> 00:12:01.000 + year, so you're not in a rush and flus. + +00:12:01.000 --> 00:12:03.000 + Okay, Vityan, it's back to you now. + +00:12:03.000 --> 00:12:05.350 + Okay, so how do you find a way to get a nice overview of + +00:12:05.350 --> 00:12:07.000 + multiple notes to rearrange them? + +00:12:07.000 --> 00:12:09.790 + Like, basically putting many small notes on another table + +00:12:09.790 --> 00:12:11.000 + and rearranging them. + +00:12:11.000 --> 00:12:16.930 + So, my initial idea when I tried to make Zettle Desk was to + +00:12:16.930 --> 00:12:20.000 + get as close as possible to this. + +00:12:20.000 --> 00:12:22.800 + Have a lot of small notes in my table and be able to + +00:12:22.800 --> 00:12:24.000 + rearrange them. + +00:12:24.000 --> 00:12:29.000 + Due to Org Mode being text, this is not exactly possible. + +00:12:29.000 --> 00:12:33.190 + But I don't know if this question was before the third demo + +00:12:33.190 --> 00:12:34.000 + or not. + +00:12:34.000 --> 00:12:39.870 + What I showed in that demo, I think, to an extent, showed + +00:12:39.870 --> 00:12:42.000 + what I do for rearranging. + +00:12:42.000 --> 00:12:47.720 + You add all the things you want on the Zelda scratch buffer + +00:12:47.720 --> 00:12:50.000 +, and then rearrange them however you want. + +00:12:50.000 --> 00:12:56.000 + So, that's as close as I have been able to get to that. + +00:12:56.000 --> 00:13:05.230 + It's not perfect, but I think it is alright for being text, + +00:13:05.230 --> 00:13:11.000 + which making it graphically would be hard, I think. + +00:13:11.000 --> 00:13:17.000 + And the next one seems to be a follow-up on that question. + +00:13:17.000 --> 00:13:20.260 + Yeah, it says it's difficult or impossible to do that. Yeah + +00:13:20.260 --> 00:13:21.000 +, I agree. + +00:13:21.000 --> 00:13:27.000 + Okay. + +00:13:27.000 --> 00:13:33.560 + So, this package that you say on the next one, on the next + +00:13:33.560 --> 00:13:39.000 + question, I will check this link out. + +00:13:39.000 --> 00:13:44.840 + It seems very interesting for writing your notes on a big + +00:13:44.840 --> 00:13:46.000 + canvas. + +00:13:46.000 --> 00:13:50.230 + I think it would definitely make sense for my workflow to + +00:13:50.230 --> 00:13:53.260 + use something like this, if it is what I have understood + +00:13:53.260 --> 00:13:54.000 + you mean it is. + +00:13:54.000 --> 00:13:59.000 + I would love to try it. And we'll get back to you. + +00:13:59.000 --> 00:14:03.750 + Whoever left that message, if you want to leave any contact + +00:14:03.750 --> 00:14:08.000 + information or talk to me, I would love to get back to you + +00:14:08.000 --> 00:14:09.000 + about this. + +00:14:09.000 --> 00:14:11.000 + Because it looks very interesting. + +00:14:11.000 --> 00:14:14.810 + Yes, so again, all the contact information will be + +00:14:14.810 --> 00:14:17.000 + available on the talk page. + +00:14:17.000 --> 00:14:18.630 + By the way, if you're worried about the lighting changes in + +00:14:18.630 --> 00:14:21.370 + my place, it's just that sometimes I have a lot of light in + +00:14:21.370 --> 00:14:22.000 + my face. + +00:14:22.000 --> 00:14:25.000 + And then, when I'm a little tired, I do rest like this. + +00:14:25.000 --> 00:14:28.000 + And it's very different, but it's still me. Don't worry + +00:14:28.000 --> 00:14:28.000 + about it. + +00:14:28.000 --> 00:14:30.460 + I'm not going to turn it off, because every time it's like + +00:14:30.460 --> 00:14:32.000 + a flashbang going into my eyes. + +00:14:32.000 --> 00:14:35.240 + So, if you want to talk to Vidyanos afterwards, maybe do + +00:14:35.240 --> 00:14:38.000 + not leave your coordinates right into the pad. + +00:14:38.000 --> 00:14:41.000 + Maybe get in touch with Vidyanos instead. + +00:14:41.000 --> 00:14:43.380 + Those ads are going to be public eventually, and even + +00:14:43.380 --> 00:14:46.000 + though we will be reviewing all the content within them, + +00:14:46.000 --> 00:14:49.000 + it means that they will be open to people for a while. + +00:14:49.000 --> 00:14:52.000 + So, maybe avoid putting personal information over there. + +00:14:52.000 --> 00:14:54.440 + But otherwise, you'll be able to connect after the + +00:14:54.440 --> 00:14:57.590 + conference relatively easily, and Vidyanos will be able to + +00:14:57.590 --> 00:14:58.000 + follow up. + +00:14:58.000 --> 00:15:01.000 + Or even just on the questions, whenever you have the time. + +00:15:01.000 --> 00:15:03.760 + But it might take one or two weeks for the speakers to get + +00:15:03.760 --> 00:15:06.000 + back to the questions you put into the pad. + +00:15:06.000 --> 00:15:09.000 + We will be asking them frequently. + +00:15:09.000 --> 00:15:11.890 + We do have this policy, as you know, with Emacs, of nudging + +00:15:11.890 --> 00:15:13.000 + speakers to do something. + +00:15:13.000 --> 00:15:15.860 + So, we will nudge speakers towards answering your questions + +00:15:15.860 --> 00:15:18.510 +, but it might take us about one or two weeks to get all the + +00:15:18.510 --> 00:15:19.000 + answers. + +00:15:19.000 --> 00:15:22.000 + I think we don't have any more questions currently. + +00:15:22.000 --> 00:15:24.000 + There is one more. + +00:15:24.000 --> 00:15:26.000 + Oh, there is one more. So, please take it. + +00:15:26.000 --> 00:15:29.800 + Can we use Zettelkasten for coding too, especially when + +00:15:29.800 --> 00:15:32.000 + using the IDs like Visual Studio and Excel? + +00:15:32.000 --> 00:15:38.080 + So, I can't say for sure if you can use it, because I'm not + +00:15:38.080 --> 00:15:39.000 + in coding. + +00:15:39.000 --> 00:15:44.000 + The only language I know the best for coding is Emacs Lisp. + +00:15:44.000 --> 00:15:48.770 + And the only other one I know is Matlab for doing + +00:15:48.770 --> 00:15:54.000 + calculations, for example, for things in university. + +00:15:54.000 --> 00:15:59.000 + But I think you should be able to do that. + +00:15:59.000 --> 00:16:03.600 + If you look for Zettelkasten for coding, you will probably + +00:16:03.600 --> 00:16:06.000 + find some resources for it. + +00:16:06.000 --> 00:16:14.000 + I don't think it breaks the Zettelkasten principles. + +00:16:14.000 --> 00:16:21.000 + You can make atomic nodes for coding concepts. + +00:16:21.000 --> 00:16:24.000 + So, it should work, I believe. + +00:16:24.000 --> 00:16:26.000 + Yeah, and I can actually confirm this. + +00:16:26.000 --> 00:16:31.150 + I did share with you before in one of the previous Q&A how + +00:16:31.150 --> 00:16:33.390 + we're taking notes on this little device right here to do + +00:16:33.390 --> 00:16:34.000 + lead code exercises. + +00:16:34.000 --> 00:16:38.400 + The thing about lead code exercises is that, well, lead + +00:16:38.400 --> 00:16:40.000 + code, sorry, let's be more vague about it. + +00:16:40.000 --> 00:16:42.990 + Lead code is a platform and not a free platform as well, + +00:16:42.990 --> 00:16:44.000 + and I'm not advertising them. + +00:16:44.000 --> 00:16:46.700 + But the concept of data structure and algorithm is really + +00:16:46.700 --> 00:16:48.000 + important to programming. + +00:16:48.000 --> 00:16:53.260 + And usually when you try to solve algorithmic problems, you + +00:16:53.260 --> 00:16:58.000 + rely on a number of patterns that have been developed by... + +00:16:58.000 --> 00:17:01.260 + Sorry, I get people telling me to my right here that, oh, + +00:17:01.260 --> 00:17:02.000 + the sim is going down. + +00:17:02.000 --> 00:17:06.850 + And so my stomach is falling into my body, just, oh, what + +00:17:06.850 --> 00:17:08.000 + happened? + +00:17:08.000 --> 00:17:10.310 + Anyway, going back to the point, we do rely on patterns and + +00:17:10.310 --> 00:17:13.000 + identification of patterns within a problem. + +00:17:13.000 --> 00:17:17.130 + So, as a result, it would be very much possible to create + +00:17:17.130 --> 00:17:20.000 + separate nodes for all these patterns. + +00:17:20.000 --> 00:17:22.630 + And you can have different exercises and say you have an + +00:17:22.630 --> 00:17:25.000 + exercise that is using two different things. + +00:17:25.000 --> 00:17:29.000 + It's using a tree pattern and it's using a depth search. + +00:17:29.000 --> 00:17:31.640 + If neither of those two words make any sense to you, do not + +00:17:31.640 --> 00:17:35.100 + worry and be grateful because this will haunt you at night + +00:17:35.100 --> 00:17:36.000 + otherwise. + +00:17:36.000 --> 00:17:38.730 + But it would be very, I think it would be a prime candidate + +00:17:38.730 --> 00:17:42.000 + really for atomization and linking within a Zettelkasten. + +00:17:42.000 --> 00:17:44.780 + Because it would make it so much easier to structure your + +00:17:44.780 --> 00:17:47.730 + knowledge in a way that is organic rather than hierarchical + +00:17:47.730 --> 00:17:48.000 +. + +00:17:48.000 --> 00:17:52.030 + So, yeah, this was a very good question and I'd be happy to + +00:17:52.030 --> 00:17:56.390 + encourage the asker to try it on their own and maybe make a + +00:17:56.390 --> 00:17:58.000 + presentation next year at the next EMACS Conf. + +00:17:58.000 --> 00:18:01.210 + Vidyanos, before we continue, I just want to give up the + +00:18:01.210 --> 00:18:02.000 + heads up. + +00:18:02.000 --> 00:18:05.230 + So, we have opened the room currently. If you want to join + +00:18:05.230 --> 00:18:10.000 + the room with Vidyanos, we have posted the link on ISC. + +00:18:10.000 --> 00:18:12.400 + And if you go to the talk page of Vidyanos talk, you will + +00:18:12.400 --> 00:18:14.000 + be able to join the room as well. + +00:18:14.000 --> 00:18:16.650 + We did have quite a number of questions. So, feel free to + +00:18:16.650 --> 00:18:17.000 + join. + +00:18:17.000 --> 00:18:19.530 + In about four minutes, we'll need to move on to the next + +00:18:19.530 --> 00:18:20.000 + talk. + +00:18:20.000 --> 00:18:23.000 + But, well, actually, I give you about three more minutes. + +00:18:23.000 --> 00:18:26.000 + Do we have any more questions on the pad, Vidyanos? + +00:18:26.000 --> 00:18:29.000 + On the pad, no. I'm looking on IRC. + +00:18:29.000 --> 00:18:34.000 + Someone says if Zeldas.dl will be available in Melpa. + +00:18:34.000 --> 00:18:39.000 + It is on Melpa right now. You can find it. + +00:18:39.000 --> 00:18:44.390 + Right. And you just have to -- sorry, my voice is getting + +00:18:44.390 --> 00:18:45.000 + raspier. + +00:18:45.000 --> 00:18:47.680 + It's only the first day of EMACS Conf. It's not even lunch + +00:18:47.680 --> 00:18:49.000 + and I'm already losing my voice. + +00:18:49.000 --> 00:18:51.000 + This is not booting well for the rest. + +00:18:51.000 --> 00:18:54.100 + But, yeah, you should be able to find it pretty easily by + +00:18:54.100 --> 00:19:00.080 + looking on doc.go for Melpa and space and zeldacaster.el, + +00:19:00.080 --> 00:19:01.000 + the name of the package. + +00:19:01.000 --> 00:19:03.000 + You'll be able to find it. And we can put it on the page. + +00:19:03.000 --> 00:19:04.600 + I'm pretty sure it's already on your talk page, Vidyanos, + +00:19:04.600 --> 00:19:05.000 + as well. + +00:19:05.000 --> 00:19:07.000 + Yeah, it is on the talk page. + +00:19:07.000 --> 00:19:09.000 + Yeah, you'll be able to find it really quickly. + +00:19:09.000 --> 00:19:11.000 + So we have about two more minutes. + +00:19:11.000 --> 00:19:12.670 + Did you see any other question that you'd like to answer as + +00:19:12.670 --> 00:19:13.000 + well? + +00:19:13.000 --> 00:19:17.800 + I'm scrolling on IRC since the talk started to see if there + +00:19:17.800 --> 00:19:19.000 + is anything else. + +00:19:19.000 --> 00:19:21.000 + I don't see anything else. + +00:19:21.000 --> 00:19:28.000 + If anyone has a room here, I would love to continue. + +00:19:28.000 --> 00:19:33.000 + If not, then I think we've already answered enough things. + +00:19:33.000 --> 00:19:38.000 + Sure, I would concur. You have covered a lot of ground. + +00:19:38.000 --> 00:19:41.240 + I am personally happy to be seeing so many talks about Zeld + +00:19:41.240 --> 00:19:42.000 +acaster. + +00:19:42.000 --> 00:19:44.430 + It feels like I was a little bit of a forerunner at EMACS + +00:19:44.430 --> 00:19:46.000 + Conf talking about Zeldacaster. + +00:19:46.000 --> 00:19:48.450 + And now, we are two years later and we're still talking + +00:19:48.450 --> 00:19:49.000 + about it. + +00:19:49.000 --> 00:19:51.170 + I know a lot of people are getting a little tired of + +00:19:51.170 --> 00:19:53.000 + hearing about Zeldacaster all the time. + +00:19:53.000 --> 00:19:59.050 + But if you part all the communication, if you focus on what + +00:19:59.050 --> 00:20:00.000 + it actually does, + +00:20:00.000 --> 00:20:03.000 + and I keep saying it's just notes and it's just links, + +00:20:03.000 --> 00:20:05.000 + it's actually quite amazing what you can do with it. + +00:20:05.000 --> 00:20:07.000 + It's just a mental model, really. + +00:20:07.000 --> 00:20:11.690 + So I would kind of use the, you know, sorry for the voxing + +00:20:11.690 --> 00:20:12.000 + here. + +00:20:12.000 --> 00:20:16.460 + But if you have been interested in Zeldacaster at some + +00:20:16.460 --> 00:20:17.000 + point, + +00:20:17.000 --> 00:20:20.000 + or if you are frustrated by all the talk about Zeldacaster, + +00:20:20.000 --> 00:20:22.000 + that seems to be kind of like a cult at some point, + +00:20:22.000 --> 00:20:27.460 + well, I would encourage you maybe to try, not necessarily + +00:20:27.460 --> 00:20:28.000 + try it for yourself, + +00:20:28.000 --> 00:20:31.000 + but try to understand really the simple stuff behind it. + +00:20:31.000 --> 00:20:34.340 + Because honestly, there's nothing very revolutionary about + +00:20:34.340 --> 00:20:36.000 + this note-taking method. + +00:20:36.000 --> 00:20:39.370 + It's just that it used to be done with paper, and now it's + +00:20:39.370 --> 00:20:40.000 + done with computers, + +00:20:40.000 --> 00:20:42.000 + and it makes it a little more easier. + +00:20:42.000 --> 00:20:45.500 + Personally, what I find the most helpful in this type of + +00:20:45.500 --> 00:20:48.000 + note-taking is how organic everything feels. + +00:20:48.000 --> 00:20:50.650 + You do not need to be thinking about the structure from the + +00:20:50.650 --> 00:20:51.000 + get-go, + +00:20:51.000 --> 00:20:53.000 + and this is extremely freeing. + +00:20:53.000 --> 00:20:56.000 + OK, Vidyanos, we are about out of time. + +00:20:56.000 --> 00:20:58.240 + Thank you so much for taking the time to answer the + +00:20:58.240 --> 00:20:59.000 + questions. + +00:20:59.000 --> 00:21:01.690 + We will be in touch in the future, and we'll be looking + +00:21:01.690 --> 00:21:04.000 + forward to having more presentations about Zeldacaster, + +00:21:04.000 --> 00:21:08.000 + and perhaps maybe one by you in the future. + +00:21:08.000 --> 00:21:11.000 + So, well, thank you so much. + +00:21:11.000 --> 00:21:13.470 + And, Vidyanos, I don't see anyone in the room, so feel free + +00:21:13.470 --> 00:21:15.000 + to leave the room after we're done. + +00:21:15.000 --> 00:21:18.410 + So in about one minute, we're going to go with the next + +00:21:18.410 --> 00:21:19.000 + talk. + +00:21:19.000 --> 00:21:23.000 + We might go a little bit quiet until the top of the minute. + +00:21:23.000 --> 00:21:26.000 + I need to drink, and I need to rest my voice. + +00:21:26.000 --> 00:21:28.000 + But in one minute, we'll be starting the next talk. + +00:21:28.000 --> 00:21:30.000 + Vidyanos, thank you so much, and see you next time. + +00:21:30.000 --> 00:21:32.000 + Bye. + +00:21:32.000 --> 00:21:35.000 + (Break) + +00:21:37.000 --> 00:21:37.000 + + +00:21:37.000 --> 00:21:40.000 + (Break) + +00:21:42.000 --> 00:21:42.000 + + +00:21:42.000 --> 00:21:45.000 + (Break) + +00:21:47.000 --> 00:21:47.000 + + +00:21:47.000 --> 00:21:50.000 + (Break) + +00:21:50.000 --> 00:21:53.000 + (Break) + +00:21:55.000 --> 00:21:55.000 + + +00:21:55.000 --> 00:21:58.000 + (Break) + +00:22:00.000 --> 00:22:00.000 + + +00:22:00.000 --> 00:22:03.000 + (Break) + |