emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Puneeth Chaganti <punchagan@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [org-drill] understand description-lists
Date: Tue, 25 Nov 2014 19:36:53 +0530	[thread overview]
Message-ID: <CALnw1fQjMTqzK6BjfKmd_RAj__SNEZVPVukdx2TOXaO0xW=k3g@mail.gmail.com> (raw)
In-Reply-To: <87r3wr7c2c.fsf@gmx.us>

On Tue, Nov 25, 2014 at 4:59 PM, Rasmus <rasmus@gmx.us> wrote:
> Hi,
>
> I would like to use org-drill to train my Spanish vocabulary.  However,
> it's essential that I can also export my file for "offline-review".  I
> don't want to maintain two files.  I like to organize my file like this:
>
> *** Days
> - lunes     :: Monday
> - martes    :: Tuesday
> - miércoles :: Wednesday
> - jueves    :: Thursday
> - viernes   :: Friday
> - sábado    :: Saturday
> - domingo   :: Sunday
>
> Is it possible to have org-drill realize that each side of the
> description item is a side of a card, and that the closest headline is a
> topic?

org-drill sets properties on each drill headline, to keep track of
your progress while learning that item.  So, I'm not sure it would be
easy to do without maintaining two files.

One idea could be to have a function that creates (and updates/merges)
an org-drill file from the normal file that you use for export.
org-drill ships with functions [1] for merging two drill
files/buffers.

Paul, the author of org-drill, may have better ideas, though.

[1] - http://orgmode.org/worg/org-contrib/org-drill.html#sec-11

-- 
Puneeth

  reply	other threads:[~2014-11-25 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 11:29 [org-drill] understand description-lists Rasmus
2014-11-25 14:06 ` Puneeth Chaganti [this message]
2014-11-25 14:37   ` Rasmus

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='CALnw1fQjMTqzK6BjfKmd_RAj__SNEZVPVukdx2TOXaO0xW=k3g@mail.gmail.com' \
    --to=punchagan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).