Hi John,
I have a doubt regarding a specific habit definition I'd like to create - A
GTD Weekly review. I want this habit to "happen" every friday, weekly. But
if this friday passes, then, I want org-habit to consider it overdue. I've
tried the following def:
** TODO GTD Weekly Review
SCHEDULE
Hello list,
I have an org file with some items that act as events (org-agenda-to-appt),
and use gnome-osd to show them in the screen when they "happen". However, I
don't want them to clutter my current's day agenda view. Is there a way to
filter them from the current day agenda view?
Thanks,
Mar
Water Lin writes:
> I use org mode as my homepage and I use tags to distinguish my content
> such as finished, on-hold and suspended.
>
> But when I publish my org files into web pages, I don't want to publish
> the content which isn't finished. That's mean I just want to publish
> content of spe
I use org mode as my homepage and I use tags to distinguish my content
such as finished, on-hold and suspended.
But when I publish my org files into web pages, I don't want to publish
the content which isn't finished. That's mean I just want to publish
content of specific tags. How can I do it?
T
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 (with a time stamp corresponding to the
current time).
This is an inte
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
Hi Jerry,
I do this using org-babel. I love being able to write my article
*and* my beamer presentation in the same file. Using the literate
programming facility of org-babel, I'm able to write them each in
pieces, then assemble them at the end for tangling and export. This
means I hav
On Oct 22, 2009, at 11:52 PM, Matthew Lundin wrote:
Carsten Dominik writes:
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
Bernt Hansen writes:
"Tim O'Callaghan" writes:
Can you use the #+BIND: keyword to set arbitrary variables and
achieve
the same result?
If I understand it corr
Carsten Dominik writes:
> On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
>
>> Bernt Hansen writes:
>>
>>> "Tim O'Callaghan" writes:
>>>
>>> Can you use the #+BIND: keyword to set arbitrary variables and
>>> achieve
>>> the same result?
>>
>> If I understand it correctly, #+BIND only works for
2009/10/22 Carsten Dominik :
>
> On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
>
>> Bernt Hansen writes:
>>
>>> "Tim O'Callaghan" writes:
>>>
Expand the #+ in-org file configuration possibilities with
a #+CONFIG or similar keyword.
The idea being to abstract more configurat
Hi,
A question about exporting:
Is it possible to export two different subtrees in the same file to a
different class? There are cases where it would be nice to be able to
generate a document (say an article) from a single subtree in a file, and
have other subtrees that contain short presentatio
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
Bernt Hansen writes:
"Tim O'Callaghan" writes:
Expand the #+ in-org file configuration possibilities with
a #+CONFIG or similar keyword.
The idea being to abstract more configuration into actual org files,
and let extensions have an easy w
Bernt Hansen writes:
> "Tim O'Callaghan" writes:
>
>> Expand the #+ in-org file configuration possibilities with
>> a #+CONFIG or similar keyword.
>>
>> The idea being to abstract more configuration into actual org files,
>> and let extensions have an easy way to use #+KEYWORD configuration. I
"Tim O'Callaghan" writes:
> Simply,
>
> Expand the #+ in-org file configuration possibilities with
> a #+CONFIG or similar keyword.
>
> The idea being to abstract more configuration into actual org files,
> and let extensions have an easy way to use #+KEYWORD configuration. I
> expect it could a
Simply,
Expand the #+ in-org file configuration possibilities with
a #+CONFIG or similar keyword.
The idea being to abstract more configuration into actual org files,
and let extensions have an easy way to use #+KEYWORD configuration. I
expect it could also be used to auto-load suitably register
Darlan Cavalcante Moreira writes:
> Hi Eric,
>
> My comments are also inline
>
> At Wed, 21 Oct 2009 09:11:50 -0600,
> Eric Schulte wrote:
[...]
>> what behavior would you suggest results from a :hide header argument?
>
> My suggestion is that if a source block has the :hide header argument it
Matthieu Lemerre writes:
> There is a bug in org-toggle-fixed-width-section in the org version
> shipped with emacs23: this function only inserts ":", when this colon
> should be followed by a space.
>
> I joined a patch for your convenience; it seems to work. Maybe this has
> already been fixed
Matthieu Lemerre writes:
> Hi
>
> There is a bug in org-toggle-fixed-width-section in the org version
> shipped with emacs23: this function only inserts ":", when this colon
> should be followed by a space.
>
> I joined a patch for your convenience; it seems to work. Maybe this has
> already been
Hi
There is a bug in org-toggle-fixed-width-section in the org version
shipped with emacs23: this function only inserts ":", when this colon
should be followed by a space.
I joined a patch for your convenience; it seems to work. Maybe this has
already been fixed in later versions.
Regards,
Matt
Applied, thanks.
- Carsten
On Oct 22, 2009, at 1:47 AM, Andreas Burtzlaff wrote:
Here's a clean rewrite of org-registry-assoc-all and
org-registry-find-all that also fixes a small bug:
---
diff --git a/contrib/ChangeLog b/contrib/ChangeLog
index 8524c9f..313fc74 100644
--- a/contrib/ChangeLo
OK, thanks for checking.
- Carsten
On Oct 22, 2009, at 12:22 PM, James TD Smith wrote:
Hi Carsten,
On 2009-10-22 07:38:04(+0200), Carsten Dominik wrote:
On Oct 21, 2009, at 11:52 AM, James TD Smith wrote:
I found the changes John Wiegley made to org-repeat-re stopped it
from
matching re
Applied, thanks.
- Carsten
On Oct 21, 2009, at 11:52 AM, James TD Smith wrote:
This needs a small C program (in UTILITIES/x11idle.c) to work.
---
.gitignore |1 +
ChangeLog |6 +-
UTILITIES/x11idle.c | 21 +
lisp/ChangeLog |8 +++-
Hi Michael,
What about just creating a single day view? Like
(setq org-agenda-custom-commands
'(("d" "Due today" agenda ""
((org-deadline-warning-days 0)
(org-agenda-skip-scheduled-if-deadline-is-shown t)
(org-agenda-ndays 1)
(org-agenda-skip-function
On Oct 22, 2009, at 6:17 AM, Mikael Fornius wrote:
I have tracked down the problem (calling time-less-p on nil when
done-dates is empty) and the following patch is solving the issue
for me
but I am not sure if this is how you intended it.
Your fix is correct, I've submitted a patch.
John
Hi Carsten,
On 2009-10-22 07:38:04(+0200), Carsten Dominik wrote:
>
> On Oct 21, 2009, at 11:52 AM, James TD Smith wrote:
>
> > I found the changes John Wiegley made to org-repeat-re stopped it from
> > matching repeaters with just a '+' at the start. I have fixed this.
>
> Hi James, can you pleas
Thanks for org-habit, it is a very nice feature!
When the last DONE date is earlier than `org-habit-preceding-days' the
graph can not be rendered due to error in org-habit-build-graph.
I have tracked down the problem (calling time-less-p on nil when
done-dates is empty) and the following patch i
On Oct 22, 2009, at 10:37 AM, Julien Barnier wrote:
Hi,
I'm trying to use the :preparation-function argument for project
publishing. What I'd like to achieve i s to load a file in order to
define some styling elements for the export process, something such
as :
(load "org-style")
I tried se
Hi,
> I'm trying to use the :preparation-function argument for project
> publishing. What I'd like to achieve i s to load a file in order to
> define some styling elements for the export process, something such
> as :
>
> (load "org-style")
>
> I tried several different syntaxes, such as :
>
> :p
28 matches
Mail list logo
