branch: externals/taxy commit 7c4e60bf2e86388beb381519771ca572e23503a2 Author: Adam Porter <a...@alphapapa.net> Commit: Adam Porter <a...@alphapapa.net>
Docs: Fix code block export lines --- README.org | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.org b/README.org index 2a78858..d114c9a 100644 --- a/README.org +++ b/README.org @@ -795,7 +795,7 @@ Now we'll define the default keys to use when classifying items. This list is e Finally, rather than using a pre-made taxy struct, we make one at runtime, making the ~:take~ function with ~taxy-make-take-function~. -#+begin_src elisp :exports both :results code :lexical t +#+begin_src elisp :exports code :results code :lexical t (let ((taxy (make-taxy :name "Sporty (DSL)" :take (taxy-make-take-function sporty-default-keys @@ -829,7 +829,7 @@ As you can see, the result is the same as that in the previous example, but we'v This also allows the grouping keys to be easily changed at runtime, producing a different result. For example, we could group sports by, first, whether they use a ball, and then by venue. Let's do this in a function so that users can pass their own list of keys: -#+begin_src elisp :exports both :results code :lexical t +#+begin_src elisp :exports code :results code :lexical t (cl-defun sporty-classify (sports &key (keys sporty-default-keys)) (declare (indent defun)) (let* ((taxy (make-taxy @@ -848,7 +848,7 @@ This also allows the grouping keys to be easily changed at runtime, producing a And this produces: #+RESULTS: -#+begin_src elisp +#+begin_src elisp :exports code ("Sporty (DSL)" ((outdoor ("Ultimate" "Disc golf")) @@ -863,7 +863,7 @@ And this produces: Showing a =taxy= with =magit-section= is very easy: -#+BEGIN_SRC elisp +#+BEGIN_SRC elisp :exports code (require 'taxy-magit-section) ;; Using the `numbery' taxy defined in earlier examples: