From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Block level specification for tex code html export method
Date: Thu, 03 Sep 2015 22:11:42 +0100 [thread overview]
Message-ID: <olupp1zmcmp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87egifp7jb.fsf@ucl.ac.uk
Hi Eric,
Thanks for following that up!
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Thursday, 3 Sep 2015 at 13:30, Andreas Leha wrote:
>> Hi Alan,
>>
>> Glad you like the example.
>>
>> Three things:
>> 1. It still works for me ;-)
>
> Andreas,
>
> the example doesn't work for me with a quite recent org (updated within
> the past week) and with -Q.
I see. Another reason for me not to upgrade? My org is quite old.
(8.3beta (release_8.3beta-1264-g365c19))
>
> By the way, with emacs -Q, I need to "(required 'cl)" for the by-backend
> macro although this is probably done by one of the export files?
>
>> 2. The distorted png might come from the bug in htlatex I mentioned in
>> this thread [1].
>
> The solution has been pointed out by Haochen Xie in this thread
> (":imagemagick yes"). I needed this fix as well to get the png creation
> to work.
>
Good to know! Thanks for the confirmation. I missed that.
Note also that it might be necessary to include
#+header: :headers '("\\usepackage{tikz}")
to the latex block. This I only need when testing with emacs -Q. Not
sure why, though. I was under the impression that global
#+latex_headers should apply in latex source blocks as well?
>> 3. It seems that the by-backend does not work properly for you. I am
>> not sure about the reason for that. What org-mode version do you run?
>
> And it doesn't work for me either. I recently ran into this problem
> myself with a document (long book chapter with many tikz figures) that I
> wrote about 4 months ago. I had a deadline so couldn't track down what
> was wrong but it is all about the by-backend macro. No matter what the
> target for export is, the by-backend macro doesn't work. I tried to fix
> it but no luck, mostly due to my lack of emacs lisp funess...
This macro is from Eric Schulte initially. And I guess I would be out
of luck adapting it to new Org mode versions as well.
I'd vote for a macro like this to be included in Org mode. I think it
is quite useful to have and somehow extends the @@latex: ...@ constructs
to babel. That way updates to org breaking this would be less probable.
Unfortunately, I don't have the time right now to even upgrade Org mode.
So, I cannot offer any testing/bisecting, I am afraid.
Best,
Andreas
next prev parent reply other threads:[~2015-09-03 21:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 8:11 Block level specification for tex code html export method Haochen Xie
2015-08-10 22:56 ` Andreas Leha
2015-08-11 8:47 ` Haochen Xie
2015-08-11 8:53 ` Fabrice Popineau
2015-08-11 16:24 ` Haochen Xie
2015-08-12 8:50 ` Andreas Leha
2015-08-12 12:51 ` Haochen Xie
2015-08-12 13:40 ` Andreas Leha
2015-09-03 11:42 ` Alan Schmitt
2015-09-03 12:30 ` Andreas Leha
2015-09-03 13:03 ` Haochen Xie
2015-09-03 20:39 ` Andreas Leha
2015-09-03 20:33 ` Eric S Fraga
2015-09-03 21:11 ` Andreas Leha [this message]
2015-09-03 21:38 ` Nicolas Goaziou
2015-09-04 6:15 ` Eric S Fraga
2015-09-04 6:23 ` Haochen Xie
2015-09-04 7:07 ` Eric S Fraga
2015-09-04 7:10 ` Alan Schmitt
2015-09-04 12:08 ` Andreas Leha
2015-09-04 12:48 ` Nicolas Goaziou
2015-09-04 13:42 ` Andreas Leha
2015-09-05 8:58 ` Nicolas Goaziou
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=olupp1zmcmp.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).