![]() From there, you’ll find some tools in “Stamps → Zettel”. You may open a project agent and enter Map View. Otherwise, you can Update Agents Automatically (I would not recommend it, though, especially if you have a large number of notes). Press ^⌘= a couple of times (or more) to make sure the Notes are appropriately set. ![]() Edit its Name and Query parameter to something meaningful. Open Properties Inspector for “Test Project”. Set WatchFolder to the path containing your Zettelkasten notes. Open Properties Inspector ( ⌘2) for “Notes”. Prototypes and attributes are set with a multi-step orchestration of agents. ![]() This way, the lines will be ignored if you use a capable Markdown processor, such as pandoc. It is advisable to include the metadata inside a YAML header section. The Agents will automatically try to set the Annotation Zettel Prototype for this kind of note, as well as its attributes. The loc attribute points to the location in the work/reference (most usually page numbers). Notes of this kind should contain a citekey information for the corresponding (BibTeX or similar) reference. There’s also a sub-type for bibliographical (secondary source) annotation. This implementation will extract tags from the notes, when a text line beginning with “tags:”, followed by hashtags, is found. You must use filenames starting with a sequence of digits (at least three), which is assumed to be a fixed identification of a note. Zettelkasten.tbx (120.4 KB) External notes and their file names You’ll find a description of the requirements and a usage guide below. For ad locum comments on the primary sources (in my case, those are mainly ancient philosophy texts), I use a separate system (and a different TBX file). In this system, the main kinds of notes I keep are thoughts on the subjects I’m working, and annotation of secondary sources (bibliographical review). I don’t think it is an adequate substitute for a more specific application. I think it should be easier to see the workings in a functional TBX file instead of trying to explain the details of its mechanism.Īs I see it, Tinderbox is an amazing tool for analysing this kind of notes, especially the Map View. If you’ve developed a filter and want to use it within a document you need to add it to the list of filters for the document.I’ve created a simplified version of the TBX file I use for analysing my “Zettelkasten”-type of notes (which I keep in The Archive), as I tried to show in today’s meet up. Access to the Pandoc and Quarto libraries of Lua helper functions.High performance (no serialization or process execution overhead).We strongly recommend using Lua Filters, which have the following advantages: You can write Pandoc filters using Lua (via Pandoc’s built-in Lua interpreter) or using any other language using a JSON representation of the Pandoc AST piped to/from an external process. Pandoc’s built-in citation processing is implemented as a filter, as are many of Quarto’s internal extensions (e.g. cross-references, figure layout, etc.). INPUT -reader-> AST -filter-> AST -writer-> OUTPUT ![]() The pandoc AST format is defined in the module in the pandoc-types package.Ī “filter” is a program that modifies the AST, between the reader and the writer. When converting a document from one format to another, text is parsed by a reader into pandoc’s intermediate representation of the document-an “abstract syntax tree” or AST-which is then converted by the writer into the target format. Pandoc consists of a set of readers and writers. If the base features of Pandoc and Quarto don’t do exactly what you need, you can very likely create a Pandoc Filter that bridges the gap.
0 Comments
Leave a Reply. |