emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: Richard Stanton <stanton@haas.berkeley.edu>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Question on latex source block
Date: Thu, 13 Sep 2012 12:04:15 -0400	[thread overview]
Message-ID: <10651.1347552255@alphaville> (raw)
In-Reply-To: Message from Eric Schulte <eric.schulte@gmx.com> of "Thu, 13 Sep 2012 09:07:55 MDT." <87392mnepg.fsf@gmx.com>

Eric Schulte <eric.schulte@gmx.com> wrote:

> Jambunathan K <kjambunathan@gmail.com> writes:
> 
> > Eric Schulte <eric.schulte@gmx.com> writes:
> >
> >> Alright,
> >>
> >> I've just committed a patch which gets part-way to your suggest
> >> solution.  While the two backend-specific functions are still separate
> >> (I agree they should be combined), I have brought back the
> >> `org-create-formula-image' function, which now dispatches to the backend
> >> specific functions.
> >>
> >> Additionally there are some problems in the `org-format-latex' function.
> >> It lists mandatory arguments as optional, and appears to create
> >> variables which are not required or properly set.
> >>
> >> These function should probably be cleaned at some point up by whoever is
> >> maintaining Org-mode's LaTeX interfaces.
> >
> > This (or one of the recent commits) is creating the following
> > regression.  I have not dived in to the details.
> >
> 
> Perhaps you could use git-bisect to find the ID of the offending commit?
> 

I did and I replied both to the list and cc: to you and Jambunathan (and
I added a clarification later). You probably haven't reached that point in
your email backlog yet, but if you don't see them let me know and I'll
forward them to you.

Nick

  reply	other threads:[~2012-09-13 16:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09  5:15 Question on latex source block Richard Stanton
2012-09-09  7:07 ` Nick Dokos
2012-09-09  7:17   ` Nick Dokos
2012-09-09 16:49   ` Eric Schulte
2012-09-09 17:44     ` Nick Dokos
2012-09-09 19:39       ` Eric Schulte
2012-09-09 20:31         ` Nick Dokos
2012-09-13  6:00         ` Jambunathan K
2012-09-13  7:28           ` Nick Dokos
2012-09-13  7:58             ` Nick Dokos
2012-09-13 15:07           ` Eric Schulte
2012-09-13 16:04             ` Nick Dokos [this message]
2012-09-13 17:09               ` Eric Schulte
2012-09-13 19:12                 ` Abdó Roig-Maranges
2012-09-13 19:42                   ` Jambunathan K
2012-09-14  7:27                     ` Bastien
     [not found] <mailman.113.1347292828.2054.emacs-orgmode@gnu.org>
2012-09-10 16:49 ` Richard Stanton
2012-09-10 19:07   ` Nick Dokos
2012-09-10 20:43     ` Richard Stanton
2012-09-10 20:53       ` Nick Dokos
2012-09-11  6:52         ` Giovanni Ridolfi

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=10651.1347552255@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.com \
    --cc=kjambunathan@gmail.com \
    --cc=stanton@haas.berkeley.edu \
    /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).