emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Frings <peter.frings@agfa.com>
To: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Re: A simpler remember architecture (was: Re: Re: is there a hook to save a remember buffer?)
Date: Thu, 1 Oct 2009 12:26:02 +0200	[thread overview]
Message-ID: <B3EB5713-BAF2-4F79-934F-73E7AFAD9723@agfa.com> (raw)
In-Reply-To: <4AC472F7.4020208@online.de>

On 01 Oct 2009, at 11:14, Rainer Stengele wrote:

> Jean-Marie Gaillourdet schrieb:
>> Hi,
>> while we are discussing a new org-remember facility. I've been  
>> missing
>> an option to clock the time I've taken to write down my remember  
>> note.
>> E.g. I use remember to make a small protocoll of a telephone call or
>> some discussion with a colleague. It would help me alot to if that
>> time would be clocked automatically. After the remember note is  
>> finalized the previous cloked in task
>> should become active again. Perhaps with some kind of optional
>> message/popup/whatever to say: Well, you were doing this before, I
>> clocked you in again.

> exactly what I am doing quite often!
> Being interrupted (telephone, colleague bringing more work ...)  
> while working on an clocked in TODO I pop up a remember buffer,  
> manually clock in, discuss/write down my stuff, save the remember  
> buffer and then have to find the old task.
> Yes, "C-u C-c C-x C-j" shows you the recent clcoked in tasks but  
> automising the clocking in/out work would make the "remembering" of  
> new tasks just faster.

I could image a `clock out and return to the previous one' would be  
handy, even out of the remember facility. Nested activities would be  
great! Of course, one could always mis-use remember for that (if the  
previous feature get implemented, that is), but it feels more  
convenient to have nested clocks.


  reply	other threads:[~2009-10-01 10:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 20:48 A simpler remember architecture (was: Re: Re: is there a hook to save a remember buffer?) Samuel Wales
2009-09-30 10:39 ` Eric S Fraga, Eric S Fraga
2009-09-30 10:40 ` Carsten Dominik
2009-09-30 14:45   ` Tim O'Callaghan
2009-09-30 14:50     ` Carsten Dominik
2009-09-30 15:55       ` Tim O'Callaghan
2009-10-01  3:25       ` Sebastian Rose
2009-10-05 23:41     ` A simpler remember architecture Daniel Clemente
2009-10-06  0:24       ` Alan E. Davis
2009-10-01  8:03   ` A simpler remember architecture (was: Re: Re: is there a hook to save a remember buffer?) Jean-Marie Gaillourdet
2009-10-01  9:14     ` Rainer Stengele
2009-10-01 10:26       ` Peter Frings [this message]
2009-10-01 18:41       ` A simpler remember architecture Bernt Hansen
2009-10-02  8:08         ` Jean-Marie Gaillourdet
2009-10-02 13:54           ` Bernt Hansen
2009-10-03  2:48           ` David Bremner
2009-10-06  6:49         ` Daniel Clemente
2009-10-06 11:32           ` Bernt Hansen
2009-10-06 12:27             ` Carsten Dominik
2009-10-06 14:33               ` Daniel Clemente
2009-10-06 14:34                 ` Bernt Hansen
2009-10-07  7:17                 ` Eric S Fraga, Eric S Fraga

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:

  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=B3EB5713-BAF2-4F79-934F-73E7AFAD9723@agfa.com \
    --to=peter.frings@agfa.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).