emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Daniel Clemente <n142857@gmail.com>
Cc: Rainer Stengele <rainer.stengele@online.de>,
	org-mode <emacs-orgmode@gnu.org>
Subject: Re: Re: A simpler remember architecture
Date: Tue, 06 Oct 2009 07:32:41 -0400	[thread overview]
Message-ID: <871vlgep0m.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <ae9590aa0910052349g392f15adye5096e940f34e25a@mail.gmail.com> (Daniel Clemente's message of "Tue\, 6 Oct 2009 08\:49\:43 +0200")

Daniel Clemente <n142857@gmail.com> writes:

>   Just another off-topic but however related...:
>
>> C-u C-c C-x C-i i
>>
>
>   What if C-u C-c C-x C-i could show, in addition to the recently
> clocked tasks, some fixed tasks from a user-defined list?
>   The dialog would be:
>
> Common tasks:
> [1] answer phone
> [b] breakfast
> [p] procrastinate!
> [n] think about next task to do
> [2] work on file2 a bit more
> Recently clocked in tasks:
> [a] working on this
> [b] working on that
>
>
>   That list of common tasks could even be progressively created from
> statistics of the most commonly clocked tasks.

I just use my STARTED agenda view for this.  I have a small number of
tasks in STARTED state for conveniently looking up what to clock in.  It
doesn't have a single keystroke access but the list is short enough that
I find it convenient to use.

I don't think we should pollute the recent clock list with other common
tasks.  If this is really needed then I think it would be better to be a
separate list so we don't have to share key sequence combinations etc.

-Bernt

  reply	other threads:[~2009-10-06 11:32 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
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 [this message]
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:
  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=871vlgep0m.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=n142857@gmail.com \
    --cc=rainer.stengele@online.de \
    /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).