--text follows this line--
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.
Bastien writes:
Hi Bastien,
> The patch looks good but I'd like to understand it better.
> Can you send an example configuration working with your patch?
In org-publish-project-alist, i have HTML publishing projects which
should be published to different target directories depending on e.g.
whe
Bastien writes:
Hi Bastien,
> The patch looks good but I'd like to understand it better.
> Can you send an example configuration working with your patch?
In org-publish-project-alist, i have HTML publishing projects which
should be published to different target directories depending on e.g.
whe
I'm using an org-mode publishing project in different locations and
would like to set different (location dependent) values for the
publishing-directory property (e.g. use different servers to upload
published files).
There might be a way to do that with the current org-mode which i just
did not
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.
-
At Wed, 28 Oct 2009 17:55:44 +0100,
Hi Carsten,
> >
> > Some days ago i noticed that time shifting in CLOCK lines stopped
> > working.
> > I've now toggled some org config variables and found that this
> > happens when
> > org-replace-disputed-keys is set to t. This was not the case with
> >
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.
-
Carsten Dominik wrote:
> Hi Kai,
>
>
> On Oct 23, 2009, at 9:01 AM, Kai Tetzlaff wrote:
>
>> Hi,
>>
>> i noticed that when using the org-mode clock persistence, the stored
>> clock data gets deleted when i start emacs and exit again without
>> turni
Carsten Dominik wrote:
> Hi Kai,
>
>
> On Oct 23, 2009, at 9:01 AM, Kai Tetzlaff wrote:
>
>> Hi,
>>
>> i noticed that when using the org-mode clock persistence, the stored
>> clock data gets deleted when i start emacs and exit again without
>> turni
Carsten Dominik wrote:
>
> On Oct 23, 2009, at 10:20 AM, Kai Tetzlaff wrote:
>
>> John Wiegley wrote:
>>> On Oct 22, 2009, at 6:32 PM, Kai Tetzlaff wrote:
>>>
>>>> 'Cannot restart clock because task does not contain unfinished clock'
&g
John Wiegley wrote:
> On Oct 22, 2009, at 6:32 PM, Kai Tetzlaff wrote:
>
>> 'Cannot restart clock because task does not contain unfinished clock'
>>
>> When i look at the corresponding clock line the previously running clock
>> has now indeed been stopped
Hi,
i noticed that when using the org-mode clock persistence, the stored
clock data gets deleted when i start emacs and exit again without
turning on org-mode in between.
When looking at org-clock-persistence-insinuate it looks like org-clock
load will only run after org-mode gets started whereas
Hi,
since the new resolve 'away time' feature has been integrated i'm having
problems when restarting emacs after exiting with a running clock. When
i'm starting org-mode after the emacs restart by entering agenda mode i
get the new prompt which is asking about how to deal with the unresolved
cloc
13 matches
Mail list logo