Org Ref is an Emacs library that provides rich support for citations, labels and cross-references in Org mode.
The basic idea of Org Ref is that it defines a convenient interface to insert citations from a reference database (e.g., from BibTeX files), and a set of functional Org links for citations, cross-references and labels that export properly to LaTeX, and that provide clickable functionality to the user. Org Ref interfaces with Helm BibTeX to facilitate citation entry, and it can also use RefTeX.
It also provides a fairly large number of utilities for finding bad citations, extracting BibTeX entries from citations in an Org file, and functions to create and modify BibTeX entries from a variety of sources, most notably from a DOI.
Org Ref is especially suitable for Org documents destined for LaTeX export and scientific publication. Org Ref is also useful for research documents and notes.
Org-Babel support for evaluating rust code. Much of this is modeled after `ob-C'. Just like the `ob-C', you can specify :flags headers when compiling with the "rust run" command. Unlike `ob-C', you can also specify :args which can be a list of arguments to pass to the binary. If you quote the value passed into the list, it will use `ob-ref to find the reference data. If you do not include a main function or a package name, `ob-rust will provide it for you and it's the only way to properly use very limited implementation: - currently only support :results output. ; Requirements: - You must have rust and cargo installed and the rust and cargo should be in your `exec-path rust command. - rust-script - `rust-mode is also recommended for syntax highlighting and formatting. Not this particularly needs it, it just assumes you have it.
Package tested on: GNU Emacs 25.2.1 (x86_64-apple-darwin16.5.0) A simple implementation of the yahtzee game. Quick start: add (require yahtzee) in your .emacs M-x yahtzee start a game (in a new buffer) C-c n start a new game (in the same buffer) C-c p add players C-c P reset players SPC throw dice 1,2,3,4,5 hold outcome of 1,2,3,4,5-th dice UP/DOWN select score to register ENTER register selected score w save the game (in json format) The score of a saved game can be loaded using `M-x yahtzee-load-game-score`. Configuration variables: The user might want to set the following variables (see associated docstrings) - `yahtzee-output-file-base - `yahtzee-fields-alist for adding extra fields - `yahtzee-players-names set names of players use (setq-default yahtzee-players-names ...) Note: personally I don't enjoy playing with "Yahtzee bonuses" and "Joker rules" so they are not implemented (even thought they are simple to include). Only the "63 bonus" is available (see `yahtzee-compute-bonus'). Furthermore, some scores differ from the official ones. Changing all this can be done by simply modifying the corresponding functions in the definition of `yahtzee-fields-alist'.
Org mode export backend for exporting the document syntax tree to JSON. The main entry points are `ox-json-export-as-json and `ox-json-export-to-json'. It can also be used through the built-in export dispatcher through `org-export-dispatch'. Export options: :json-data-type-property (string) - This the name of a property added to all JSON objects in export to differentiate between structured data and ordinary key-value mappings. Its default value is "$$data_type". Setting to nil prevents the property being added altogether. :json-exporters - plist containing exporter functions for different data types. The keys appear in :json-property-types and can also be used with `ox-json-encode-with-type'. Functions are called with the value to be exported and the export info plist. Default values stored in `ox-json-default-type-exporters'. :json-property-types (plist) - Sets the types of properties of specific elements/objects. Nested set of plists - the top level is keyed by element type (see `org-element-type') and the second level by property name (used with `org-element-property'). Values in 2nd level are keys in the :json-exporters plist and are used to pick the function that will export the property value. Properties with a type of t will be encoded using `ox-json-encode-auto', but this sometimes can produce undesirable results. The "all" key contains the default property types for all element types. This option overrides the defaults set in `ox-json-default-property-types'. :json-strict (bool) - If true an error will be signaled when problems are encountered in exporting a data structure. If nil the data structure will be exported as an object containing an error message. Defaults to nil. :json-include-extra-properties (bool) - Whether to export node properties not listed in the :json-property-types option. If true these properties will be exported using `ox-json-encode-auto'.
Documentation at https://melpa.org/#/shelldon
Documentation at https://melpa.org/#/luarocks
Documentation at https://melpa.org/#/pythonic
Documentation at https://melpa.org/#/750words
Documentation at https://melpa.org/#/outshine
Documentation at https://melpa.org/#/repeater
Documentation at https://melpa.org/#/tinkerer
Documentation at https://melpa.org/#/smeargle
Documentation at https://melpa.org/#/whitaker
Documentation at https://melpa.org/#/deadgrep
Documentation at https://melpa.org/#/libmpdel
Documentation at https://melpa.org/#/tiktoken
Documentation at https://melpa.org/#/markless
Documentation at https://melpa.org/#/winpoint
Documentation at https://melpa.org/#/lobsters
Documentation at https://melpa.org/#/rbtagger
Documentation at https://melpa.org/#/savefold