From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Feature request: Periodic events based on count of specific weekdays (was: Monthly events based on count of specific weekdays) Date: Fri, 20 Nov 2009 08:37:29 +0100 Message-ID: <77D21500-F2A5-45AA-9490-660C4AA7EF07@gmail.com> References: <87ws214lpo.fsf@benfinney.id.au> <87fx8p434f.fsf@benfinney.id.au> <87bpjc4u4i.fsf@benfinney.id.au> <87vdh6gmpc.fsf_-_@benfinney.id.au> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBPKD-0005zv-C0 for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 03:58:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBPK8-0005vo-IZ for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 03:58:40 -0500 Received: from [199.232.76.173] (port=58813 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBPK8-0005vl-EZ for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 03:58:36 -0500 Received: from mail-fx0-f225.google.com ([209.85.220.225]:60290) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBPK8-0005x3-0F for emacs-orgmode@gnu.org; Fri, 20 Nov 2009 03:58:36 -0500 Received: by mail-fx0-f225.google.com with SMTP id 25so3573542fxm.26 for ; Fri, 20 Nov 2009 00:58:35 -0800 (PST) In-Reply-To: <87vdh6gmpc.fsf_-_@benfinney.id.au> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Ben Finney Cc: emacs-orgmode@gnu.org Hi Ben, extending the date format would be a significant amount of work. The current time/date format is already complex to handle internally, mainly because it was build not with a clean design but step by step. o I am hesitating to add something like you propose. My feeling is that date specifications like this are seldomly used, and as far as readability is concerned, for these few events you could just (as suggested by Matt) write a note explaining what the entry does. Sorry. - Carsten On Nov 19, 2009, at 11:43 PM, Ben Finney wrote: > Ben Finney writes: > >> [=85] =93second Tuesday of the month=94 isn't niche, it is pretty = common, I >> would have thought. > > [=85] > >>> You'd have to ask Carsten to implement a new timestamp syntax. What >>> would you propose as a more readable designation? > > How about a keyword that specifies the type of repeat being requested: > > <2009-10-13 Tue 14:00 +1m dow> > Repeat each month, on the second Tuesday of the month. Calculated > because this date is the second Tuesday of the month, and =93dow=94 = is > the specified repeat type. > > <2009-10-13 Tue 14:00 +1m dom> > Repeat each month, on the 13th day of the month. Calculated because > this date is the 13th of the month, and =93dom=94 is the specified > repeat type. > > <2009-10-13 Tue 14:00 +1m> > Repeat each month, on the 13th day of the month. Calculated because > this date is the 13th of the month, and =93dom=94 is the default = repeat > type. > > This allows existing behaviour to be continued (=93repeat on the same =20= > day > of the month=94), preserves the default behaviour, and allows for = other > repeat types to be added later without breaking existing timestamp =20 > data. > > --=20 > \ =93He who laughs last, thinks slowest.=94 =97=20 > anonymous | > `=20 > \ | > _o__=20 > ) | > Ben Finney > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten