From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Arntson Subject: Re: beginner agenda question Date: Mon, 28 Jul 2014 10:01:10 -0700 Message-ID: <87mwbtxvs9.fsf@stevenarntson.com> References: <87r416xoqg.fsf@stevenarntson.com> <87ppgqi65h.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XBoIm-0004QJ-AJ for emacs-orgmode@gnu.org; Mon, 28 Jul 2014 13:01:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XBoIg-0006DL-9w for emacs-orgmode@gnu.org; Mon, 28 Jul 2014 13:01:32 -0400 Received: from plane.gmane.org ([80.91.229.3]:60806) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XBoIg-0006D3-3R for emacs-orgmode@gnu.org; Mon, 28 Jul 2014 13:01:26 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XBoId-0008Gl-Ia for emacs-orgmode@gnu.org; Mon, 28 Jul 2014 19:01:23 +0200 Received: from 97-113-62-203.tukw.qwest.net ([97.113.62.203]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Jul 2014 19:01:23 +0200 Received: from steven by 97-113-62-203.tukw.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Jul 2014 19:01:23 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eric Abrahamsen writes: > Steven Arntson writes: > >> Simple question, I think, but it has me stumped. I'm wondering what >> variable controls the org-agenda function that gives you upcoming >> events, a la: >> >> todo: In 2 d.: TODO Friend's Birthday >> todo: In 4 d.: TODO Rehearsal >> todo: In 4 d.: TODO Happy Hour >> todo: In 9 d.: TODO Some other thing >> >> I'd like to get rid of all of that > > It looks like you've put a DEADLINE cookie on those events -- the > advance warning only kicks in in that case, if I recall correctly. For > plain old events (birthdays, doctors appointments, etc), it's often best > just to use a regular old timestamp, so: > > * Rehearsal <2014-07-28 Mon> > > Or you can put the timestamp on the line below the headline. > > HTH, > Eric Eric, thank you, yes, that did it. Best! steven