Hi David and Eric,
Reverting the following fixes the export corruption bug for me.
commit ec293ae62b1d92a45b752beb29b9d4163c04c573
Author: Eric Schulte schulte.e...@gmail.com
Date: Fri May 6 14:45:38 2011 -0600
Thanks.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I
Hi David,
Sorry it took me a while to notice this thread -- incidentally after a
patch to this effect was shared by Lawrence Mitchell in a separate
thread. I've just applied Lawrence's patch, which should resolve this
issue as well.
Please let me know if the problem remains. Now that this
On 2011-06-02, Eric Schulte schulte.e...@gmail.com wrote:
Please let me know if the problem remains. Now that this thread is on
my radar I should be more attentive to it.
Thanks Eric, David. Test case and .emacs seem to work for it so far.
To anybody: I noticed that the region stays active
Samuel Wales samolog...@gmail.com writes:
On 2011-06-02, Eric Schulte schulte.e...@gmail.com wrote:
Please let me know if the problem remains. Now that this thread is
on
my radar I should be more attentive to it.
Thanks Eric, David. Test case and .emacs seem to work for it so far.
At Fri, 27 May 2011 07:15:10 -0700,
Samuel Wales wrote:
Hi David,
Thank you. I am unable to debug this further so I appreciate it.
I've just pushed a fix for compatibility with Emacs22 and the
`activate-mark' function.
Were you able to reproduce the corruption bug? Did anybody else?
Hi David,
Thank you. I am unable to debug this further so I appreciate it.
Is it necessary to construct this regexp for babel if babel is not used?
Were you able to reproduce the corruption bug? Did anybody else?
Emacs -Q, minimal test case.
(I'm trying to warn the world about one
At Wed, 25 May 2011 09:58:03 -0700,
Samuel Wales wrote:
Minimal .emacs and test case for export corruption bug.
Okay, I can reproduce the args out of range with Emacs 22. Turns out
that `regexp-opt` behaves different when creating
`org-babel-result-regexp'.
(regexp-opt org-babel-data-names)
