From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Symbol's value as variable is void
Date: Thu, 28 Jan 2010 17:15:19 -0500 [thread overview]
Message-ID: <9468.1264716919@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Thomas S. Dye" <tsd@tsdye.com> of "Wed, 27 Jan 2010 14:52:31 -1000." <8318ED89-925E-4D87-8559-6764017F38B3@tsdye.com>
Thomas S. Dye <tsd@tsdye.com> wrote:
> Thanks Nick,
>
> Perhaps that is the relevant commit. I'm pretty sure it was made =20
> subsequent to my last successful export.
>
> All the best,
> Tom
>
> On Jan 27, 2010, at 2:37 PM, Nick Dokos wrote:
>
> > I took a quick look but I don't know what's wrong: Eric S. will have =20=
>
> > to take a look,
> > but this commit seems relevant:
> >
> > commit d154f2794741275a41d4631892335d581d7da27a
> > Author: Eric Schulte <schulte.eric@gmail.com>
> > Date: Mon Jan 18 13:03:36 2010 -0700
> >
> > babel: no longer overwriting non-babel src blocks org-exp-blocks: =20=
>
> > adding progress-marker local variable
> >
> > the progress-marker local variable set inside of a let in
> > org-exp-blocks is used to constrain searches in org-babel-exp to
> > ensure that a babel block doesn't overwrite non-babel src blocks
> >
I'm blind: Eric S. fixed it on Monday with
commit b59a57e8909e38fd4c69c7c62ec8ecad87e8528e
Author: Eric Schulte <schulte.eric@gmail.com>
Date: Mon Jan 25 23:54:03 2010 -0700
babel: bug fix related to "no longer overwriting non-babel src blocks" commit
this fixes a bug introduced in commit
d154f2794741275a41d4631892335d581d7da27a
You just need to update I think.
Nick
prev parent reply other threads:[~2010-01-28 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 23:05 Symbol's value as variable is void Thomas S. Dye
2010-01-27 23:42 ` Nick Dokos
2010-01-28 0:09 ` Thomas S. Dye
2010-01-28 0:37 ` Nick Dokos
2010-01-28 0:52 ` Thomas S. Dye
2010-01-28 22:15 ` Nick Dokos [this message]
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=9468.1264716919@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).