aboutsummaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authoreeeickythump <devnull@localhost>2011-04-22 15:41:08 +1200
committereeeickythump <devnull@localhost>2011-04-22 15:41:08 +1200
commit97aad887284ac4d9590e31f843d4f4f11393e9be (patch)
tree2b75b3dab0e0a4a5dbf1fec9dc61e37c4f3b80aa /README.org
parent17c34adec502b8d4368d7dd09a23041b9891cdaa (diff)
downloadorg-drill-97aad887284ac4d9590e31f843d4f4f11393e9be.tar.gz
org-drill-97aad887284ac4d9590e31f843d4f4f11393e9be.zip
- 'multicloze' card type renamed to 'hide1cloze' (though 'multicloze' is
still recognised as a synonym, for backwards compatibility) - new card type 'show1cloze' -- like hide1cloze, but only reveals one of the areas of clozed text in the item. - when 'revealing' an item during a drill session, do not show contents of any subheadings which are themselves tagged as drill items. This means you can have drill items inside drill items, without giving their answers away when you review the parent item. - better ensure visibility state of the org buffer is restored after the drill session. - syntax highlighting of [clozed text] now works if other faces are applied inside the clozed text area, eg [the *largest* city]
Diffstat (limited to 'README.org')
-rwxr-xr-xREADME.org19
1 files changed, 13 insertions, 6 deletions
diff --git a/README.org b/README.org
index 491378d..168182b 100755
--- a/README.org
+++ b/README.org
@@ -82,7 +82,7 @@ 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:
- [[Two-sided cards]]
- [[Multi-sided cards]]
-- [[Multicloze cards]]
+- [[Multi-cloze cards]]
- [[User-defined card types]]
*A note about comments:* In org mode, comment lines start with '#'. The rest of
@@ -286,14 +286,21 @@ The capital city of New Zealand is Wellington, which is located in
the [North|North/South] Island.
#+END_EXAMPLE
-However, this is really cumbersome. The 'multicloze' card type exists for this
+However, this is really cumbersome. Multicloze card types exist for this
situation. Multicloze cards behave like 'simple' cards, except that when there
-is more than one area marked as cloze text, only one of the marked areas will
-be hidden during review -- the others all remain visible. The hidden text area
-is chosen randomly at each review.
+is more than one area marked as cloze text, some but not all of the areas
+are hidden. There are two types of multicloze card:
+
+1. =hide1cloze= -- one of the marked areas is hidden during review; the others
+ all remain visible. The hidden text area is chosen randomly at each review.
+ (Note: this type used to be called 'multicloze', and that card type is
+ retained as a synonym for 'hide1cloze'.)
+2. =show1cloze= -- only one of the marked areas is visible during review; all
+ the others are hidden. The hidden text area is chosen randomly at each
+ review.
So, for the above example, we can actually use the original 'bad' simple card,
-but change its card type to 'multicloze'. Each time the card is presented for
+but change its card type to 'hide1cloze'. Each time the card is presented for
review, one of 'New Zealand', 'Wellington', 'the South Island' or '400,000'
will be hidden.