From: phillip.lord@russet.org.uk (Phillip Lord)
To: Gerhard Butscher <gerhard.butscher@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-drill vocabulary and question about properties
Date: Wed, 31 Jul 2019 12:44:38 +0100 [thread overview]
Message-ID: <87imri4ee1.fsf@russet.org.uk> (raw)
In-Reply-To: <WM!fa384f8b7f257507d091606088897a6d13f2e56e737227ef2e036a835b70c7579f2959b493bb262460d406db80a2e5d5!@mailhub-mx4.ncl.ac.uk> (Gerhard Butscher's message of "Mon, 29 Jul 2019 16:56:44 +0200")
"Gerhard Butscher" <gerhard.butscher@gmx.net> writes:
> Hello, I intend to use org-drill for learning vocabulary
> (german-spanish). Does anybody know a repository of such a vocabulary?
>
> As far as I know the inner workings of org-drill are placed in the
> :PROPERTIES: section of the item. When I use :DRILL_CARD_TYPE:
> twosided then the item gets questioned some time in german and some
> time in spanish. But the PROPERTIES are still only once there. If I
> want to track the learning in both directions separately, I need to
> make two items for one word, once german-spanish and once
> spanish-german. Am I right?
Yes, the properties are shared.
For language learning, I use multi-cloze cards with
"hide1_firstmore". So:
It: [Ciao]
En: [Hello/Goodbye]
So you learn in both directions, but see the foreign language phrase
more often (assuming you are not Italian, of course).
My experience is you are better of making your own vocabulary -- since
you need to use org-drill learning to reinforce other forms of learning,
and you spend more time learning the vocab than you will writing it. The
only bits that I automate are the verb tables.
Phil
next prev parent reply other threads:[~2019-07-31 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:56 org-drill vocabulary and question about properties Gerhard Butscher
[not found] ` <WM!fa384f8b7f257507d091606088897a6d13f2e56e737227ef2e036a835b70c7579f2959b493bb262460d406db80a2e5d5!@mailhub-mx4.ncl.ac.uk>
2019-07-31 11:44 ` Phillip Lord [this message]
2019-07-31 19:32 ` Milan Zamazal
2019-08-01 3:09 ` Bob Newell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imri4ee1.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-orgmode@gnu.org \
--cc=gerhard.butscher@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).