From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Yearly repeats on the agenda Date: Tue, 17 Apr 2012 09:10:24 -0400 Message-ID: <2536.1334668224@alphaville> References: <1890.1334665342@alphaville> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34354) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SK8B2-0006M6-Sv for emacs-orgmode@gnu.org; Tue, 17 Apr 2012 09:10:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SK8Aw-0003kx-JT for emacs-orgmode@gnu.org; Tue, 17 Apr 2012 09:10:36 -0400 Received: from g6t0185.atlanta.hp.com ([15.193.32.62]:47096) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SK8Aw-0003km-E3 for emacs-orgmode@gnu.org; Tue, 17 Apr 2012 09:10:30 -0400 In-Reply-To: Message from SW of "Tue, 17 Apr 2012 12:40:37 -0000." 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: SW Cc: emacs-orgmode@gnu.org SW wrote: > Nick Dokos hp.com> writes: > > > Indeed - I can reproduce that. It happens in org-agenda-get-timestamps, > > in the call to org-agenda-format-item: this function takes a regexp > > argument, remove-re, and removes any matches from the string it > > produces. The regexp is constructed from the *current* date though: > > > > (concat > > (regexp-quote > > (format-time-string > > "<%Y-%m-%d" > > (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date)))) > > ".*?>") > > > > so it becomes "<2012-04-17.*?>". Hence it removes the date in the third > > example above, but not in the other two. > > > > The question is whether this is intended or not: personally, I don't see > > any reason for the difference in behavior, so it might be a good idea to > > generalize the regexp to match *any* year. > > BTW, this should be "*any* date": monthly, daily, weekly repeaters would exhibit the same behavior. > > Nick > > Thanks for the reply. Do I need to file this as a bug, or does this thread > constitute a bug report? I'll let the maintainers decide a) whether it's a bug and b) whether a formal bug report is needed. > I'm behind a firewall/proxy and haven't setup email in > Emacs, so I would just copy and paste the message from org-submit-bug-report and > email it? I'm not (yet) an elisp-er, so I can't fix this myself. > Yes, that would be the procedure. Nick