Hi,
> I see. Would you like to continue to receive bug reports based on
> byte-compilation, or should I just load the sources for now?
>
Just pushed a fix that nukes all the warnings that the byte-compiler was
generating.
Jambunathan K.
> Hi,
>
> I see. Would you like to continue to receive bug reports based on
> byte-compilation, or should I just load the sources for now?
The one you reported is a serious error and I have fixed it.
Anything amounting to a crash or a crash in waiting has to be
immeditately addressed. As for wa
Hi,
I see. Would you like to continue to receive bug reports based on
byte-compilation, or should I just load the sources for now?
Yours,
Christian
On 3/21/11 2:31 PM, Jambunathan K wrote:
Hello Christian
Thanks for your first bug report. I have the habit of not using
byte-compilation.
Th
Hello Christian
Thanks for your first bug report. I have the habit of not using
byte-compilation.
The reason for the crash you have reported is that
`with-org-html-preserve-paragraph-state' is a macro and some of the
references to it preceded the definition. As a result the byte compiler
was mi
Hi, Jambunathan,
Thanks, I should have tested first if the previous instructions
worked. I think I have it set up now.
With a minimal Emacs as per the old instructions, and with one minor
change to your test file (`LaTeX:verbatim' -- I don't have dvipng
installed), I get this:
Debugger en
> 1. A generic exporter
There is lots of generic exporter floating around and I don't want to
add to confusion. Let's call the new patch `newhtml' with the
understanding that the patch does much more than offer a new html and
odt backends.
For the developers among us, refer to the following post
> How does this relate to the docbook exporter?
(In principle), Docbook exporter can move to the new core. This would
considerably reduce the size of the org-docbook.el.
> I ask because I needed a generic exporter (this was more than a year
> ago) and I made do with the docbook exporter for that
Christian Moe writes:
> Hi,
>
> I'd love to try it out, but I'm not good at git. Would someone be kind
> enough to post directions?
>
> I thought this would do it:
>
> git checkout 3d802
> git checkout -b ooo
> git apply
> ../0001-Re-implement-org-export-as-html-and-add-support-for-.patch
>
> But
How does this relate to the docbook exporter?
I ask because I needed a generic exporter (this was more than a year ago)
and I made do with the docbook exporter for that purpose
Christian
Thanks being the first one here (again).
I have tried incorporating some subset (and not all) of your feedback on
the new odt exporter. My priority was to get the html exporter and the
generic interface right.
> Hi,
>
> I'd love to try it out, but I'm not good at git. Would someone b
Bastien,
>> This patch introduces 3 major features:
>> 1. A generic exporter
>
> Let me understand: this is more a generalization of the HTML export than
> a true generic exporter, right? The docstring of org-do-export suggests
> so. Rewriting org-html.el so that the HTML export is done in a mo
Hi,
I'd love to try it out, but I'm not good at git. Would someone be kind
enough to post directions?
I thought this would do it:
git checkout 3d802
git checkout -b ooo
git apply
../0001-Re-implement-org-export-as-html-and-add-support-for-.patch
But I got:
error: patch failed: lisp/org.el
Hi Jambunathan,
Jambunathan K writes:
> This is a formal request to integrate my org-html.el & org-odt.el
> changes in to the master branch.
Thanks a *LOT* for this work! I'm willing to help as much as possible
to get this integrated.
> This patch introduces 3 major features:
> 1. A generic
13 matches
Mail list logo
