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 09:31:30 +0200 Message-ID: <877gevwwq5.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> 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]:50734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHU2c-0000Vy-K6 for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 03:31:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VHU2V-0002Ge-VI for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 03:31:46 -0400 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:64950) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHU2V-0002GM-KF for emacs-orgmode@gnu.org; Thu, 05 Sep 2013 03:31:39 -0400 Received: by mail-wi0-f177.google.com with SMTP id cb5so1438690wib.10 for ; Thu, 05 Sep 2013 00:31:38 -0700 (PDT) In-Reply-To: <87vc743hyw.fsf@berkeley.edu> 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: Richard Lawrence , emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Richard Lawrence writes: > Hi Gareth, > > Gareth Smith writes: > >> I hadn't thought of using :tags on a clock table. I still worry if we'll >> find ourselves in a situation where more than one of us has clocked in >> some time on the same task. > > Yes, I agree this might not be optimal, for that case in particular. > One nice thing about this use of tags is that you have a representation > of when more than one person is working on a task, but that makes the > clock less useful, as it can no longer represent an individual's working > time without some effort to separate the clocks of the different owners. I recently encountered the issues of having to collaborate with other persons on the same task (all of us would need at some point to clock into this task). I thought that changing the value of the variable org-clock-string could help, but I have not tried it yet. Let me explain why it could help: It is for the time being set to "CLOCK:", but imagine that the user A set it to "CLOCK-A:" and the user B set it to "CLOCK-B:" (in their respective .emacs files), then after some time a clocked task would then look like: =2D-8<---------------cut here---------------start------------->8--- * Do something CLOCK-A: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] =3D> 0:51 CLOCK-A: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] =3D> 0:36 CLOCK-B: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] =3D> 1:03 =2D-8<---------------cut here---------------end--------------->8--- Then the agenda for each user would report only the time spent by himself. The time spent by each participant is clearly separated. There are some problems with doing so: =2D I don't know yet how to configure a report showing the time spent by every body, =2D I am not sure the clock time sum would work. =2D grepping for "CLOCK:" on org sources shows: --8<---------------cut here---------------start------------->8--- ./lisp/org-clock.el:782: (while (re-search-forward "CLOCK: \\(\\[.*?\\]\= \)$" nil t) ./lisp/org.el:851: (defcustom org-clock-string "CLOCK:" ./lisp/org.el:8501: (while (re-search-forward "^[ \t]*CLOCK:.*$" n= il t) ./lisp/org.el:15007: (defconst org-clock-drawer-start-re "^[ \t]*:CLOCK:[= \t]*$" ./lisp/org.el:15578: (while (looking-at "^[ \t]*\\(:CLOCK:\\|:LOGBOOK= :\\|CLOCK:\\|:END:\\)") ./lisp/org.el:15579: (if (member (match-string 1) '("CLOCK:" ":END:= ")) ./lisp/org.el:17278: (looking-at "^[ \t]*CLOCK:"))) --8<---------------cut here---------------end--------------->8--- Those look like "hard coded" "CLOCK:" instead of using org-clock-string. They would need to be fixed. What do you think of this solution? Has anyone already use a solution like this? Best, PS: I have tried changing the org-clock-into-drawer variable to be "CLOCK-A" and "CLOCK-B" so that the task would then look like=20 =2D-8<---------------cut here---------------start------------->8--- * Do something :CLOCK-A: 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-B: CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] =3D> 1:03 :END: =2D-8<---------------cut here---------------end--------------->8--- But it needs org-drawers to contain the values for each collaborators for it to work (and then should be maintained) and the folding mechanism did not seem to work for those special drawers. =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) iQEcBAEBAgAGBQJSKDNSAAoJEHXSPO10ORBqeUMIAJhvv5sQ0EBJkFGbx/VJnppu 0DmYnZNi8rA4Llh+WzmaEHoLchTZq6CyUDgwCnoVdcZeQVzZ4vazCfxazz+3Ifaz XVtffwV4RStCR5Tb7XJlxAMbqlg9lDtoZRvch+F1nCsu3ZgQpvX2eY1BJYuBPz1J j7TVnuP4Qf4nsHrRJhymRv3oAXiM5uF0Tf9E57YwBZGc56sS1sKH+x7acuZpMxjz WQ79sb5/zKyw+YF+4FVjh58LuRzF5hG81p883Cr9iaVrmVPmrUuWaBUSxFp26p/O IrheTQ27Kq0yNcgk7FrgQIfZbssQhMPKHsEcOsvloSGqQAf7+L0oRcHRacL+xGU= =n2nX -----END PGP SIGNATURE----- --=-=-=--