Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: stipim@rpi.edu (Mike Stipicevic)
Subject: [sup-talk] Can sup only "save threads" on exit??
Date: Fri, 07 Nov 2008 12:13:48 -0500	[thread overview]
Message-ID: <1226078013-sup-1549@rmtacc26-la.rcs.rpi.edu> (raw)
In-Reply-To: <1226010841-sup-4962@entry>

I had hoped to work on this in a bit...

Excerpts from William Morgan's message of Thu Nov 06 17:35:13 -0500 2008:
> Reformatted excerpts from Steve Goldman's message of 2008-11-05:
> > Is there a setting to make sup do this automatically every
> > once in a while?  It would be nice to be able to leave sup open all
> > day, or many days, and not have to worry about remembering to hit '$'
> > or a crash.
> 
> I've been avoiding this because currently the only way to undo changes
> in thread-index-mode is to press @, which reverts you to the state you
> were last time you pressed $. Undo patches also welcome. :)
-- 
Mike Stipicevic
Chairman, RPI Student Branch of the IEEE

stipim at rpi.edu
mstipicevic at ieee.org


      reply	other threads:[~2008-11-07 17:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 22:55 Steve Goldman
2008-11-05  0:36 ` John Bent
2008-11-05 13:06   ` Nicolas Pouillard
2008-11-06 16:19     ` William Morgan
2008-11-07 14:18       ` Nicolas Pouillard
2008-11-10  4:49         ` William Morgan
2008-11-05 14:34   ` Steve Goldman
2008-11-05 17:59     ` William Morgan
2008-11-06 14:38       ` Steve Goldman
2008-11-06 16:18         ` William Morgan
2008-11-06 14:40     ` Nicolas Pouillard
2008-11-06 15:00       ` [sup-talk] [PATCH] save contacts.txt on '$' Nicolas Pouillard
2008-11-10  4:51         ` William Morgan
2008-11-06 22:35     ` [sup-talk] Can sup only "save threads" on exit?? William Morgan
2008-11-07 17:13       ` Mike Stipicevic [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=1226078013-sup-1549@rmtacc26-la.rcs.rpi.edu \
    --to=stipim@rpi.edu \
    /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