From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Loury Subject: Re: Collaborating with TODO lists and clocks. Date: Thu, 05 Sep 2013 10:52:09 +0200 Message-ID: <874n9zwszq.fsf@konixwork.incubateur.ens-lyon.fr> References: <87li82se2b.fsf@totherme.org> <87obcybgmc.fsf@berkeley.edu> <87txmpoz34.fsf@doc.ic.ac.uk> <87vc743hyw.fsf@berkeley.edu> <877gevwwq5.fsf@konixwork.incubateur.ens-lyon.fr> <8638pjiujv.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38717) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHVId-0003e9-RW for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 04:52:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VHVIY-0000c8-1F for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 04:52:23 -0400 Received: from mail-wi0-x22e.google.com ([2a00:1450:400c:c05::22e]:58267) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHVIX-0000c3-Pk for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 04:52:17 -0400 Received: by mail-wi0-f174.google.com with SMTP id hj3so4585869wib.7 for ; Thu, 05 Sep 2013 01:52:16 -0700 (PDT) In-Reply-To: <8638pjiujv.fsf@somewhere.org> 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: Sebastien Vauban , emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Sebastien Vauban writes: > Having thought about that in the past, I had thought of adding "tags" aft= er > clock lines, such as: > > --8<---------------cut here---------------start------------->8--- > CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] =3D> 0:51 :us= erA: > CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] =3D> 0:36 :de= vB: > --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] =3D> 0:51 > CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] =3D> 0:36 > :END: > :CLOCK:devB: > CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] =3D> 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 usab= le: > > - 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? =2D-=20 Konubinix GPG Key : 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBAgAGBQJSKEY5AAoJEHXSPO10ORBqXIQIAIYtnN4TC3WbMIZX1R9/MVr/ LrPhxJ6WJILeKhe5Lwsl7jfg9gau/qh+KV5PGChyvuoRn/IXZKwMYhiJrow/QzPd gy9QRHYb5a7bmetLlZ9RserC5wuI/APLVM5w5xPM3IX0s/yB+pfBao+j2aDlVLiF zbPBWifaUauq2xbT+vObuDCDXQ+IxXeIRCsOdazAjxggjSpNCu0uDFzVOnze+8Tk CPv+9huvwrOkvRmATZyzuHkGn81BGPGrf7ZD0IH0DYVJmsC+LDxTvRITcqmFxqHh zID11KP6XwtLOdP+A37wQufBXwYtxscADod+QEzlLXr21n2J0QjxXuhhng5M9vE= =518J -----END PGP SIGNATURE----- --=-=-=--