From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Release 6.28 Date: Thu, 25 Jun 2009 17:34:17 +0200 Message-ID: <77CC7E37-2552-4E0E-B894-2AF3768235F1@gmail.com> References: <697A2093-E226-4AD6-B7DE-21A2DA8208A6@gmail.com> <87r5x8fo1u.fsf@bzg.ath.cx> <87r5x8l5t1.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJqy2-0002Bg-IN for emacs-orgmode@gnu.org; Thu, 25 Jun 2009 11:34:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJqxx-00029l-Oz for emacs-orgmode@gnu.org; Thu, 25 Jun 2009 11:34:26 -0400 Received: from [199.232.76.173] (port=46423 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJqxx-00029W-Jo for emacs-orgmode@gnu.org; Thu, 25 Jun 2009 11:34:21 -0400 Received: from mail-ew0-f220.google.com ([209.85.219.220]:62506) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJqxx-0001W1-5J for emacs-orgmode@gnu.org; Thu, 25 Jun 2009 11:34:21 -0400 Received: by ewy20 with SMTP id 20so253721ewy.42 for ; Thu, 25 Jun 2009 08:34:20 -0700 (PDT) In-Reply-To: <87r5x8l5t1.fsf@gollum.intra.norang.ca> 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: Bernt Hansen Cc: Bastien , emacs-orgmode Mailinglist On Jun 25, 2009, at 4:57 PM, Bernt Hansen wrote: > Carsten Dominik writes: > >> With `d' and `w' in place, `m' and `y' are consistent, logical. >> However, I don't believe anyone uses monthly views, I am sure >> that no-one uses yearly views, right? So I will negotiate over >> `m', i someone can propose a viable alternative that makes sense. > > I use monthly view... monthly :) To get my clock report usage for the > file over the past month. I restrict the agenda to the single file > when > doing this monthly view to get clock time just for this project and > that > could possibly be done with a dynamic block. > > I've been enjoying not having my generated clock reports in my git > history though and the agenda monthly view is perfect for that. Nobody is talking about abandoning monthly view - only about putting it on a different key. - Carsten