From: <yggdrasil@gmx.co.uk>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: imaxima babel
Date: Thu, 28 Nov 2013 00:10:30 +0100 [thread overview]
Message-ID: <87vbzdmoex.fsf@gmx.co.uk> (raw)
In-Reply-To: <m2a9gq5ind.fsf@polytechnique.org> (Alan Schmitt's message of "Wed, 27 Nov 2013 09:54:46 +0100")
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
> This is very useful, thanks a lot. A couple comments and questions on
> your example file (which would be a nice addition to worg).
>
There is actually already some maxima documentation on worg that got me
started as I was unsure if maxima is supported at all, I have added the
link in the summary. It would probably be good to merge to worg, but I
have no access to it and not time right now to learn how it works. Feel
free to copy paste whatever is useful to amend it though.
> It would be useful to know more about maxima and how to enable it with
> babel (a link to existing documentation, if there is any, would be
> great).
>
Thanks for the pointer, I have included some more resources I used.
> In my setup, the previewing latex fragment keybinding is "C-c C-x C-l",
> not "C-c C-x C-x".
Sorry, that was a typo!
>
> I tried previewing the fragment, but I got the error:
>
> ,----
> | Failed to create dvi file from
> /var/folders/68/fvntfrw92y50gkk_67rkhsfw0000gn/T/orgtex16220cbr.tex
> `----
>
> Looking at the tex file and the log file, it seems that the tex files is
> to be processed by xelatex, but the command called seems to be pdfTeX. I
> probably have something misconfigured, but I don't know what it is. Any
> suggestion?
>
Are you sure you have 'dvipng' installed as mentioned in the manual?
,----
| If you have `dvipng' installed, LaTeX fragments can be processed to
| produce preview images of the typeset expressions:
`----
I have dvipng 1.14 that comes with texlive 2013-3 in F20 which seems to
work fine.
> Finally, and it's a nitpick: breaking lines in the middle of (info ...)
> links prevents following them using "C-x C-e".
>
Actually, I never used these sort of links myself, thanks for pointing
out how this is done! :) I moved all infolinks to footnotes to avoid the
line breaks.
All the best,
J
[-- Attachment #2: orgmaxima_example.org --]
[-- Type: application/vnd.lotus-organizer, Size: 2090 bytes --]
next prev parent reply other threads:[~2013-11-27 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 22:58 imaxima babel yggdrasil
2013-11-21 23:07 ` Rüdiger Sonderfeld
2013-11-21 23:33 ` Eric Schulte
2013-11-22 17:05 ` yggdrasil
2013-11-23 16:12 ` Eric Schulte
2013-11-26 21:53 ` yggdrasil
2013-11-27 8:54 ` Alan Schmitt
2013-11-27 23:10 ` yggdrasil [this message]
2013-11-28 0:42 ` Nick Dokos
2013-11-28 1:09 ` Thomas S. Dye
2013-11-30 10:19 ` Cannot generate latex preview images (Was: imaxima babel) Alan Schmitt
2013-11-30 12:49 ` Cannot generate latex preview images Nicolas Goaziou
2013-12-02 10:09 ` Alan Schmitt
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=87vbzdmoex.fsf@gmx.co.uk \
--to=yggdrasil@gmx.co.uk \
--cc=alan.schmitt@polytechnique.org \
--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).