Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Since my last pull from git master, the preview images of my LaTeX
fragments have been black. I've tried customizing
org-format-latex-options, but while the :scale property works,
changing the :foreground property has no effect. I would like to have
it use my default foreground color. Any help w
Hi Martyn and Eric,
Martyn Jago wrote:
> Eric Schulte writes:
>> Martyn Jago writes:
>>> Eric Schulte writes:
I've just pushed up what will hopefully be a more general solution.
Basically, language-specific test files can now signal errors if they
have unmet dependencies. These
I have habits that I need to perform, e.g., every weekday, or four times
a week. I don't see a way to express that. If I could schedule a task
for +1.4d or +1.75d (respectively), I'd be happy.
Even better would be a more human-readable way to express repetition,
because in addition to being fru
"Sebastien Vauban" writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> I could not reproduce the error you describe, and your test case passes
>> for me. I have added your test case to testing/test-ob.el however so it
>> should protect from this error in the future.
>
> I can't reproduce it anymore ri
Hi Eric,
Eric Schulte wrote:
> I could not reproduce the error you describe, and your test case passes
> for me. I have added your test case to testing/test-ob.el however so it
> should protect from this error in the future.
I can't reproduce it anymore right now. But the goal was to have a fuse
Dear list
I believe I have found a bug in the export of latex source blocks (to
HTML, ascii, etc) when ob-latex.el has been loaded.
In summary, setting the :exports argument as a header property fails
to override the default value in org-babel-default-header-args:latex
Please see the attached or
Hi Nicolas
On Fri, Sep 23, 2011 at 18:45, Nicolas Goaziou wrote:
> Michael Brand writes:
>> There is an issue with org-feed. The backtrace is attached. I hope
>> this is enough to reproduce.
>
> Fixed. Here comes the new patch.
>
> Thanks again.
I can confirm that the issue is resolved. Thank y
[posted at Edward's request]
--- Forwarded Message
Date:Thu, 22 Sep 2011 22:36:29 -0400
From:"Edward N. Lewis"
To:
Subject: RE: [O] Bug: File Links [6.33x]
Please disregard my earlier e-mail earlier this evening.
I found a solution for the display issue.
change the line in
/e
Hello,
Michael Brand writes:
> There is an issue with org-feed. The backtrace is attached. I hope
> this is enough to reproduce.
Fixed. Here comes the new patch.
Thanks again.
Regards,
--
Nicolas Goaziou
>From 1f8df0573427f02f0e0553bcfa8bec10ac097188 Mon Sep 17 00:00:00 2001
From: Nicolas G
Hi Eric
Eric Schulte writes:
> Martyn Jago writes:
>
>> Hi Eric
>>
>> Eric Schulte writes:
>>
>>> Hi Martyn,
>>>
>>> I've just pushed up what will hopefully be a more general solution.
>>> Basically, language-specific test files can now signal errors if they
>>> have unmet dependencies. These
Hi Seb,
I could not reproduce the error you describe, and your test case passes
for me. I have added your test case to testing/test-ob.el however so it
should protect from this error in the future.
You could try running the test suite in batch mode (which will not load
your configuration) and se
Martyn Jago writes:
> Hi Eric
>
> Eric Schulte writes:
>
>> Hi Martyn,
>>
>> I've just pushed up what will hopefully be a more general solution.
>> Basically, language-specific test files can now signal errors if they
>> have unmet dependencies. These are then intercepted by `org-test-load'
>>
#+TITLE: Multiple results blocks for the same source code
#+AUTHOR:Seb Vauban
#+DATE: 2011-09-23
#+LANGUAGE: en
* Bug
When evaluating multiple times the following code, we get multiple =results=
blocks.
#+begin_src sh
echo Hello
#+end_src
#+results:
: Hello
#+results:
: Hello
*
Hi Eric
Eric Schulte writes:
> Hi Martyn,
>
> I've just pushed up what will hopefully be a more general solution.
> Basically, language-specific test files can now signal errors if they
> have unmet dependencies. These are then intercepted by `org-test-load'
> and the file is not added to the t
Dear Jan
On Fri, Sep 23, 2011 at 3:51 AM, Jan Böcker wrote:
>
> Hi Jay,
>
> I faced the same problem about a year ago.
> See this thread in the mailing list archive:
>
> http://thread.gmane.org/gmane.emacs.orgmode/24227
>
> The HTML exporter will refuse to include a TOC if body-only is t; the
>
Hi Nicolas
There is an issue with org-feed. The backtrace is attached. I hope
this is enough to reproduce:
1) /tmp/feed.org:
#+begin_src org
,-*- coding: utf-8-unix -*-
,#+DRAWERS: FEEDSTATUS
,* podcast
, :FEEDSTATUS:
, :END:
#+end_src
2) (setq org-feed-alist '((
On 09/21/2011 09:40 PM, G. Jay Kerns wrote:
> In other words, it looks like I am obliged to :body-only t which cuts
> out header/footer/TOC or I can NOT do :body-only t which will give me
> the TOC plus a bunch of extra stuff.
>
> My question: is it possible to do what I want? Is there some sort
20 matches
Mail list logo
