emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Bastien <bastienguerry@googlemail.com>,
	emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Release 6.28
Date: Thu, 25 Jun 2009 17:34:17 +0200	[thread overview]
Message-ID: <77CC7E37-2552-4E0E-B894-2AF3768235F1@gmail.com> (raw)
In-Reply-To: <87r5x8l5t1.fsf@gollum.intra.norang.ca>


On Jun 25, 2009, at 4:57 PM, Bernt Hansen wrote:

> Carsten Dominik <carsten.dominik@gmail.com> 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

  reply	other threads:[~2009-06-25 15:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  7:10 Release 6.28 Carsten Dominik
2009-06-25  7:14 ` Carsten Dominik
2009-06-25 13:05 ` Bastien
2009-06-25 13:19 ` Bastien
2009-06-25 13:58   ` Peter Frings
2009-06-25 16:16     ` Bastien
2009-06-25 17:34     ` Eric S Fraga, Eric S Fraga
2009-06-25 14:24   ` Carsten Dominik
2009-06-25 14:54     ` peter.frings
2009-06-25 14:57     ` Bernt Hansen
2009-06-25 15:34       ` Carsten Dominik [this message]
2009-06-25 16:15     ` Bastien
2009-06-25 19:34       ` Eric S Fraga
2009-06-25 17:00     ` Samuel Wales
2009-06-26  5:18       ` Carsten Dominik
2009-06-26  8:03         ` Carsten Dominik
2009-06-26 10:06           ` peter.frings
2009-06-26 14:05           ` Bernt Hansen
2009-06-26 14:14           ` Bastien
2009-06-26 10:59         ` Eric S Fraga, Eric S Fraga
2009-06-26 13:59           ` Carsten Dominik
2009-06-25 13:59 ` Sebastian Rose
2009-06-25 17:02   ` Eddward DeVilla
2009-06-25 17:10 ` Tom Tobin
2009-06-25 18:38 ` Xin Shi
2009-06-25 20:05 ` Matthew Lundin
2009-07-01  7:20 ` Ulf Stegemann
2009-07-01  9:47   ` Carsten Dominik
2009-07-01 10:26     ` Christian Egli
2009-07-01 11:17       ` Ulf Stegemann
2009-07-02  9:58         ` Carsten Dominik
2009-07-02 11:14           ` Ulf Stegemann
2009-07-02 11:33             ` Carsten Dominik
2009-07-02 21:09       ` Carsten Dominik
2009-07-03 12:32         ` Ulf Stegemann

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=77CC7E37-2552-4E0E-B894-2AF3768235F1@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bastienguerry@googlemail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    /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).