Expression-Oriented ClojureScript code

In this example, whenever a contact is changed, we replace the map modeling that contact entirely. When it comes time to render to the virtual DOM, the ContactList is going to re-render, because the contacts list is now a new object entirely.

Consider this: we are writing a contact management app, and we have a ContactList component that contains ContactListItem components. These components are all backed by a list of contacts and should re-render whenever a contact changes.

single-line macros being redefined

Single-line macros are defined using the %define preprocessor directive

The preprocessor collapses all lines which end with a backslash (\) character into a single line.

What we need, in order to live well, is a proper appreciation of the way in which such goods as friendship, pleasure, virtue, honor and wealth fit together as a whole. In order to apply that general understanding to particular cases, we must acquire, through proper upbringing and habits, the ability to see, on each occasion, which course of action is best supported by reasons. Therefore practical wisdom, as he conceives it, cannot be acquired solely by learning general rules.

Org-roam’s Design Principle

Appendix D Variable Index

Appendix C Function Index

mathpix.el uses Mathpix’s API to convert clips into latex equations:

org-roam-dailies-goto-next-note

org-roam-dailies-goto-previous-note

org-roam-dailies-find-directory

org-roam-dailies-goto-date

org-roam-dailies-capture-date

org-roam-dailies-goto-yesterday

org-roam-dailies-capture-yesterday

org-roam-dailies-goto-today

org-roam-dailies-capture-today

org-roam-dailies provides these interactive functions:

org-roam-dailies-directory

org-roam-dailies-capture-templates

For org-roam-dailies to work, you need to define two variables: Variable: org-roam-dailies-directory Path to daily-notes. This path is relative to org-roam-directory. Variable: org-roam-dailies-capture-templates Capture templates for daily-notes in Org-roam.

Org-roam provides journaling capabilities akin to Org-journal with org-roam-dailies.

Org-roam provides basic graphing capabilities to explore interconnections between notes, in org-roam-graph. This is done by performing SQL queries and generating images using Graphviz. The graph can also be navigated: see Roam Protocol.

8.2 Titles and Aliases

9 Citations

13 The Templating System

13.2 Org-roam Template Expansion

If foo is a function, foo is called with the current node as its argument. Else if org-roam-node-foo is a function, foo is called with the current node as its argument. The org-roam-node- prefix defines many of Org-roam’s node accessors such as org-roam-node-title and org-roam-node-level. Else look up org-roam-capture--info for foo. This is an internal variable that is set before the capture process begins. If none of the above applies, read a string using completing-read. Org-roam also provides the ${foo=default_val} syntax, where if a default value is provided, will be the initial value for the foo key during minibuffer completion.

Org-roam provides the ${foo} syntax for substituting variables with known strings. ${foo}’s substitution is performed as follows:

Org-roam’s templates are specified by org-roam-capture-templates

Org-roam capture templates are incompatible with org-capture templates.

To use this, create the following bookmarklet in your browser:

This protocol finds or creates a new note with a given ROAM_REFS:

Org-roam provides extensions for capturing content from external applications such as the browser, via org-protocol.

To enable Org-roam’s protocol extensions, simply add the following to your init file:

To test that you have the handler setup and registered properly from the command line you can run:

To create encrypted files, simply add the .gpg extension in your Org-roam capture templates. For example:

Emacs has support for creating and editing encrypted gpg files, and Org-roam need not provide additional tooling.

Completions for Org-roam are provided via completion-at-point. Org-roam currently provides completions in two scenarios: When within an Org bracket link Anywhere

Extension developers may be interested in retrieving the citations within their notes. This information can be found within the citation table of the Org-roam database.

It is common to use take reference notes for academic papers. To designate the node to be the canonical node for the academic paper, we can use its unique citation key:

Org-roam attempts to load both the org-ref and org-cite package when indexing files, so no further setup from the user is required for citation support.

You may assign multiple refs to a single node, for example when you want multiple papers in a series to share the same note, or an article has a citation key and a URL at the same time.

org-roam-alias-remove

For users that prefer using a side-window for the org-roam buffer, the following example configuration should provide a good starting point:

To assign an alias to a node, add the “ROAM_ALIASES” property to the node:

Nodes can also have multiple aliases. Aliases allow searching for nodes via an alternative name.

Org-roam caches most of the standard Org properties. The full list now includes: outline level todo state priority scheduled deadline tags

org-roam-buffer-display-dedicated: Launch an Org-roam buffer for a specific node without visiting its file. Unlike org-roam-buffer-toggle you can have multiple such buffers and their content won’t be automatically replaced with a new node at point.

org-roam-buffer-toggle: Launch an Org-roam buffer that tracks the node currently at point. This means that the content of the buffer changes as the point is moved, if necessary.

org-roam-buffer-display-dedicated

org-roam-buffer-toggle