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.

1 files changed, 20 insertions, 14 deletions

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
 # <<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.
-