From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org-mode collaborative (multiple users working on the same set of files)
Date: Tue, 22 Jun 2010 17:04:31 +0200 [thread overview]
Message-ID: <87631bt8g0.fsf@mundaneum.com> (raw)
In-Reply-To: 87631mxbch.fsf_-_@mundaneum.com
Hi all,
> Regarding the clocked times:
>
>>> I just read this and before nobody answers, I'll give you a small POC that
>>> should work for you. As far as I can tell it doesn't break anything.
>>>
>>> (defun org-clock-out-mark-clock ()
>>> (unless remove (insert (format " (%s)" user-full-name))))
>>>
>>> (add-hook 'org-clock-out-hook 'org-clock-out-mark-clock)
>
> Yep, this seems to work perfectly -- did not catch any conflict yet, but
> usage time still low.
>
> Example results:
>
> * My sub-project
> :LOGBOOK:
> CLOCK: [2010-06-14 Mon 09:15]--[2010-06-14 Mon 10:11] => 0:56 (Sebastien Vauban)
> - Test.
> :END:
>
> Your proposed format seems nice to me.
Thinking a bit more about this, I would imagine a "tag"-like format would even
be more aligned with the rest, moreover if we could get a filtering function
(thus, based on tags):
--8<---------------cut here---------------start------------->8---
* My sub-project
:LOGBOOK:
CLOCK: [2010-06-14 Mon 09:15]--[2010-06-14 Mon 10:10] => 0:55 :svauban:
- Introduction.
CLOCK: [2010-06-17 Thu 11:55]--[2010-06-17 Thu 14:40] => 2:45 :eschulte:
- First essay.
CLOCK: [2010-06-18 Fri 12:10]--[2010-06-18 Fri 13:20] => 1:10 :svauban:
- Brainstorming.
:END:
--8<---------------cut here---------------end--------------->8---
Of course, when using tags, that would imply that identifiers don't contain
spaces, if I'm not misspeaking.
>> [...] I have been using org-mode files as a point of collaboration on a
>> couple of projects (including org-babel [1]) and I think a generalization
>> of something like your proposed `org-user-identifier' variable could be
>> very useful for many of the org meta-data items associated with headlines.
>>
>> For example, it would be great to record the user responsible for every
>> TODO state change, so that something like
>>
>> ** DONE Org-babel should work well when indented
>> - State "DONE" from "TODO" [2010-06-10 Thu 15:48]
>>
>> would instead be
>>
>> ** DONE Org-babel should work well when indented
>> - State "DONE" from "TODO" by eschulte [2010-06-10 Thu 15:48]
>
> That'd be great. I now dream of the ability to get a "revision history" to
> be easily inserted at the begin of a document, like all pros do.
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-06-22 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 18:45 simultaneous clocks? Erik Iverson
2010-06-09 18:53 ` Erik L. Arneson
2010-06-09 19:36 ` brian powell
2010-06-10 0:27 ` Bernt Hansen
2010-06-10 0:35 ` Erik Iverson
2010-06-10 0:37 ` Bernt Hansen
2010-06-10 3:50 ` Bernt Hansen
2010-06-10 7:41 ` Debate about "One clock per user, but user is identified" Sébastien Vauban
2010-06-12 15:23 ` Benjamin Andresen
2010-06-12 17:07 ` org-remember and anything Glauber Alex Dias Prado
2010-06-12 17:09 ` Bernt Hansen
2010-06-12 17:44 ` Glauber Alex Dias Prado
2010-06-12 17:33 ` Thierry Volpiatto
2010-06-14 12:21 ` Glauber Alex Dias Prado
2010-06-14 20:21 ` Thierry Volpiatto
2010-06-14 13:38 ` Glauber Alex Dias Prado
2010-06-25 21:06 ` rubikitch
2010-06-12 16:34 ` Debate about "One clock per user, but user is identified" Eric Schulte
2010-06-12 16:48 ` Daniel Martins
2010-06-14 8:33 ` Org-mode collaborative (multiple users working on the same set of files) Sébastien Vauban
2010-06-22 15:04 ` Sébastien Vauban [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87631bt8g0.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.