emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Org-Drill] Latex Images are removed in sessions
Date: Thu, 09 Oct 2014 21:23:37 +0200	[thread overview]
Message-ID: <84oatldp3a.fsf@tm6592.fritz.box> (raw)
In-Reply-To: 8738axcepg.fsf@ilxwinb01.fritz.box

Hi Thomas,

> first of all thanks for the great piece of software.

Totally agreed.

> ------------------------------------------------------------
> * Einheitliche Kreisbewegung                                          :drill:
>
> Zentripetale Beschleunigung bei gegebener Geschwindigkeit $v$ und
> Radius $r$.
>
> ** Antwort
>
> #+BEGIN_LATEX
>   \begin{equation}
>     \label{eq:1}
>     a = \frac{v^2}{r}.
>   \end{equation}
> #+END_LATEX
>
> ------------------------------------------------------------
>
> What I usually do is to generate latex fragments of the whole tree by
> going to the beginning of the buffer and executing
> `org-toggle-latex-fragment' (C-c C-x C-l). After that I execute `M-x
> org-drill'. This usually works rather fine. Although there are a few
> issues:
>
> [...issues...]
>
> Can you give me a hint on how to investigate this problem further?
> org-mode is on version 8.3beta (installed via el-get) and org-drill
> seems to be at 2.4.1 at least it says so in org-drill.el.

Obviously there already is some logic in org-drill.org to handle latex
fragments.  See the lines containing (org-preview-latex-fragment).
Looks like the logic for displaying the fragments is somehow broken.

A pragmatic patch to keep you going with physics drills could be to
comment out all those lines containing (org-preview-latex-fragment) in
org-drill.org.


HTH,  Marco
-- 
http://www.wahlzone.de
PGP: 0x0A3AE6F2

      reply	other threads:[~2014-10-09 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 17:53 [Org-Drill] Latex Images are removed in sessions Thomas Bach
2014-10-09 19:23 ` Marco Wahl [this message]

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=84oatldp3a.fsf@tm6592.fritz.box \
    --to=marcowahlsoft@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).