From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: Preview Latex fragments should include definitions in #+LATEX_HEADER: [6.33trans (release_6.33f.71.g0969.dirty)]
Date: Mon, 07 Dec 2009 14:39:24 -0300 [thread overview]
Message-ID: <4b1d3dd6.0407c00a.08c1.ffffd863@mx.google.com> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------
Hello all,
I have defined the command "vetor" in a org file header with the line below
#+LATEX_HEADER:\newcommand{\vetor}[1]{{\mathbf{#1}}}
It works correctly when exporting to latex, but the preview of latex fragments
with C-c C-x C-l does not work for equations that use the defined command.
After customizing the variable "Org Format Latex Header" through the customize
buffer to include the newcommand at the end, the preview of latex fragments
worked as expected.
If this is not a bug, I'd like to make a feature request. That is, everything
that is included in the header of the exported latex document
with #+LATEX_HEADER: should be also included in the variable
org-format-latex-header such that the preview functionality can work as expected
with user defined commands or included packages.
- Darlan Cavalcante
Emacs : GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0)
of 2009-09-27 on crested, modified by Debian
Package: Org-mode version 6.33trans (release_6.33f.71.g0969.dirty)
next reply other threads:[~2009-12-07 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:39 Darlan Cavalcante Moreira [this message]
2010-01-01 10:18 ` Bug: Preview Latex fragments should include definitions in #+LATEX_HEADER: [6.33trans (release_6.33f.71.g0969.dirty)] Carsten Dominik
2010-01-04 15:36 ` Darlan Cavalcante Moreira
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=4b1d3dd6.0407c00a.08c1.ffffd863@mx.google.com \
--to=darcamo@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).