From: Samuel Loury <konubinix@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>, emacs-orgmode@gnu.org
Subject: Re: Collaborating with TODO lists and clocks.
Date: Thu, 05 Sep 2013 10:52:09 +0200 [thread overview]
Message-ID: <874n9zwszq.fsf@konixwork.incubateur.ens-lyon.fr> (raw)
In-Reply-To: <8638pjiujv.fsf@somewhere.org>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Sebastien Vauban <sva-news@mygooglest.com> writes:
> Having thought about that in the past, I had thought of adding "tags" after
> clock lines, such as:
>
> --8<---------------cut here---------------start------------->8---
> CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] => 0:51 :userA:
> CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] => 0:36 :devB:
> --8<---------------cut here---------------end--------------->8---
That sounds good also.
> Though, having separate CLOCK drawers would even be better for Git merges,
> such as (keeping the idea of pseudo-tags):
>
> --8<---------------cut here---------------start------------->8---
> :CLOCK:userA:
> CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] => 0:51
> CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] => 0:36
> :END:
> :CLOCK:devB:
> CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] => 1:03
> :END:
> --8<---------------cut here---------------end--------------->8---
I really like this solution.
> But, of course, a lot of development is required to make this become usable:
>
> - clocking reports (`R') must be updated with the knowledge of the current
> user
>
> - clock checking functions (`v c') must be enhanced to ignore clocks from
> other users
>
> - etc.
That is my point with the solution by customization of
org-clock-string. It appears to need only a few corrections of the hard
coded "CLOCK:" string (that would be required anyway) and it looks like
it would work out of the box without further development. Wouldn't it?
--
Konubinix
GPG Key : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-09-05 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 18:30 Collaborating with TODO lists and clocks Gareth Smith
2013-04-28 19:27 ` Richard Lawrence
2013-04-29 20:34 ` Gareth Smith
2013-04-30 1:50 ` Richard Lawrence
2013-04-30 18:21 ` Gareth Smith
2013-09-05 7:31 ` Samuel Loury
2013-09-05 7:42 ` Sebastien Vauban
2013-09-05 8:52 ` Samuel Loury [this message]
2013-09-05 11:22 ` Sebastien Vauban
2013-09-05 11:54 ` Thorsten Jolitz
2013-09-05 13:32 ` Samuel Loury
2013-09-05 13:29 ` Samuel Loury
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=874n9zwszq.fsf@konixwork.incubateur.ens-lyon.fr \
--to=konubinix@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.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).