Re: [O] How to specify birthdays?
On Di, Mai 13, 2014 at 05:07:19 +0800, Eric Abrahamsen wrote: > Josef Wolf writes: > Ah, for that you'll want (setq org-agenda-include-diary t). I assume you > don't have that set right now? Yes, it works with this setting. Thanks! I was confused by this paragraph: | If you are using the diary only for sexp entries and holidays, it is faster to | not use the above setting, but instead to copy or even move the entries into | an Org file. Org mode evaluates diary-style sexp entries, and does it faster | because there is no overhead for first creating the diary display. Since I don't want the DIARY-ANNIVERSARY anyway (because of its wired ordering of arguments), I hesitated to use the setting that the documentation suggests not to set =8-() -- Josef Wolf j...@raven.inka.de
Re: [O] How to specify birthdays?
On Di, Mai 13, 2014 at 09:40:56 +0800, Eric Abrahamsen wrote: > Dominic Surano writes: > Deadlines and schedules are generally for things that require an action > on your part, and thus will continue to show up in the agenda as > un-acted-upon if you don't do anything. Usually, for things like > birthdays, you just use a plain timestamp (no scheduled or deadline), > and then you can just see it coming in the usual org agenda. I don't > think there's any other way to give a specific warning about an upcoming > timestamp, though... Yeah, that seems to work better. But still no way for something like "Married %d years ago!" like its shown in the org-anniversary example on orgmode.org/manual/Weekly_002fdaily-agenda.html -- Josef Wolf j...@raven.inka.de
Re: [O] How to specify birthdays?
On Mo, Mai 12, 2014 at 10:22:02 +, Dominic Surano wrote: > Make it a deadline instead of a SCHEDULED item and set it to the current > year with the +1y modifier. That way it will only come up a few days before > it's due. > > * Calendar > ** Birthdays > *** Somebody > DEADLINE: <2014-05-12 Tue +1y> By setting it to the current year, I'd loose track of the original year when the event happened. I _really_ like the idea of "XXX is %d years old", like it is shown in the org-anniversary example! -- Josef Wolf j...@raven.inka.de
[O] How to specify birthdays?
Hello, I am trying to use org-mode for birthdays. I have tried those two entries: * Calendar ** Birthdays *** Somebody SCHEDULED: <1970-05-20 Mo +1y> *** Somebody1 SCHEDULED: %%(org-anniversary 1970 5 20) Somebody1 is %d years old The first entry is shown in the agenda for the current day as: Calendar: Sched.358x: Somebody I find this a bit strange. I want a reminder a couple of days before the event. But I don't want an everday reminder of how days have gone past the last event. The second entry doesn't appear at all in the agenda. Any ideas what I am missing here? -- Josef Wolf j...@raven.inka.de
Re: [O] Problems with org-capture
On Di, Mai 06, 2014 at 11:57:34 +0200, Josef Wolf wrote:
> I am new to org-mode, and am currently working through
> http://members.optusnet.com.au/~charles57/GTD/gtd_workflow.html and am stuck
> a little bit the the caprure mode.
>
> My first question is: org-capture seems to come with a pre-confuigured
> template for a "Todo" stanza. I thought, I'd take a closer look at this
> example to learn from it and as a starting point for my own
> customizations. But DESCRIBE-VARIABLE shows that ORG-CAPTURE-TEMPLATES is set
> to NIL. So, where does this pre-configured "Todo" entry come from?
>
> The I created my own template like this:
>
> (setq org-capture-templates
> '(("t" "Todo" entry (file+headline "/m/s/rep/git/todo/newgtd.org" "Tasks")
> "* TODO %^{Brief Description} %^g%?\n Created: %U\n %i\n %A\n\n"
> :kill-buffer :empty-lines 3)))
>
> With this template, I have two problems:
>
> - The most annoying problem is that it eats up the newlines behind the newly
> created entry. I always keep multiple empty lines between top-level
> headings. But even then, a newly created entry eats up all the newlines and
> even melts the succeeding heading onto the end of the newly created entry.
> I guess, this is not how it is meant to work. How would I define
>
> - The second problem is that when invoked with content fron an active region
> (the %i flag), then the %A flag won't ask me for a link description and the
> %i contents are used as description.
Any ideas on that problem?
--
Josef Wolf
j...@raven.inka.de
[O] Problems with org-capture
Hello everybody,
I am new to org-mode, and am currently working through
http://members.optusnet.com.au/~charles57/GTD/gtd_workflow.html and am stuck
a little bit the the caprure mode.
My first question is: org-capture seems to come with a pre-confuigured
template for a "Todo" stanza. I thought, I'd take a closer look at this
example to learn from it and as a starting point for my own
customizations. But DESCRIBE-VARIABLE shows that ORG-CAPTURE-TEMPLATES is set
to NIL. So, where does this pre-configured "Todo" entry come from?
The I created my own template like this:
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "/m/s/rep/git/todo/newgtd.org" "Tasks")
"* TODO %^{Brief Description} %^g%?\n Created: %U\n %i\n %A\n\n"
:kill-buffer :empty-lines 3)))
With this template, I have two problems:
- The most annoying problem is that it eats up the newlines behind the newly
created entry. I always keep multiple empty lines between top-level
headings. But even then, a newly created entry eats up all the newlines and
even melts the succeeding heading onto the end of the newly created entry.
I guess, this is not how it is meant to work. How would I define
- The second problem is that when invoked with content fron an active region
(the %i flag), then the %A flag won't ask me for a link description and the
%i contents are used as description.
Any ideas what might be wrong here?
--
Josef Wolf
j...@raven.inka.de
