From: Bastien <bzg@altern.org>
To: Peder Stray <peder.stray@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Patch to get clocktable to split on week boundraries
Date: Fri, 15 Mar 2013 11:50:11 +0100 [thread overview]
Message-ID: <87ip4tj5ss.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAE4U0JGxbaF4e=MDPeRA-5=49bsz4_z-e=noqEZ2Sem6e5CJ3g@mail.gmail.com> (Peder Stray's message of "Mon, 4 Mar 2013 15:44:24 +0100")
Hi Peder,
Peder Stray <peder.stray@gmail.com> writes:
> When calling clocktable with :block *month and :step week it splits
> into block 7 days long starting from the first day in the month...
> that's not very useful I think, so here is a patch making it split
> the month into weeks starting on mondays. The first and last week
> will be clipped to only include the days in the selected month and as
> such will not contain the full 7 days of those weeks.
thanks for this idea and for the patch. I just pushed a different
implementation, allowing a new :mstart parameter for clocktables,
similar to the already existing :wstart parameter.
The default for :wstart (the week starting day) is 1, for monday.
The default for :mstart (the month starting day) is 1, for the first
day of the month.
So the new default for e.g.,
#+BEGIN: clocktable :block month :step week
#+END
is to start on the 1st of the month (ignoring :wstart) and to continue
with weeks starting on mondays.
If you use
#+BEGIN: clocktable :block month :step week :wstart 2 :mstart 3
#+END
it will start the report on the 3rd of the month, and continue the
weekly steps starting from tuesdays.
Thanks for this idea and for the patch!
--
Bastien
prev parent reply other threads:[~2013-03-15 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 14:44 Patch to get clocktable to split on week boundraries Peder Stray
2013-03-15 10:50 ` Bastien [this message]
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=87ip4tj5ss.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=peder.stray@gmail.com \
/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).