emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: brian powell <briangpowellms@gmail.com>
Cc: Memnon Anon <gegendosenfleisch@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: ThoughtBack
Date: Sat, 16 Jul 2011 13:28:31 +0200	[thread overview]
Message-ID: <87ipr2fmxs.fsf@altern.org> (raw)
In-Reply-To: <CAFm0skE4+HGKJ4i27PzMdt8mcdAq_2SxNh0tT-=V-NM4gei2Jw@mail.gmail.com> (brian powell's message of "Fri, 15 Jul 2011 12:50:55 -0400")


AFAIU, the fun of using ThoughtBack is to get *random* ideas 
from the past.  This actually could fit in Org: get a random
agenda based on selected criteria.  

Would that be useful?

For the record, we already have some randomness through the
bulk command "scatter" -- where items are scattered randomly
over a definite period of time.


  parent reply	other threads:[~2011-07-16 12:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 15:03 ThoughtBack brian powell
2011-07-13 16:11 ` ThoughtBack Bastien
2011-07-13 18:49   ` ThoughtBack John Hendy
2011-07-15 13:00     ` ThoughtBack Memnon Anon
2011-07-15 16:50       ` ThoughtBack brian powell
2011-07-15 18:30         ` ThoughtBack Memnon Anon
2011-07-16 11:28         ` Bastien [this message]
2011-07-15 18:11       ` ThoughtBack John Hendy

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=87ipr2fmxs.fsf@altern.org \
    --to=bzg@altern.org \
    --cc=briangpowellms@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gegendosenfleisch@googlemail.com \


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