From: Nick Dokos <nicholas.dokos@hp.com>
To: Brian van den Broek <brian.van.den.broek@gmail.com>
Cc: emacs-orgmode@gnu.org, SW <sabrewolfy@gmail.com>
Subject: Re: Yearly repeats on the agenda
Date: Tue, 17 Apr 2012 10:28:57 -0400 [thread overview]
Message-ID: <3423.1334672937@alphaville> (raw)
In-Reply-To: Message from Brian van den Broek <brian.van.den.broek@gmail.com> of "Tue, 17 Apr 2012 16:00:33 +0200." <CAF6DajJTnonRu4OzuvAdMFbvfdPAJN-cPdO+y63z18MScpQQ3g@mail.gmail.com>
Brian van den Broek <brian.van.den.broek@gmail.com> wrote:
> On 17 April 2012 15:11, SW <sabrewolfy@gmail.com> wrote:
> > SW <sabrewolfy <at> gmail.com> writes:
> >
> >> > > 2) I just added a bunch of holidays / days of observation to my system.
> >> Your use case is better accomplished via org-anniversary:
> >> > >
> >> > > (org-anniversary 2011 01 01) New Year's Day
> >> > Emailing before first coffee is a bad idea. I left out some syntax. See
> >> http://orgmode.org/manual/Weekly_002fdaily-agenda.html.
> >
> >> Thanks, didn't know about those, but that's exactly what I need. There is *so*
> >> much to org-mode and always another section to the manual ... :)
> >
> > FWIF 1: Anniversaries in the agenda don't have tags now. The tag I provided
> > appears in the headline only and does not appear in the agenda. Adding :TAG:
> > didn't solve this.
> >
> > FWIW 2: The CATEGORY example included in the link above resulted in the category
> > appearing next to some other entries in the agenda as well. Replacing it with
> > :CATEGORY: instead of #+CATEGORY: solved this.
>
> I've not tagged any of my holidays and days of observance.
>
> The #+CATEGORY issue will arise in other regards as well. It was a
> first pass at changing categories within an org file before the
> general category property mechanism was included. I don't recall if
> "#+CATEGORY" has been deprecated, but I've treated it as such and been
> much happier than when I was struggling with it.
I'm still stuck in the past, using #+CATEGORY: instead of properties,
but fwiw I haven't had any problem. Like Brian, I'm not tagging these
things.
Nick
next prev parent reply other threads:[~2012-04-17 14:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 20:40 Yearly repeats on the agenda SW
2012-04-16 23:24 ` Nick Dokos
2012-04-17 0:52 ` Samuel Wales
2012-04-17 7:16 ` SW
2012-04-17 7:21 ` SW
2012-04-17 7:39 ` Brian van den Broek
2012-04-17 7:44 ` Brian van den Broek
2012-04-17 12:46 ` SW
2012-04-17 13:11 ` SW
2012-04-17 14:00 ` Brian van den Broek
2012-04-17 14:28 ` Nick Dokos [this message]
2012-04-17 10:28 ` SW
2012-04-17 10:39 ` SW
2012-04-17 12:22 ` Nick Dokos
2012-04-17 12:40 ` SW
2012-04-17 13:10 ` Nick Dokos
2012-04-20 12:46 ` Bastien
2012-04-20 12:57 ` SW
2012-04-20 13:17 ` Nick Dokos
2012-04-20 23:52 ` Samuel Wales
2012-05-08 14:10 ` Bastien
2012-05-08 16:50 ` Nicolas Richard
2012-05-10 6:38 ` Bastien
2012-05-10 8:57 ` Nicolas Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3423.1334672937@alphaville \
--to=nicholas.dokos@hp.com \
--cc=brian.van.den.broek@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sabrewolfy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).