emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: e.fraga@ucl.ac.uk
Cc: emacs-orgmode@gnu.org
Subject: Re: latex fragment problems with * environments
Date: Tue, 12 May 2009 12:29:41 +0200	[thread overview]
Message-ID: <05754EA5-3E43-4638-8F47-7B5B293327EC@gmail.com> (raw)
In-Reply-To: <18953.19070.36647.266729@pinto.chemeng.ucl.ac.uk>

On May 12, 2009, at 12:07 PM, Eric S Fraga wrote:

> Carsten Dominik writes:
>> Hi Eric,
>> this was fixed 11 days ago in commit
>>    5f86fd7ae2da40b20c967382fa938fc871fb7e44
>> If you use the latet git version, this problem will not be present.
> Apologies.  I missed this.  I don't track the latest git version,
> preferring to track the debian unstable version as it makes my life
> easier (given that I use 3+ computers daily...).  I do, however, try
> to keep track of what has been fixed and I missed this.

No problem.

I need to make a new release soon, enough stuff has accuulated

- Carsten

  reply	other threads:[~2009-05-12 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 18:02 latex fragment problems with * environments Eric S Fraga
2009-05-11 20:52 ` Carsten Dominik
2009-05-12 10:07   ` Eric S Fraga, Eric S Fraga
2009-05-12 10:29     ` Carsten Dominik [this message]
2009-05-12 10:34       ` Eric S Fraga, Eric S Fraga

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:

  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=05754EA5-3E43-4638-8F47-7B5B293327EC@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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).