From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] inconsistencies and new user confusion
Date: Thu, 21 May 2009 08:24:42 -0700 [thread overview]
Message-ID: <1242919384-sup-7255@entry> (raw)
In-Reply-To: <20090521144607.GC28854@pimlott.net>
Reformatted excerpts from Andrew Pimlott's message of 2009-05-21:
> What branch? No change on mainline.
Sorry, the "next" branch.
> What I'm getting at is, why not keep the index up-to-date at all
> times? The only reason I see not to is so the user can say "oops" and
> quit without saving. But that's what undo is for. (Or transactions.)
This is certainly an option in the future. We've used "$" because until
recently there hasn't been an undo, and because it gives me fond
memories of Mutt. Once undo is fleshed out a bit more, auto-syncing
could certainly be an option.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-05-21 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 23:33 Andrew Pimlott
[not found] ` <20090513042345.GB18461@cabinet.hsd1.ma.comcast.net>
2009-05-13 5:23 ` Edward Z. Yang
2009-05-18 19:19 ` William Morgan
2009-05-13 14:53 ` Andrew Pimlott
2009-05-18 19:17 ` William Morgan
2009-05-21 14:46 ` Andrew Pimlott
2009-05-21 15:24 ` William Morgan [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=1242919384-sup-7255@entry \
--to=wmorgan-sup@masanjin.net \
/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