From 6be323d0335245c47392fd3671dd781b3e4b2d81 Mon Sep 17 00:00:00 2001 From: eeeickythump Date: Wed, 5 Sep 2012 10:46:16 +1200 Subject: Entries in 'org-drill-card-type-alist' can now take a fourth argument, 'drill-empty-p' (boolean). If true, items of this type are not skipped if their bodies are empty. Bugfixes related to cram mode. Cram mode displays a coloured 'C' in the mode line. Sped up testing whether items have empty bodies. Updated documentation. --- org-drill.el | 169 +++++++++++++++++----------- org-drill.html | 345 +++++++++++++++++++++++++++++++-------------------------- org-drill.org | 34 +++--- 3 files changed, 315 insertions(+), 233 deletions(-) diff --git a/org-drill.el b/org-drill.el index b71b1bd..bfce766 100755 --- a/org-drill.el +++ b/org-drill.el @@ -2,7 +2,7 @@ ;;; org-drill.el - Self-testing using spaced repetition ;;; ;;; Author: Paul Sexton -;;; Version: 2.3.6 +;;; Version: 2.3.7 ;;; Repository at http://bitbucket.org/eeeickythump/org-drill/ ;;; ;;; @@ -209,38 +209,48 @@ the hidden cloze during a test.") (defcustom org-drill-card-type-alist - '((nil . org-drill-present-simple-card) - ("simple" . org-drill-present-simple-card) - ("twosided" . org-drill-present-two-sided-card) - ("multisided" . org-drill-present-multi-sided-card) - ("hide1cloze" . org-drill-present-multicloze-hide1) - ("hide2cloze" . org-drill-present-multicloze-hide2) - ("show1cloze" . org-drill-present-multicloze-show1) - ("show2cloze" . org-drill-present-multicloze-show2) - ("multicloze" . org-drill-present-multicloze-hide1) - ("hidefirst" . org-drill-present-multicloze-hide-first) - ("hidelast" . org-drill-present-multicloze-hide-last) - ("hide1_firstmore" . org-drill-present-multicloze-hide1-firstmore) - ("show1_lastmore" . org-drill-present-multicloze-show1-lastmore) - ("show1_firstless" . org-drill-present-multicloze-show1-firstless) - ("conjugate" org-drill-present-verb-conjugation + '((nil org-drill-present-simple-card) + ("simple" org-drill-present-simple-card) + ("twosided" org-drill-present-two-sided-card nil t) + ("multisided" org-drill-present-multi-sided-card nil t) + ("hide1cloze" org-drill-present-multicloze-hide1) + ("hide2cloze" org-drill-present-multicloze-hide2) + ("show1cloze" org-drill-present-multicloze-show1) + ("show2cloze" org-drill-present-multicloze-show2) + ("multicloze" org-drill-present-multicloze-hide1) + ("hidefirst" org-drill-present-multicloze-hide-first) + ("hidelast" org-drill-present-multicloze-hide-last) + ("hide1_firstmore" org-drill-present-multicloze-hide1-firstmore) + ("show1_lastmore" org-drill-present-multicloze-show1-lastmore) + ("show1_firstless" org-drill-present-multicloze-show1-firstless) + ("conjugate" + org-drill-present-verb-conjugation org-drill-show-answer-verb-conjugation) - ("spanish_verb" . org-drill-present-spanish-verb) + ("spanish_verb" org-drill-present-spanish-verb) ("translate_number" org-drill-present-translate-number)) - "Alist associating card types with presentation functions. Each entry in the -alist takes one of two forms: -1. (CARDTYPE . QUESTION-FN), where CARDTYPE is a string or nil (for default), - and QUESTION-FN is a function which takes no arguments and returns a boolean - value. -2. (CARDTYPE QUESTION-FN ANSWER-FN), where ANSWER-FN is a function that takes - one argument -- the argument is a function that itself takes no arguments. - ANSWER-FN is called with the point on the active item's - heading, just prior to displaying the item's 'answer'. It can therefore be - used to modify the appearance of the answer. ANSWER-FN must call its argument - before returning. (Its argument is a function that prompts the user and - performs rescheduling)." + "Alist associating card types with presentation functions. Each +entry in the alist takes the form: + +;;; (CARDTYPE QUESTION-FN [ANSWER-FN DRILL-EMPTY-P]) + +Where CARDTYPE is a string or nil (for default), and QUESTION-FN +is a function which takes no arguments and returns a boolean +value. + +When supplied, ANSWER-FN is a function that takes one argument -- +that argument is a function of no arguments, which when called, +prompts the user to rate their recall and performs rescheduling +of the drill item. ANSWER-FN is called with the point on the +active item's heading, just prior to displaying the item's +'answer'. It can therefore be used to modify the appearance of +the answer. ANSWER-FN must call its argument before returning. + +When supplied, DRILL-EMPTY-P is a boolean value, default nil. +When non-nil, cards of this type will be presented during tests +even if their bodies are empty." :group 'org-drill - :type '(alist :key-type (choice string (const nil)) :value-type function)) + :type '(alist :key-type (choice string (const nil)) + :value-type function)) (defcustom org-drill-scope @@ -1276,28 +1286,29 @@ How well did you do? (0-5, ?=help, e=edit, t=tags, q=quit)" ((and (>= ch ?0) (<= ch ?5)) (let ((quality (- ch ?0)) (failures (org-drill-entry-failure-count))) - (save-excursion - (org-drill-smart-reschedule quality - (nth quality next-review-dates))) - (push quality *org-drill-session-qualities*) - (cond - ((<= quality org-drill-failure-quality) - (when org-drill-leech-failure-threshold - ;;(setq failures (if failures (string-to-number failures) 0)) - ;; (org-set-property "DRILL_FAILURE_COUNT" - ;; (format "%d" (1+ failures))) - (if (> (1+ failures) org-drill-leech-failure-threshold) - (org-toggle-tag "leech" 'on)))) - (t - (let ((scheduled-time (org-get-scheduled-time (point)))) - (when scheduled-time - (message "Next review in %d days" - (- (time-to-days scheduled-time) - (time-to-days (current-time)))) - (sit-for 0.5))))) - (org-set-property "DRILL_LAST_QUALITY" (format "%d" quality)) - (org-set-property "DRILL_LAST_REVIEWED" - (time-to-inactive-org-timestamp (current-time))) + (unless *org-drill-cram-mode* + (save-excursion + (org-drill-smart-reschedule quality + (nth quality next-review-dates))) + (push quality *org-drill-session-qualities*) + (cond + ((<= quality org-drill-failure-quality) + (when org-drill-leech-failure-threshold + ;;(setq failures (if failures (string-to-number failures) 0)) + ;; (org-set-property "DRILL_FAILURE_COUNT" + ;; (format "%d" (1+ failures))) + (if (> (1+ failures) org-drill-leech-failure-threshold) + (org-toggle-tag "leech" 'on)))) + (t + (let ((scheduled-time (org-get-scheduled-time (point)))) + (when scheduled-time + (message "Next review in %d days" + (- (time-to-days scheduled-time) + (time-to-days (current-time)))) + (sit-for 0.5))))) + (org-set-property "DRILL_LAST_QUALITY" (format "%d" quality)) + (org-set-property "DRILL_LAST_REVIEWED" + (time-to-inactive-org-timestamp (current-time)))) quality)) ((= ch ?e) 'edit) @@ -1376,9 +1387,13 @@ the current topic." (format "%s %s %s %s %s %s" (propertize (char-to-string - (case status - (:new ?N) (:young ?Y) (:old ?o) (:overdue ?!) - (:failed ?F) (t ??))) + (cond + ((eql status :failed) ?F) + (*org-drill-cram-mode* ?C) + (t + (case status + (:new ?N) (:young ?Y) (:old ?o) (:overdue ?!) + (t ??))))) 'face `(:foreground ,(case status (:new org-drill-new-count-color) @@ -1619,9 +1634,20 @@ Note: does not actually alter the item." (substring-no-properties text)))) -(defun org-drill-entry-empty-p () - (zerop (length (org-drill-get-entry-text)))) +;; (defun org-entry-empty-p () +;; (zerop (length (org-drill-get-entry-text)))) + +;; This version is about 5x faster than the old version, above. +(defun org-entry-empty-p () + (save-excursion + (org-back-to-heading t) + (let ((lim (save-excursion + (outline-next-heading) (point)))) + (org-end-of-meta-data-and-drawers) + (or (>= (point) lim) + (null (re-search-forward "[[:graph:]]" lim t)))))) +(defun org-drill-entry-empty-p () (org-entry-empty-p)) ;;; Presentation functions ==================================================== @@ -2025,6 +2051,7 @@ See `org-drill' for more details." ;; (org-back-to-heading)) (let ((card-type (org-entry-get (point) "DRILL_CARD_TYPE")) (answer-fn 'org-drill-present-default-answer) + (present-empty-cards nil) (cont nil) ;; fontification functions in `outline-view-change-hook' can cause big ;; slowdowns, so we temporarily bind this variable to nil here. @@ -2036,10 +2063,12 @@ See `org-drill' for more details." (org-show-subtree) (org-cycle-hide-drawers 'all) - (let ((presentation-fn (cdr (assoc card-type org-drill-card-type-alist)))) + (let ((presentation-fn + (cdr (assoc card-type org-drill-card-type-alist)))) (if (listp presentation-fn) (psetq answer-fn (or (second presentation-fn) 'org-drill-present-default-answer) + present-empty-cards (third presentation-fn) presentation-fn (first presentation-fn))) (cond ((null presentation-fn) @@ -2090,6 +2119,7 @@ See `org-drill' for more details." "Returns true if the current drill session has continued past its maximum duration." (and org-drill-maximum-duration + (not *org-drill-cram-mode*) *org-drill-start-time* (> (- (float-time (current-time)) *org-drill-start-time*) (* org-drill-maximum-duration 60)))) @@ -2099,6 +2129,7 @@ maximum duration." "Returns true if the current drill session has reached the maximum number of items." (and org-drill-maximum-items-per-session + (not *org-drill-cram-mode*) (>= (length *org-drill-done-entries*) org-drill-maximum-items-per-session))) @@ -2211,7 +2242,8 @@ RESUMING-P is true if we are resuming a suspended drill session." (> qual org-drill-failure-quality)) *org-drill-session-qualities*)) (max 1 (length *org-drill-session-qualities*)))) - (prompt nil)) + (prompt nil) + (max-mini-window-height 0.6)) (setq prompt (format "%d items reviewed. Session duration %s. @@ -2340,8 +2372,14 @@ one of the following values: (cond ((not (org-drill-entry-p)) nil) - ((org-drill-entry-empty-p) - nil) ; skip -- item body is empty + ((and (org-entry-empty-p) + (let* ((card-type (org-entry-get (point) "DRILL_CARD_TYPE" nil)) + (dat (cdr (assoc card-type org-drill-card-type-alist)))) + (or (null card-type) + (not (third dat))))) + ;; body is empty, and this is not a card type where empty bodies are + ;; meaningful, so skip it. + nil) ((null due) ; unscheduled - usually a skipped leech :unscheduled) ;; ((eql -1 due) @@ -2481,7 +2519,8 @@ than starting a new one." (:overdue (push (cons (point-marker) due) overdue-data)) (:old - (push (point-marker) *org-drill-old-mature-entries*))))))) + (push (point-marker) *org-drill-old-mature-entries*)) + ))))) scope) (org-drill-order-overdue-entries overdue-data) (setq *org-drill-overdue-entry-count* @@ -2500,6 +2539,7 @@ than starting a new one." (message "Drill session finished!")))) (progn (unless end-pos + (setq *org-drill-cram-mode* nil) (org-drill-free-markers *org-drill-done-entries*))))) (cond (end-pos @@ -2534,8 +2574,8 @@ all drill items are considered to be due for review, unless they have been reviewed within the last `org-drill-cram-hours' hours." (interactive) - (let ((*org-drill-cram-mode* t)) - (org-drill scope))) + (setq *org-drill-cram-mode* t) + (org-drill scope)) (defun org-drill-tree () @@ -2558,6 +2598,7 @@ were not reviewed during the last session, rather than scanning for unreviewed items. If there are no leftover items in memory, a full scan will be performed." (interactive) + (setq *org-drill-cram-mode* nil) (cond ((plusp (org-drill-pending-entry-count)) (org-drill-free-markers *org-drill-done-entries*) diff --git a/org-drill.html b/org-drill.html index 065fca3..10367c1 100644 --- a/org-drill.html +++ b/org-drill.html @@ -1,13 +1,13 @@ - + org-drill.el – flashcards and spaced repetition for org-mode + - + @@ -44,6 +44,12 @@ lang="en" xml:lang="en"> dt { font-weight: bold; } div.figure { padding: 0.5em; } div.figure p { text-align: center; } + div.inlinetask { + padding:10px; + border:2px solid gray; + margin:10px; + background: #ffffcc; + } textarea { overflow-x: auto; } .linenr { font-size:smaller } .code-highlighted {background-color:#ffff00;} @@ -79,62 +85,68 @@ lang="en" xml:lang="en"> -
+
+ +
+ +

org-drill.el – flashcards and spaced repetition for org-mode

+

Table of Contents

-

General

+

General

@@ -183,7 +195,7 @@ version. The repository is at:
-

Installation

+

Installation

@@ -205,13 +217,12 @@ to make sure that Org's "contrib/lisp" directory is in the emacs load-path. -
-

Demonstration

+

Demonstration

@@ -230,7 +241,7 @@ drill topics are written.
-

Writing the questions

+

Writing the questions

@@ -261,13 +272,13 @@ This will be adequate for some items, but usually you will want to write items where you have more control over what information is hidden from the user for recall purposes. For this reason, some other card types are defined, including:

@@ -283,9 +294,9 @@ invisible while items are being tested.
-
-

Simple topics

-
+
+

Simple topics

+
@@ -306,7 +317,6 @@ Tallinn. -

When this item is presented for review, the text beneath the main heading will be visible, but the contents of the subheading ("The Answer") will be hidden. @@ -316,9 +326,9 @@ be visible, but the contents of the subheading ("The Answer") will be hidden.

-
-

Cloze deletion

-
+
+

Cloze deletion

+
@@ -340,7 +350,6 @@ The capital city of Estonia is [Tallinn]. -

During review, the user will see:

@@ -360,15 +369,15 @@ When the user presses a key, the text "Tallinn" will become visible.
-
-

Clozed text hints

-
+
+

Clozed text hints

+

Clozed text can contain a "hint" about the answer. If the text surrounded -by single square brackets contains a `|' character (vertical bar), all text +by single square brackets contains `||' (two vertical bars), all text after that character is treated as a hint. During testing, the hint text will be visible when the rest of the text is hidden, and invisible when the rest of the text is visible. @@ -379,12 +388,11 @@ Example: -

Type 1 hypersensitivity reactions are mediated by [immunoglobulin E|molecule]
-and [mast cells|cell type].
+
Type 1 hypersensitivity reactions are mediated by [immunoglobulin E||molecule]
+and [mast cells||cell type].
 

 
 
-
 

 
 
Type 1 hypersensitivity reactions are mediated by
@@ -401,9 +409,9 @@ and
-
-

Two-sided cards

-
+
+

Two-sided cards

+

@@ -446,7 +454,6 @@ Who was that woman? -

In this example, the user will be shown the main text – "Translate this word" – and either 'la mujer', or 'the woman', at random. The section 'Example @@ -458,9 +465,9 @@ not one of the first two 'sides' of the topic.

-
-

Multi-sided cards

-
+
+

Multi-sided cards

+
@@ -490,7 +497,6 @@ the table -

The user will be shown the main text and either 'la mesa', or 'the table', or a picture of a table. @@ -500,9 +506,9 @@ The user will be shown the main text and either 'la mesa', or 'the table'

-
-

Multi-cloze cards

-
+
+

Multi-cloze cards

+
@@ -518,7 +524,6 @@ North Island and has a population of about 400,000. -

There is more than one fact in this statement – you could create a single 'simple' card with all the facts marked as cloze text, like so: @@ -527,11 +532,10 @@ There is more than one fact in this statement – you could create a single 

The capital city of [New Zealand] is [Wellington], which is located in
-the [North|North/South] Island and has a population of about [400,000].
+the [North||North/South] Island and has a population of about [400,000].
-

But this card will be difficult to remember. If you get just one of the 4 hidden facts wrong, you will fail the card. A card like this is likely to @@ -567,11 +571,10 @@ the North Island. * Fact The capital city of New Zealand is Wellington, which is located in -the [North|North/South] Island. +the [North||North/South] Island. -

However, this is really cumbersome. Multicloze card types exist for this situation. Multicloze cards behave like 'simple' cards, except that when there @@ -635,19 +638,18 @@ will be hidden. :END: The capital city of [New Zealand] is [Wellington], which is located in -the [North|North/South] Island and has a population of about [400,000]. +the [North||North/South] Island and has a population of about [400,000]. -

-
-

User-defined card types

-
+
+

User-defined card types

+
@@ -683,9 +685,9 @@ of all the card types discussed above.
-
-

Empty cards

-
+
+

Empty cards

+
@@ -703,8 +705,17 @@ unless they are empty as well.

If you have an item with an empty body, but still want it to be included in a -drill session, put a brief comment ('# …') in the item body. -

+drill session, you can either: +

    +
  1. Put a brief comment ('# …') in the item body. +
    2. +
  2. Change the entry for its card type in org-drill-card-type-alist so that + items of this type will always be tested, even if they have an empty body. + See the documentation for org-drill-card-type-alist for details. +
    3. +
+ +
@@ -712,16 +723,16 @@ drill session, put a brief comment ('# …') in the item body.
-

Running the drill session

+

Running the drill session

-Start a drill session with M-x org-drill. By default, this includes all +Start a drill session with M-x org-drill. By default, this tests all non-hidden topics in the current buffer. org-drill takes an optional argument, SCOPE, which allows it to take drill items from other -sources. See below for details. +sources. See below for details.

During a drill session, you will be presented with each item, then asked to @@ -776,7 +787,7 @@ session.

-

Multiple sequential drill sessions

+

Multiple sequential drill sessions

@@ -800,7 +811,7 @@ session without re-scanning (as if you had run org-drill-again).
-

Cram mode

+

Cram mode

@@ -810,18 +821,23 @@ There are some situations, such as before an exam, where you will want to revise all of your cards regardless of when they are next due for review.

-To do this, run a cram session with the org-drill-cram command (M-x org-drill-cram RET). This works the same as a normal drill session, except +To do this, run a cram session with the org-drill-cram command (M-x org-drill-cram). This works the same as a normal drill session, except that all items are considered due for review unless you reviewed them within the last 12 hours (you can change the number of hours by customising the variable org-drill-cram-hours).

+

+Cram sessions are not considered to be part of the normal learning process for +the tested items. Cramming will not affect when items are next due for +revision. +

-

Leeches

+

Leeches

@@ -873,7 +889,7 @@ See the SuperMemo website
-

Customisation

+

Customisation

@@ -887,9 +903,9 @@ settings by adding elisp code to your configuration file (.emacs).
-
-

Visual appearance of items during drill sessions

-
+
+

Visual appearance of items during drill sessions

+
@@ -904,7 +920,6 @@ buffers, add this to your .emacs: -

Item headings may contain information that "gives away" the answer to the item, either in the heading text or in tags. If you want item headings to be made @@ -918,14 +933,13 @@ invisible while each item is being tested, add: -

-
-

Duration of drill sessions

-
+
+

Duration of drill sessions

+
@@ -942,7 +956,6 @@ the following settings. -

If either of these variables is set to nil, then item count or elapsed time will not count as reasons to end the session. If both variables are nil, the @@ -953,9 +966,9 @@ session will not end until all outstanding items have been reviewed.

-
-

Saving buffers after drill sessions

-
+
+

Saving buffers after drill sessions

+
@@ -971,14 +984,13 @@ drill session. If you don't like this behaviour, use the following setting: -
-
-

Sources of items for drill sessions (scope)

-
+
+

Sources of items for drill sessions (scope)

+

@@ -1015,13 +1027,15 @@ the variable org-drill-scope. Possible values are: + +

-
-

Definition of old and overdue items

-
+
+

Definition of old and overdue items

+
@@ -1054,7 +1068,6 @@ than 1.0. -

After prioritising overdue items, Org-Drill next prioritises young items. These are items which were recently learned (or relearned in the case of @@ -1075,23 +1088,22 @@ of 10 days or less. To change this, use the following: -

-
-

Spaced repetition algorithm

-
+
+

Spaced repetition algorithm

+
-
-

Choice of algorithm

-
+
+

Choice of algorithm

+
@@ -1117,7 +1129,10 @@ SuperMemo algorithms. These are: -

If you want Org-Drill to use the SM2 algorithm, put the following in your + + +

+If you want Org-Drill to use the SM2 algorithm, put the following in your .emacs:

@@ -1128,14 +1143,13 @@ SuperMemo algorithms. These are: -
-
-

Random variation of repetition intervals

-
+
+

Random variation of repetition intervals

+
@@ -1144,7 +1158,7 @@ The intervals generated by the SM2 and SM5 algorithms are pretty deterministic. If you tend to add items in large, infrequent batches, the lack of variation in interval scheduling can lead to the problem of "lumpiness" -- one day a large batch of items are due for review, the next there is almost -nothing, a few days later another big pile of items is due. +nothing, a few days later another big pile of items is due, and so on.

This problem can be ameliorated by adding some random "noise" to the interval @@ -1164,14 +1178,13 @@ your .emacs: -

-
-

Adjustment for early or late review of items

-
+
+

Adjustment for early or late review of items

+
@@ -1187,7 +1200,6 @@ is also presented on the SuperMemo website. It can be enabled with: -

This will affect both early and late repetitions if the Simple8 algorithm is used. For the SM5 algorithm it will affect early repetitions only. It has no @@ -1198,9 +1210,35 @@ effect on the SM2 algorithm.

-
-

Adjusting item difficulty globally

-
+
+

Adjusting the first interval (SM5 algorithm only)

+
+ + + +

+In the SM5 algorithm, the initial interval after the first successful +presentation of an item is always 4 days. If you wish to change this for some +reason, you can do so with: +

+ + + +
(setq org-drill-sm5-initial-interval 5.0)
+
+ + +

+note that this will have no effect if you are not using the SM5 algorithm. +

+ +
+ +
+ +
+

Adjusting item difficulty globally

+
@@ -1247,15 +1285,14 @@ To alter the learn fraction, put the following in your .emacs: -
-
-

Per-file customisation settings

-
+
+

Per-file customisation settings

+

@@ -1274,7 +1311,6 @@ that file: -

You can achieve the same effect by including the settings in the 'mode line' (this must be the first line in the file), like so: @@ -1286,10 +1322,8 @@ You can achieve the same effect by including the settings in the 'mode line' -

-In either case you will need to save, close and re-open the file for the -changes to take effect. +In either case you will need to reload the file for the changes to take effect.

@@ -1298,7 +1332,7 @@ changes to take effect.
-

Coping with large collections

+

Coping with large collections

@@ -1309,23 +1343,25 @@ large. The file will be slow to load, and Emacs may have trouble syntax-highlighting the file contents correctly.

-The easiest steps to solve this problem are: +The easiest way to solve this problem is:

  1. Move your file into its own dedicated directory.
  2. Divide the file into two or more smaller files.
  3. Within each file, set org-drill-scope to 'directory'. See - per-file settings above for instructions about how to do this. + per-file settings above for instructions about how to do this.
+ +
-

Sharing, merging and synchronising item collections

+

Sharing, merging and synchronising item collections

@@ -1389,7 +1425,7 @@ procedure.
-

Incremental reading

+

Incremental reading

@@ -1446,7 +1482,6 @@ captured facts. -

Using these templates and org-protocol, you can set up buttons in your web browser to: @@ -1525,7 +1560,6 @@ Calmette-Guérin vaccine. -

You need to edit this fact so it makes sense independent of its context, as that is how it will be presented to you in future. The easiest way to turn the @@ -1550,20 +1584,21 @@ or give it different tags or properties, for example.

-

Author

+

Author

Org-Drill is written by Paul Sexton. -

+

+
-

Date: 2011-05-21 00:08:14 NZST

-

Org version 7.5 with Emacs version 23

+

Date: 2012-09-05T10:41+1200

+

Org version N/A with Emacs version 24

Validate XHTML 1.0 -
+
diff --git a/org-drill.org b/org-drill.org index b53ab2b..1d20752 100755 --- a/org-drill.org +++ b/org-drill.org @@ -146,7 +146,7 @@ When the user presses a key, the text "Tallinn" will become visible. Clozed text can contain a "hint" about the answer. If the text surrounded -by single square brackets contains a `|' character (vertical bar), all text +by single square brackets contains `||' (two vertical bars), all text after that character is treated as a hint. During testing, the hint text will be visible when the rest of the text is hidden, and invisible when the rest of the text is visible. @@ -154,8 +154,8 @@ the text is visible. Example: #+BEGIN_EXAMPLE -Type 1 hypersensitivity reactions are mediated by [immunoglobulin E|molecule] -and [mast cells|cell type]. +Type 1 hypersensitivity reactions are mediated by [immunoglobulin E||molecule] +and [mast cells||cell type]. #+END_EXAMPLE #+BEGIN_QUOTE @@ -257,7 +257,7 @@ There is more than one fact in this statement -- you could create a single #+BEGIN_EXAMPLE The capital city of [New Zealand] is [Wellington], which is located in -the [North|North/South] Island and has a population of about [400,000]. +the [North||North/South] Island and has a population of about [400,000]. #+END_EXAMPLE But this card will be difficult to remember. If you get just one of the 4 @@ -291,7 +291,7 @@ the North Island. * Fact The capital city of New Zealand is Wellington, which is located in -the [North|North/South] Island. +the [North||North/South] Island. #+END_EXAMPLE However, this is really cumbersome. Multicloze card types exist for this @@ -339,7 +339,7 @@ will be hidden. :END: The capital city of [New Zealand] is [Wellington], which is located in -the [North|North/South] Island and has a population of about [400,000]. +the [North||North/South] Island and has a population of about [400,000]. #+END_EXAMPLE @@ -381,13 +381,17 @@ Note that if an item is empty, any child drill items will *not* be ignored, unless they are empty as well. If you have an item with an empty body, but still want it to be included in a -drill session, put a brief comment ('# ...') in the item body. +drill session, you can either: +1. Put a brief comment ('# ...') in the item body. +2. Change the entry for its card type in =org-drill-card-type-alist= so that + items of this type will always be tested, even if they have an empty body. + See the documentation for =org-drill-card-type-alist= for details. * Running the drill session -Start a drill session with =M-x org-drill=. By default, this includes all +Start a drill session with =M-x org-drill=. By default, this tests all non-hidden topics in the current buffer. =org-drill= takes an optional argument, SCOPE, which allows it to take drill items from other sources. See [[scope][below]] for details. @@ -448,11 +452,15 @@ There are some situations, such as before an exam, where you will want to revise all of your cards regardless of when they are next due for review. To do this, run a /cram session/ with the =org-drill-cram= command (=M-x -org-drill-cram RET=). This works the same as a normal drill session, except +org-drill-cram=). This works the same as a normal drill session, except that all items are considered due for review unless you reviewed them within the last 12 hours (you can change the number of hours by customising the variable =org-drill-cram-hours=). +Cram sessions are not considered to be part of the normal learning process for +the tested items. Cramming will not affect when items are next due for +revision. + * Leeches # <> @@ -644,7 +652,7 @@ The intervals generated by the SM2 and SM5 algorithms are pretty deterministic. If you tend to add items in large, infrequent batches, the lack of variation in interval scheduling can lead to the problem of "lumpiness" -- one day a large batch of items are due for review, the next there is almost -nothing, a few days later another big pile of items is due. +nothing, a few days later another big pile of items is due, and so on. This problem can be ameliorated by adding some random "noise" to the interval scheduling algorithm. The author of SuperMemo actually recommends this approach @@ -743,8 +751,7 @@ You can achieve the same effect by including the settings in the 'mode line' # -*- org-drill-maximum-items-per-session: 50; org-drill-spaced-repetition-algorithm: simple8 -*- #+END_EXAMPLE -In either case you will need to save, close and re-open the file for the -changes to take effect. +In either case you will need to reload the file for the changes to take effect. * Coping with large collections @@ -754,7 +761,7 @@ If you keep all your items in a single file, it may eventually get very large. The file will be slow to load, and Emacs may have trouble syntax-highlighting the file contents correctly. -The easiest steps to solve this problem are: +The easiest way to solve this problem is: 1. Move your file into its own dedicated directory. 2. Divide the file into two or more smaller files. 3. Within each file, set =org-drill-scope= to 'directory'. See @@ -930,4 +937,3 @@ or give it different tags or properties, for example. * Author Org-Drill is written by Paul Sexton. - -- cgit v1.2.3