WEBVTT captioned by sachac NOTE Introduction 00:00:01.400 --> 00:00:03.938 Hello there, fellow basement dwellers. 00:00:03.939 --> 00:00:05.958 I'm Christian and you are watching " 00:00:05.959 --> 00:00:08.519 Zettelkasten for Regular Emacs Hackers," 00:00:08.520 --> 00:00:12.920 my Emacs Conference 2025 talk submission. 00:00:12.921 --> 00:00:14.000 In this presentation, 00:00:14.001 --> 00:00:15.700 I'll be showing you a couple of things 00:00:15.701 --> 00:00:18.701 about Zettelkasten, very basic mechanics and habits 00:00:18.702 --> 00:00:21.622 that you can pick up and implement in Emacs, 00:00:21.623 --> 00:00:24.442 the most malleable of all environments, 00:00:24.443 --> 00:00:27.823 to make a thinking environment happen in your life 00:00:27.824 --> 00:00:32.434 that stays with you potentially forever. 00:00:32.435 --> 00:00:36.055 The subtitle "For Regular Emacs Hackers" implies at least 00:00:36.056 --> 00:00:38.356 the possibility of irregular Emacs hackers 00:00:38.357 --> 00:00:42.498 and regular Emacs non-hackers, so the target audience here 00:00:42.499 --> 00:00:45.119 is people who are comfortable tweaking their setup 00:00:45.120 --> 00:00:47.980 when they run into issues and use Emacs to write, 00:00:47.981 --> 00:00:49.980 no matter if it's prose or code. 00:00:49.981 --> 00:00:53.631 So that's regular Emacs hacking. 00:00:53.632 --> 00:00:55.614 You don't need to be an irregular Emacs hacker, 00:00:55.615 --> 00:00:58.759 for example, being a core maintainer or whatever. 00:00:58.760 --> 00:01:01.243 You just need to be a normal user 00:01:01.244 --> 00:01:06.679 who also modifies the setup. 00:01:06.680 --> 00:01:10.301 However, you should probably not be an Emacs non-hacker. 00:01:10.302 --> 00:01:12.781 Or maybe you shouldn't stay an Emacs non-hacker, 00:01:12.782 --> 00:01:16.002 someone who is not tweaking their setup ever. 00:01:16.003 --> 00:01:18.820 So, if you just open your application 00:01:18.821 --> 00:01:20.240 to write with a double click, 00:01:20.241 --> 00:01:23.283 and it happens to be Emacs, this may not be for you, 00:01:23.284 --> 00:01:25.533 but you ultimately be the judge there. NOTE Advocating Freedoms 00:01:25.534 --> 00:01:28.744 It is my sacred duty to, of course, 00:01:28.745 --> 00:01:32.665 advocate all the essential freedoms during this presentation. 00:01:32.666 --> 00:01:34.507 These are the following. 00:01:34.508 --> 00:01:37.389 You shall not be shackled by a proprietary tool. 00:01:37.390 --> 00:01:40.791 (You shall be shackled by Emacs. (Which is free software.)) 00:01:40.792 --> 00:01:44.114 You shall also not be shackled by an esoteric method 00:01:44.115 --> 00:01:45.275 that turns out to be a grift 00:01:45.276 --> 00:01:47.897 where you need to visit annual workshops, walk on broken glass 00:01:47.898 --> 00:01:50.399 and stuff to be a true ""knower"". 00:01:50.400 --> 00:01:52.880 You shall be empowered to do great things 00:01:52.881 --> 00:01:55.883 for the rest of your life after this session alone. 00:01:55.884 --> 00:01:58.870 This is not a sales pitch. 00:01:58.871 --> 00:02:00.651 Finally, you should also not be shackled 00:02:00.652 --> 00:02:05.039 by whichever sources of information you rely on in the future. 00:02:05.040 --> 00:02:07.853 You shall be free to think and explore new ideas, 00:02:07.854 --> 00:02:12.175 ideally forever, in an environment you built to your liking, 00:02:12.176 --> 00:02:15.796 without the degrading web searches and the dead internet 00:02:15.797 --> 00:02:18.857 getting in your way. No libraries, no dead trees. 00:02:18.858 --> 00:02:21.538 It's you and your knowledge base 00:02:21.539 --> 00:02:29.679 that can truly produce magnificent things. NOTE What Is This About? 00:02:29.680 --> 00:02:33.586 So what is this about? In the teaser text for this session, 00:02:33.587 --> 00:02:36.148 I brought up that when people talk about Emacs 00:02:36.149 --> 00:02:38.931 pulling in everything that people do on their computer, 00:02:38.932 --> 00:02:42.614 it's usually things they used other software for in the past. 00:02:42.615 --> 00:02:46.057 Like email, chat, playing music, browsing the web, 00:02:46.058 --> 00:02:48.819 managing tasks, you know, stuff like that. 00:02:48.820 --> 00:02:51.761 We don't have a good blueprint for thinking environments though. 00:02:51.762 --> 00:02:53.263 So it's not a trivial task, 00:02:53.264 --> 00:02:54.744 just port this or that to Emacs 00:02:54.745 --> 00:02:56.705 and then you'll be happy and productive. 00:02:56.706 --> 00:02:58.199 That's different from doing your emails 00:02:58.200 --> 00:03:00.328 or task management or writing in Emacs, 00:03:00.329 --> 00:03:02.950 where we have a lot of experience with existing software 00:03:02.951 --> 00:03:06.413 to adapt and deviate from, where we can essentially 00:03:06.414 --> 00:03:09.855 port the task to Emacs. We can practice to think, 00:03:09.856 --> 00:03:12.998 purposefully and productively, on complex things 00:03:12.999 --> 00:03:14.459 over long periods of time 00:03:14.460 --> 00:03:19.059 when we create bespoke environments that help with that. 00:03:19.060 --> 00:03:20.467 The first assumption is this: 00:03:20.468 --> 00:03:24.058 Writing is very important to form complex thought. 00:03:24.059 --> 00:03:26.279 Without writing, you won't be able to cross 00:03:26.280 --> 00:03:28.760 a certain complexity threshold. 00:03:28.761 --> 00:03:31.921 Thinking in your head alone without any externalization 00:03:31.922 --> 00:03:34.261 makes you prone to loops, repetitions, 00:03:34.262 --> 00:03:36.142 and worst of all: jumps. 00:03:36.143 --> 00:03:38.562 Jumps that get you to a point, 00:03:38.563 --> 00:03:40.723 but not backed by reason or argument. 00:03:40.724 --> 00:03:46.501 So you and your future and others cannot follow. 00:03:46.502 --> 00:03:48.362 Written words direct thought. 00:03:48.363 --> 00:03:51.984 The linearization or sequence-making of thoughts 00:03:51.985 --> 00:03:55.306 frames your next idea. That's the same for reading, 00:03:55.307 --> 00:03:57.307 which enables you to pick up existing ideas 00:03:57.308 --> 00:04:00.249 and continue to write about them later. 00:04:00.250 --> 00:04:02.810 So for "good thinking", writing, reading, 00:04:02.811 --> 00:04:05.072 and writing is mandatory. 00:04:05.073 --> 00:04:07.193 Emacs is good at showing text to read. 00:04:07.194 --> 00:04:09.634 It's good at processing keyboard inputs to write. 00:04:09.635 --> 00:04:13.176 So let's go. Let's set up an environment within Emacs 00:04:13.177 --> 00:04:16.319 to make this thinking thing happen. 00:04:16.320 --> 00:04:18.059 I'll walk you through some mechanics 00:04:18.060 --> 00:04:20.881 of the Zettelkasten machine and habits for you, 00:04:20.882 --> 00:04:22.900 dear thinker and regular Emacs hacker. 00:04:22.901 --> 00:04:25.885 And for your reference, highlight these things 00:04:25.886 --> 00:04:30.468 as I present them in the bottom left corner of the screen. 00:04:30.469 --> 00:04:33.190 So working with Zettelkasten as a thinking environment 00:04:33.191 --> 00:04:36.533 only requires very simple mechanics. NOTE Write - Essential Mechanic 00:04:36.534 --> 00:04:39.639 First one is to write. I mentioned this. 00:04:39.640 --> 00:04:42.488 It could be one large text file, could be many small ones. 00:04:42.489 --> 00:04:46.359 We use the power of Emacs and small files because Emacs is cool, 00:04:46.360 --> 00:04:49.354 and individual files put boundaries around ideas 00:04:49.355 --> 00:04:52.662 that force you to decide what goes where. 00:04:52.663 --> 00:04:55.686 Most importantly though, write like you mean it. 00:04:55.687 --> 00:04:58.510 The principle of "garbage in and garbage out" holds. 00:04:58.511 --> 00:05:01.374 You don't need to use your novelist voice when taking notes, 00:05:01.375 --> 00:05:04.137 but it also shouldn't be shorthand only, 00:05:04.138 --> 00:05:06.794 so that your future you has an easy time 00:05:06.795 --> 00:05:09.600 reading and digesting what you wrote. NOTE Connect - Essential Mechanic 00:05:09.601 --> 00:05:13.524 Next mechanic, which is also essential, is to connect. 00:05:13.525 --> 00:05:14.999 We think in associations. 00:05:15.000 --> 00:05:18.639 Connect notes to capture the associations that come to mind 00:05:18.640 --> 00:05:20.916 and that you want the reader, which is the future you, 00:05:20.917 --> 00:05:24.074 to make. Traveling a path of connections 00:05:24.075 --> 00:05:25.835 indirectly via tags or keywords 00:05:25.836 --> 00:05:27.096 and directly with links 00:05:27.097 --> 00:05:30.720 can feel like reading an essay you make up as you go. 00:05:30.721 --> 00:05:34.267 That's where connections show their power. NOTE Correct - Essential Habit 00:05:34.268 --> 00:05:38.260 The next essential habit is to read and correct 00:05:38.261 --> 00:05:40.180 and reconnect as you go. 00:05:40.181 --> 00:05:42.311 You spend time and effort at the writing stage, 00:05:42.312 --> 00:05:43.792 you are the primary audience, 00:05:43.793 --> 00:05:46.895 so do your past self a favor and read what you wrote. 00:05:46.896 --> 00:05:50.478 And then as you read it, make it better. 00:05:50.479 --> 00:05:52.340 Make it better, continuously make things better 00:05:52.341 --> 00:05:55.222 and capture new ideas as they come up as you read. 00:05:55.223 --> 00:05:57.784 And things you can only now remember 00:05:57.785 --> 00:06:00.927 because you learned about things in the meantime. 00:06:00.928 --> 00:06:03.429 You'll also get better at this whole thing with practice. 00:06:03.430 --> 00:06:05.866 So improve old notes when you find them lacking in detail, 00:06:05.867 --> 00:06:08.575 their tone pretentious, their mere existence 00:06:08.576 --> 00:06:10.895 an insult to your intelligence. 00:06:10.896 --> 00:06:11.735 Pay [knocks on table] attention [knocks again] 00:06:11.736 --> 00:06:13.639 to pain points in using notes. 00:06:13.640 --> 00:06:16.559 Yes, I knocked on my desk to emphasize. 00:06:16.560 --> 00:06:18.601 And fix things on the fly. 00:06:18.602 --> 00:06:19.802 From this principle follows 00:06:19.803 --> 00:06:22.063 a lot of common practices and tips. 00:06:22.064 --> 00:06:24.125 This principle truly is essential. 00:06:24.126 --> 00:06:25.546 Too long and you didn't read it? 00:06:25.547 --> 00:06:27.227 Add a summary at the beginning. 00:06:27.228 --> 00:06:30.089 You can't understand what you wrote a year ago? 00:06:30.090 --> 00:06:32.511 Do your best to rewrite it in your own words. 00:06:32.512 --> 00:06:35.099 It only gets worse if you wait longer. 00:06:35.100 --> 00:06:37.115 Can't find anything in the mess? 00:06:37.116 --> 00:06:39.137 Collect links to what you could find 00:06:39.138 --> 00:06:41.659 in a new "meta" note so next time, 00:06:41.660 --> 00:06:43.240 you have a navigational help. 00:06:43.241 --> 00:06:44.861 This practice will form the basis 00:06:44.862 --> 00:06:46.733 for structure notes, maps, and overviews, 00:06:46.734 --> 00:06:49.433 which we will come to later. NOTE Design for Use - Habit 00:06:49.434 --> 00:06:52.071 The next habit, non-essential though, 00:06:52.072 --> 00:06:55.332 is to create notes with intent to use them. 00:06:55.333 --> 00:06:58.133 It's one thing to write about facts, capture information, 00:06:58.134 --> 00:07:01.354 but all this is just collecting stuff. 00:07:01.355 --> 00:07:03.615 It's another thing altogether to write about 00:07:03.616 --> 00:07:06.556 a train of thought, about an argument you found compelling, 00:07:06.557 --> 00:07:09.858 about a model to understand the world, or yourself, 00:07:09.859 --> 00:07:12.899 in a better way. So collect to remember, 00:07:12.900 --> 00:07:16.260 but work in your Zettelkasten to think. 00:07:16.261 --> 00:07:18.221 What does that even mean, though? 00:07:18.222 --> 00:07:19.822 Recreate how intriguing books 00:07:19.823 --> 00:07:21.803 lay out their premises and arguments, for example. 00:07:21.804 --> 00:07:24.885 First this, then that, also that supports the premise, 00:07:24.886 --> 00:07:27.407 and so on. That's the structure of an argument. 00:07:27.408 --> 00:07:30.549 You can recreate it in list form, as a graph, 00:07:30.550 --> 00:07:33.500 you can draw and import the image, whatever. 00:07:33.501 --> 00:07:36.112 The structure of that argument is one thing, 00:07:36.113 --> 00:07:38.333 and the details, like the evidence for each claim, 00:07:38.334 --> 00:07:39.999 can be separate things. 00:07:40.000 --> 00:07:43.919 These can become their own sub-networks over time. NOTE Create Structure - Mechanic 00:07:43.920 --> 00:07:45.470 To facilitate all that, 00:07:45.471 --> 00:07:47.931 you will be needing to create structures. 00:07:47.932 --> 00:07:50.612 You've connected notes, so links already leave trails 00:07:50.613 --> 00:07:52.519 to traverse between your notes. 00:07:52.520 --> 00:07:55.929 Structures can emerge from these with a sheer volume, 00:07:55.930 --> 00:07:58.616 but they also can be designed by you to be 00:07:58.617 --> 00:08:02.258 navigational hubs of similar shape and form over time. 00:08:02.259 --> 00:08:04.240 Patterns like that reduce confusion 00:08:04.241 --> 00:08:05.800 and improve feeling at home 00:08:05.801 --> 00:08:09.222 and finding your way around, so that's worth investing in. 00:08:09.223 --> 00:08:13.404 For example, use outlines for complex topics. 00:08:13.405 --> 00:08:15.247 Tables of contents of a book, for example, 00:08:15.248 --> 00:08:17.319 that you love and processed in great detail. 00:08:17.320 --> 00:08:19.492 Just recreate the table of contents, 00:08:19.493 --> 00:08:23.037 the nested structure of it, in your notes, 00:08:23.038 --> 00:08:28.196 and then you have something to hang your future thoughts onto. 00:08:28.197 --> 00:08:31.517 Another example is a pro/contra table or list 00:08:31.518 --> 00:08:35.478 to discuss opposing facets and perspective of a thing. 00:08:35.479 --> 00:08:37.830 Another example would be models or metaphors 00:08:37.831 --> 00:08:39.060 like the iceberg model 00:08:39.061 --> 00:08:42.181 where you point out something has a hidden depth to it 00:08:42.182 --> 00:08:44.381 or the metaphor of a tree to model a thing 00:08:44.382 --> 00:08:47.967 as a branching and growing idea. NOTE Start in the Zettelkasten - Mechanic 00:08:47.968 --> 00:08:50.434 Another habit which is also not essential 00:08:50.435 --> 00:08:52.454 is to start in your Zettelkasten. 00:08:52.455 --> 00:08:55.255 Starting in your Zettelkasten removes the cost of deciding 00:08:55.256 --> 00:08:57.516 what goes in there and what doesn't. 00:08:57.517 --> 00:08:59.636 It gets you moving and up to speed 00:08:59.637 --> 00:09:03.277 with the method and the tool much easier. 00:09:03.278 --> 00:09:05.078 Importing stuff later into the Zettelkasten 00:09:05.079 --> 00:09:06.198 can feel like a chore, 00:09:06.199 --> 00:09:09.259 but starting the work you need to do anyway in it? 00:09:09.260 --> 00:09:11.560 That reduces the mental hurdle. 00:09:11.561 --> 00:09:12.921 As a regular Emacs hacker, 00:09:12.922 --> 00:09:14.582 you'll eventually develop your own tools 00:09:14.583 --> 00:09:17.303 to make initial exploration smoother over time, 00:09:17.304 --> 00:09:19.544 like do you start in a particular place 00:09:19.545 --> 00:09:22.519 or just create a new note from scratch somewhere. 00:09:22.520 --> 00:09:25.026 You won't know this until you experience this stuff 00:09:25.027 --> 00:09:26.867 for a while and try different things. 00:09:26.868 --> 00:09:32.400 So don't worry and be open for change. NOTE Start with a Link - Mechanic 00:09:32.401 --> 00:09:36.369 The final habit, also non-essential, is to start with a link 00:09:36.370 --> 00:09:38.451 and not with the creation of a new file. 00:09:38.452 --> 00:09:40.512 Start with a link, create the file later. 00:09:40.513 --> 00:09:42.473 This avoids orphaned notes. 00:09:42.474 --> 00:09:45.896 Orphaned notes are those no others are linking to. 00:09:45.897 --> 00:09:48.457 To these you can only get with a full-text search 00:09:48.458 --> 00:09:51.299 or maybe by accident when you browse your notes, 00:09:51.300 --> 00:09:54.567 but there is no orderly way to get to them. NOTE Recap 00:09:54.568 --> 00:09:58.533 To recap: Write. Don't be sloppy. 00:09:58.534 --> 00:10:00.600 Put in effort early to get faster at this. 00:10:00.601 --> 00:10:04.159 This is essential, because without putting effort 00:10:04.160 --> 00:10:08.133 into writing, you won't have anything to use. 00:10:08.134 --> 00:10:10.500 Connect and leave trails to navigate. 00:10:10.501 --> 00:10:13.619 That can tell a story when you traverse the trail later. 00:10:13.620 --> 00:10:16.540 This is essential because without connection, 00:10:16.541 --> 00:10:18.600 you will not get anywhere. 00:10:18.601 --> 00:10:20.300 Correct and improve things as you go. 00:10:20.301 --> 00:10:21.839 The last essential thing: well, 00:10:21.840 --> 00:10:24.141 don't worry about perfection, and then, 00:10:24.142 --> 00:10:25.802 be gentle to your past self. 00:10:25.803 --> 00:10:27.976 Adapt to what you learn along the way. 00:10:27.977 --> 00:10:31.124 It's essential, because without this attitude, 00:10:31.125 --> 00:10:33.745 you can easily get stuck in analysis paralysis, 00:10:33.746 --> 00:10:35.039 like where do I need to put this, 00:10:35.040 --> 00:10:37.367 or what would be the perfect way to phrase this. 00:10:37.368 --> 00:10:40.733 Design for use. This helps both finding your voice, 00:10:40.734 --> 00:10:42.819 and to have criteria for selecting 00:10:42.820 --> 00:10:45.233 what to spend time and effort on in the first place. 00:10:45.234 --> 00:10:47.349 It takes into account the opportunity cost 00:10:47.350 --> 00:10:50.250 of high quality work from writing and connecting. 00:10:50.251 --> 00:10:53.333 Create structures. You won't be able to scale 00:10:53.334 --> 00:10:55.876 and stay organized and find your way around 00:10:55.877 --> 00:10:58.539 without structures. You can practice this early 00:10:58.540 --> 00:11:00.599 and design structures deliberately, 00:11:00.600 --> 00:11:03.984 but it's also okay to ignore this for a while and wing it. 00:11:03.985 --> 00:11:05.746 So it's not marked essential, 00:11:05.747 --> 00:11:08.939 although it may hurt you sooner than later. 00:11:08.940 --> 00:11:10.891 The habit to start in the Zettelkasten? 00:11:10.892 --> 00:11:13.793 Well, do the work you need to do in a place 00:11:13.794 --> 00:11:15.479 that can pay back dividends 00:11:15.480 --> 00:11:16.715 on the effort you put in. 00:11:16.716 --> 00:11:19.257 That's powerful, but also not essential. 00:11:19.258 --> 00:11:21.619 You could just as well continue to write and think 00:11:21.620 --> 00:11:23.460 and scribble somewhere else, 00:11:23.461 --> 00:11:27.423 and then do the Zettelkasten importing stuff later. 00:11:27.424 --> 00:11:28.439 Start with a link. 00:11:28.440 --> 00:11:30.245 That's really useful practice, 00:11:30.246 --> 00:11:33.206 but more like a lifehack and not an essential habit. 00:11:33.207 --> 00:11:35.347 So you can also create new files from scratch 00:11:35.348 --> 00:11:38.049 for ideas that come up as they come up 00:11:38.050 --> 00:11:39.610 and then try to connect them later. 00:11:39.611 --> 00:11:42.731 Well, that's better than not writing at all, right? 00:11:42.732 --> 00:11:44.747 So if you look at this, you may ask yourself, 00:11:44.748 --> 00:11:48.319 why is this create structure thing a mechanic and not a habit? 00:11:48.320 --> 00:11:50.876 What's the difference? It seems kind of random. 00:11:50.877 --> 00:11:53.918 Well, do create structures as an imperative 00:11:53.919 --> 00:11:55.279 is a good habit, yes. 00:11:55.280 --> 00:11:57.981 Structures facilitate growth of the Zettelkasten 00:11:57.982 --> 00:11:59.562 and help you discover useful patterns 00:11:59.563 --> 00:12:00.679 and the things you care about. 00:12:00.680 --> 00:12:03.444 Patterns that work for you personally, 00:12:03.445 --> 00:12:04.724 which make navigation easier 00:12:04.725 --> 00:12:07.605 because they fit your personal expectations 00:12:07.606 --> 00:12:10.586 for what is and what is not. 00:12:10.587 --> 00:12:13.847 That's something for you to do. That's a process. 00:12:13.848 --> 00:12:18.148 But from the perspective of the Zettelkasten as a system, 00:12:18.149 --> 00:12:20.609 that's a mechanic or rather dynamic, 00:12:20.610 --> 00:12:23.149 the Zettelkasten grows organically. 00:12:23.150 --> 00:12:25.310 Thanks to your constant intervention and usage of course. 00:12:25.311 --> 00:12:27.631 That's how time passes in your Zettelkasten. 00:12:27.632 --> 00:12:32.272 That's how a process of transformation enters the system. 00:12:32.273 --> 00:12:34.800 The transformation affects the network. 00:12:34.801 --> 00:12:36.255 Every new or updated note, 00:12:36.256 --> 00:12:38.557 every new connection changes the network. 00:12:38.558 --> 00:12:40.718 The existing network then imposes demands 00:12:40.719 --> 00:12:43.679 for new stuff to fit in, slowly solidifying 00:12:43.680 --> 00:12:47.363 how things are organized to be perceived as orderly. 00:12:47.364 --> 00:12:49.084 This is calcifying. 00:12:49.085 --> 00:12:52.326 That's emergent creation of structure from use. 00:12:52.327 --> 00:12:56.268 Structure here is expectation for what could come next. 00:12:56.269 --> 00:12:58.649 On top of this interplay of emergent structure 00:12:58.650 --> 00:13:00.190 in your notes and processes 00:13:00.191 --> 00:13:01.871 that operate these constraints, 00:13:01.872 --> 00:13:04.372 you can design and influence and architect 00:13:04.373 --> 00:13:06.873 and have explicit structures and patterns, 00:13:06.874 --> 00:13:09.633 and therefore you can influence what is expected, 00:13:09.634 --> 00:13:11.836 what is unexpected and what fits 00:13:11.837 --> 00:13:14.257 and what needs to change to fit in. 00:13:14.258 --> 00:13:18.139 So the time you spend designing these things 00:13:18.140 --> 00:13:20.300 will influence how the Zettelkasten 00:13:20.301 --> 00:13:22.033 will behave in the future. NOTE Facilitate Growth 00:13:22.034 --> 00:13:24.061 To prepare for growth 00:13:24.062 --> 00:13:27.533 you will probably encounter thresholds along your journey. 00:13:27.534 --> 00:13:29.267 Like 1-10 notes, well, 00:13:29.268 --> 00:13:31.300 you can easily remember all of them. 00:13:31.301 --> 00:13:34.333 10-100, you will have forgotten some details, 00:13:34.334 --> 00:13:37.067 but will probably remember writing most of these notes 00:13:37.068 --> 00:13:40.239 in some way. 100-1000? 00:13:40.240 --> 00:13:42.919 Bad luck, you will have a hard time going through everything 00:13:42.920 --> 00:13:46.439 one by one to find what you have. You will have to rely on 00:13:46.440 --> 00:13:50.087 filtering results. For example, with a full text search, 00:13:50.088 --> 00:13:53.492 you will crave to use tags and keywords more 00:13:53.493 --> 00:14:02.039 to group notes into more manageable departments or collections. 00:14:02.040 --> 00:14:05.879 By this mark, search results produce way too many results. 00:14:05.880 --> 00:14:07.967 Popular tags become overcrowded, 00:14:07.968 --> 00:14:10.069 and you have the same problem you had in the last stage, 00:14:10.070 --> 00:14:12.519 but for each of these tags. 00:14:12.520 --> 00:14:15.779 So manual structures will take you through this. 00:14:15.780 --> 00:14:18.919 Anticipate growth pains by starting from structures. 00:14:18.920 --> 00:14:22.119 That's the recommendation here. Design your entry points 00:14:22.120 --> 00:14:24.167 into your current projects and research topics 00:14:24.168 --> 00:14:28.159 and interests as 'departments' of your Zettelkasten. 00:14:28.160 --> 00:14:31.161 Keep a list of, for example, 12 darlings, 00:14:31.162 --> 00:14:34.124 like Feynman did: a list of 12 things 00:14:34.125 --> 00:14:35.485 that you can check mechanically 00:14:35.486 --> 00:14:36.926 where you capture something new, 00:14:36.927 --> 00:14:39.889 and then you can see whether the newfound knowledge 00:14:39.890 --> 00:14:46.139 can also push one of your darling projects forward. NOTE Emacs demo 00:14:46.140 --> 00:14:50.222 Now, finally, let's get to the demonstration in Emacs. 00:14:50.223 --> 00:14:52.334 Here is a very minimal init file. 00:14:52.335 --> 00:14:55.738 I will share it with you in the show notes. 00:14:55.739 --> 00:14:59.539 And this is the Denote default configuration. 00:14:59.540 --> 00:15:02.439 Here I'm using the shortcut to create a new note 00:15:02.440 --> 00:15:08.594 immediately for this talk. And there you see. 00:15:08.595 --> 00:15:10.496 That's an empty new note. Here, 00:15:10.497 --> 00:15:16.420 sped up like two or three times the normal typing speed of me, 00:15:16.421 --> 00:15:21.785 is how I would process this very Emacs conference talk. 00:15:21.786 --> 00:15:25.668 The essential mechanics and habits, additional habits, 00:15:25.669 --> 00:15:30.111 mechanics, and then from there after I capture everything. 00:15:30.112 --> 00:15:32.053 Make sure that I have a reference. 00:15:32.054 --> 00:15:36.136 This is not a thought-out implementation in Emacs, 00:15:36.137 --> 00:15:39.039 so this is just plain text. Christian Tietze, 00:15:39.040 --> 00:15:42.146 Zettelkasten for Regular Emacs Hackers at the bottom. 00:15:42.147 --> 00:15:46.585 You can use reference management systems that you like, 00:15:46.586 --> 00:15:49.233 but I don't want to get into these details. 00:15:49.234 --> 00:15:54.367 Here I'm creating a note with the denote shortcut. 00:15:54.368 --> 00:15:56.399 Based on the selected text, 00:15:56.400 --> 00:16:01.099 I'm starting a link. This link is creating the note for me. 00:16:01.100 --> 00:16:04.640 It's also default Denote functionality 00:16:04.641 --> 00:16:05.720 and garbage in garbage out. 00:16:05.721 --> 00:16:08.022 I needed to edit the title because the selected text 00:16:08.023 --> 00:16:10.043 became the note title. Didn't want that. 00:16:10.044 --> 00:16:13.335 That was the abbreviation. 00:16:13.336 --> 00:16:16.220 Notice that the default configuration does not in fact 00:16:16.221 --> 00:16:20.527 include auto-fill-mode, so the lines get infinitely long. 00:16:20.528 --> 00:16:23.653 Looks a bit weird. Just garbage in, garbage out. 00:16:23.654 --> 00:16:27.920 Processing this from Wikipedia. 00:16:27.921 --> 00:16:31.863 So we have a detail note from this overview. 00:16:31.864 --> 00:16:34.265 So that's an overview with one link already. 00:16:34.266 --> 00:16:38.668 Starting from here, now I want to write more about my talk. 00:16:38.669 --> 00:16:43.772 And next we create structure, types of structures, etc. 00:16:43.773 --> 00:16:46.835 It creates a weird link, but I can edit this easily 00:16:46.836 --> 00:16:51.922 thanks to Emacs being so nice to work with. 00:16:51.923 --> 00:16:55.323 A couple of examples. I mentioned some of these 00:16:55.324 --> 00:16:58.604 in previous minutes of this conference talk, 00:16:58.605 --> 00:17:00.584 like position pair, one note for the pair, 00:17:00.585 --> 00:17:03.921 one note per pro and contra, table of contents, 00:17:03.922 --> 00:17:06.405 like lists of things you like, 00:17:06.406 --> 00:17:10.607 to talk about recreating a book's content, 00:17:10.608 --> 00:17:14.308 table of contents so you can process the book in detail, 00:17:14.309 --> 00:17:16.839 argument structures, I believe I mentioned these. 00:17:16.840 --> 00:17:19.370 Look at this up if you're not into arguments, 00:17:19.371 --> 00:17:22.912 but arguments are very well structured, usually. 00:17:22.913 --> 00:17:26.133 A table of things like two-dimensional table or grid. 00:17:26.134 --> 00:17:28.334 Graphics. You can also include graphics, images, 00:17:28.335 --> 00:17:31.636 and then write about these. And then there are metaphors. 00:17:31.637 --> 00:17:33.797 And into one metaphor that I'm presenting here, 00:17:33.798 --> 00:17:37.538 iceberg, black box, and then atom, molecule, and organism, 00:17:37.539 --> 00:17:40.400 I want to get into this. Atom, molecule, organism. 00:17:40.401 --> 00:17:43.923 That's a composition and recursion 00:17:43.924 --> 00:17:47.799 because I have Big Ideas there. Atom, smallest part; 00:17:47.800 --> 00:17:49.567 molecule, comprised of atoms; 00:17:49.568 --> 00:17:51.968 and organism is comprised of molecules. 00:17:51.969 --> 00:17:56.432 Different level of analysis. Because this is irreducible. 00:17:56.433 --> 00:17:59.154 In fact, if you have no clue about reducibility, 00:17:59.155 --> 00:18:02.196 irreducibility -- that doesn't mean much to you? -- 00:18:02.197 --> 00:18:05.978 but look this up. You can go very deep 00:18:05.979 --> 00:18:10.617 with this kind of stuff. It's basically that if you 00:18:10.618 --> 00:18:12.522 decompose organs into atoms, 00:18:12.523 --> 00:18:14.125 you cannot get back to the organs. 00:18:14.126 --> 00:18:17.072 You just have a bunch of atoms. There's information loss, 00:18:17.073 --> 00:18:19.879 more or less. 00:18:19.880 --> 00:18:24.246 Here you see that I create a new thing at the end 00:18:24.247 --> 00:18:26.949 so that I can write about Denote. The tool doesn't matter, 00:18:26.950 --> 00:18:31.834 but when you use Emacs, use Denote because, well, why? 00:18:31.835 --> 00:18:35.457 Let's get into this. Fix the link. 00:18:35.458 --> 00:18:37.279 These are good reasons to use Denote. 00:18:37.280 --> 00:18:44.379 Denote is very simple. Denote has a couple of sane defaults. 00:18:44.380 --> 00:18:47.078 That makes life easier. Backlinks. 00:18:47.079 --> 00:18:51.140 We will see a backlink view at the end. 00:18:51.141 --> 00:18:52.397 I have to create a couple of things. 00:18:52.398 --> 00:18:55.964 I'm copying the source code there, the Elisp source, 00:18:55.965 --> 00:19:01.667 so that you can see, hey, this is just an Org Mode file. 00:19:01.668 --> 00:19:03.629 You can style it to your liking 00:19:03.630 --> 00:19:06.751 and then you can even execute the code if you want. 00:19:06.752 --> 00:19:13.294 Very powerful. Create notes as links first to avoid orphans. 00:19:13.295 --> 00:19:14.675 Forward link again. 00:19:14.676 --> 00:19:16.015 At least I wanted to create a forward link. 00:19:16.016 --> 00:19:17.036 I pressed the wrong shortcut. 00:19:17.037 --> 00:19:19.737 But anyway, I can fix this easily. 00:19:19.738 --> 00:19:23.479 You see, there's no link. Dammit. 00:19:23.480 --> 00:19:26.761 Now I need to create the link after the fact. 00:19:26.762 --> 00:19:33.279 Here's a list of shortcuts. The denote keymap. 00:19:33.280 --> 00:19:35.165 It's a recommended practice by me, 00:19:35.166 --> 00:19:36.766 starting your note with a link. 00:19:36.767 --> 00:19:40.639 You've heard this all just a couple of minutes ago. 00:19:40.640 --> 00:19:42.854 It reduces orphans and supposedly teaches you 00:19:42.855 --> 00:19:45.574 about thinking in connections early. 00:19:45.575 --> 00:19:53.099 It's a good practice to practice. 00:19:53.100 --> 00:19:55.938 So with that note, trying to switch back. 00:19:55.939 --> 00:20:00.119 Denote note switching, that wasn't as smooth, 00:20:00.120 --> 00:20:01.319 but inserting links is. 00:20:01.320 --> 00:20:10.179 And there you go. Here's a backlink view. And that's it. 00:20:10.180 --> 00:20:12.651 In a somewhat self-documenting way, 00:20:12.652 --> 00:20:14.867 here you see a structure note 00:20:14.868 --> 00:20:17.682 which is an overview that represents the gist 00:20:17.683 --> 00:20:19.563 of this Emacs conference talk, 00:20:19.564 --> 00:20:21.839 with a couple of links to details. 00:20:21.840 --> 00:20:24.107 From these details, as you've seen, 00:20:24.108 --> 00:20:27.891 you can go into even more detail. That's all there is to it. 00:20:27.892 --> 00:20:30.133 Repeat this for infinity, 00:20:30.134 --> 00:20:32.875 and you get really really complex networks 00:20:32.876 --> 00:20:35.858 and can do a lot of amazing things in parallel 00:20:35.859 --> 00:20:39.067 without interference. NOTE Learn, Share, Grow 00:20:39.068 --> 00:20:42.439 I just want to stress that the Zettelkasten 00:20:42.440 --> 00:20:47.032 can help you to learn when you publish, when you share, 00:20:47.033 --> 00:20:51.181 and when you grow it and yourself in the process. 00:20:51.182 --> 00:20:54.083 Again, design the Zettelkasten to be used. 00:20:54.084 --> 00:20:58.159 Publish something, write a blog, share stuff with co-workers. 00:20:58.160 --> 00:21:00.485 That's powerful and that's so rewarding. 00:21:00.486 --> 00:21:04.039 This can in turn influence how you do it 00:21:04.040 --> 00:21:06.033 the next time in your Zettelkasten, 00:21:06.034 --> 00:21:09.380 because now you can anticipate these kinds of arguments, 00:21:09.381 --> 00:21:11.979 maybe I can do this early on, 00:21:11.980 --> 00:21:15.133 and then you're prepared even more for the future 00:21:15.134 --> 00:21:17.479 to share what you learn. 00:21:17.480 --> 00:21:20.159 You are also invited very warmly to our 00:21:20.160 --> 00:21:23.319 community of practice in the Zettelkasten forums. 00:21:23.320 --> 00:21:26.155 Just share your journey, write about your projects, 00:21:26.156 --> 00:21:29.793 ask questions. Everyone's welcome, newbie to pro. 00:21:29.794 --> 00:21:32.674 Just get in touch with people, talk about the processes, 00:21:32.675 --> 00:21:35.361 improve them, and eventually you'll figure out, well, 00:21:35.362 --> 00:21:39.979 reaching enlightenment in that regard may not be that hard after all, 00:21:39.980 --> 00:21:42.953 and then you're fine and good to go for the next projects 00:21:42.954 --> 00:21:48.559 that you tackle. Most importantly is to make this thing your own. 00:21:48.560 --> 00:21:50.746 The Zettelkasten, the method, the environment. 00:21:50.747 --> 00:21:53.474 Create a thinking environment for you. 00:21:53.475 --> 00:21:56.877 Create your own tools to think with. 00:21:56.878 --> 00:21:59.378 This goes back to the meme of Shuhari, 00:21:59.379 --> 00:22:02.800 which is basically imitate and then deviate and innovate. 00:22:02.801 --> 00:22:07.123 And this invitation here is to imitate what I just laid out. 00:22:07.124 --> 00:22:10.586 Imitate for a couple of years. One, two, three years. 00:22:10.587 --> 00:22:12.927 The time goes by faster [snaps fingers] than you think. 00:22:12.928 --> 00:22:16.448 And then figure out ways to deviate from the doctrine, 00:22:16.449 --> 00:22:18.909 to figure out ways to improve 00:22:18.910 --> 00:22:22.030 and change the processes to fit you better. 00:22:22.031 --> 00:22:24.451 But you need to try to manifest 00:22:24.452 --> 00:22:26.652 the best practices in your life first, 00:22:26.653 --> 00:22:28.833 for a while, to then figure out, well, 00:22:28.834 --> 00:22:30.853 they are not that best after all 00:22:30.854 --> 00:22:33.054 and I need to change some of them. 00:22:33.055 --> 00:22:37.064 But you wouldn't know if you didn't try. So do try. 00:22:37.065 --> 00:22:38.639 Yeah, and with that I want to thank you. 00:22:38.640 --> 00:22:40.249 Thank you so much for watching. That's it. 00:22:40.250 --> 00:22:41.531 That was the conference talk, 00:22:41.532 --> 00:22:45.296 my short introduction to the Zettelkasten mechanics and habits. NOTE Outro 00:22:45.297 --> 00:22:46.678 I want to thank you so much for watching 00:22:46.679 --> 00:22:48.380 and spending time with me on this topic, 00:22:48.381 --> 00:22:50.143 on these two topics actually, 00:22:50.144 --> 00:22:52.546 that are very near and dear to my heart. 00:22:52.547 --> 00:22:55.399 Do share questions, ask questions in the etherpad. 00:22:55.400 --> 00:22:57.608 And if you watch this after the conference 00:22:57.609 --> 00:23:01.190 and all the live participation is long over, 00:23:01.191 --> 00:23:04.632 step into the forums and ask around there. 00:23:04.633 --> 00:23:09.234 Thanks also to Sacha and team for organizing EmacsConf 2025, 00:23:09.235 --> 00:23:11.595 for having me. Well, I'm looking forward to hearing from 00:23:11.596 --> 00:23:14.256 every one of you. So that's it. 00:23:14.257 --> 00:23:18.360 Peace out and see you in the next one.