emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: jamshark70@dewdrop-world.net
Cc: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: Fwd: [bug] Beamer export fails in current master
Date: Wed, 15 Jan 2014 22:29:32 +0100	[thread overview]
Message-ID: <87ppntvsqr.fsf@gmail.com> (raw)
In-Reply-To: <CAFniQ7WAAe9txPsOCeS7nNct_siunLsxqYQuhe7Rm3zMCF67UQ@mail.gmail.com> (James Harkins's message of "Sat, 11 Jan 2014 17:44:47 +0800")

Hello,

James Harkins <jamshark70@gmail.com> writes:

> Fine thought, but my bisect regimen went something like this:
>
> 1. Delete all elc files from the location from which I'm loading org.
>
> 2. Quit emacs.
>
> 3. At every bisect step, launch Emacs fresh with "emacs
> /path/to/test-file.org" and then do nothing except C-c C-e l B. Then
> quit Emacs.
>
> 4. If I got the error, git bisect bad. If I got an export buffer of
> LaTeX code, git bisect good.
>
> When I got the error, it was always consistently reproducible for that
> revision, and it was always enough to launch Emacs, open the file and
> try the export, no fancy other things to mess up the cache.

I see nothing wrong in that process. Can you still reproduce the error
with latest Org?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-01-15 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11  3:40 [bug] Beamer export fails in current master James Harkins
2014-01-11  8:25 ` Nicolas Goaziou
     [not found]   ` <CAFniQ7XfifzACfVQLTTtesmUaCOpM3Q-esyYMorc7KFUQcmRhg@mail.gmail.com>
2014-01-11  9:44     ` Fwd: " James Harkins
2014-01-15 21:29       ` Nicolas Goaziou [this message]
2014-01-18  1:39         ` James Harkins
2014-01-18 16:33           ` Nicolas Goaziou
2014-01-19  5:25             ` James Harkins

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=87ppntvsqr.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=jamshark70@dewdrop-world.net \
    /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).