Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] 0.5 thoughts
Date: Fri, 25 Jan 2008 20:00:13 -0500	[thread overview]
Message-ID: <1201308435-sup-8242@lenin> (raw)
In-Reply-To: <1201307782-sup-1056@tangerine.lanl.gov>

Excerpts from John Bent's message of Fri Jan 25 19:37:07 -0500 2008:
> Excerpts from vasudeva's message of Fri Jan 25 06:22:52 -0700 2008:
> > Excerpts from William Morgan's message of Fri Jan 25 00:59:43 -0500 2008:
> > If we're interested in 'Getting Things Done', then a nice related
> > feature might be the ability to tell sup not to exit on a 'q' keypress
> > if there are buffers open marked TODO (or whatever). One of the things I
> > like about sup is the multi-window approach, because instead of making
> > me feel *bad* about having lots of half-finished work, it makes me feel
> > as though it's reasonable I might just have it going in the background.
> > I find this mis-truth appealing.
> > 
> What is this TODO buffer you're talking about please?  Sounds useful!

Sort of random association I made. There's a neat type-A smartypants
thing called 'Getting Things Done' which seems to be a methodology
for...  getting things done. More here...

http://en.wikipedia.org/wiki/Getting_Things_Done

The bit William brought up about adding 'note' objects piqued my
interest and seemed kind of GTD-ish.  Personally, I tend to use my inbox
as my TODO list, so the ability to "stick" windows -- to set sup buffers
non-volatile -- would be something I'd use a lot. As a long-time mutt
user, a certain background portion of my brain, as I navigate sup, is
devoted entirely to NOT hitting the 'q' key, which is basically muscle
memory at this point.

-- 
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart



  reply	other threads:[~2008-01-26  1:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25  5:59 William Morgan
2008-01-25  6:22 ` John Bent
2008-01-25 16:52   ` William Morgan
2008-01-25 20:37     ` Nicolas Pouillard
2008-01-25 22:31     ` John Bent
2008-01-25 11:12 ` Sho Fukamachi
2008-01-25 11:26   ` Nicolas Pouillard
2008-01-31 13:24     ` Giorgio Lando
2008-02-08  1:09       ` William Morgan
2008-02-08  8:42         ` Giorgio Lando
2008-01-26  5:03   ` Daniel Wagner
2008-01-26  5:12     ` Daniel Wagner
2008-01-25 13:22 ` vasudeva
2008-01-26  0:37   ` John Bent
2008-01-26  1:00     ` vasudeva [this message]
2008-01-25 14:46 ` John Bent
2008-01-26  3:56 ` Christopher Warrington
2008-01-26  5:05 ` Daniel Wagner
2008-01-27 16:16 ` Giorgio Lando
2008-01-27 20:29 ` Marcus Williams

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=1201308435-sup-8242@lenin \
    --to=vasudeva@linkswarm.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox