From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sent mail in inbox view
Date: Sat, 19 Dec 2009 17:26:23 -0500 [thread overview]
Message-ID: <1261261488-sup-6981@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1261249910-sup-9552@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 716 bytes --]
Excerpts from William Morgan's message of Sat Dec 19 14:14:33 -0500 2009:
> I think it might be better to auto-archive sent messages and to flash a
> message saying "Message sent!" or something instead.
I'm not opposed to a changed default (a configure knob would be nice
though), but I've always liked the current behaviour and now find
gmail's behaviour annoying. To me, it fits more with the 'big stack
of mail' approach, although it's definitely a grey area when you
consider auto-archived sources.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-20 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 14:19 C. Morgan Hamill
2009-12-19 19:14 ` William Morgan
2009-12-19 21:27 ` Helge Titlestad
2009-12-19 22:26 ` Ben Walton [this message]
2009-12-20 1:22 ` Cameron Matheson
2009-12-21 16:56 ` John Bent
2009-12-21 18:13 ` William Morgan
2009-12-21 18:25 ` John Bent
2009-12-21 18:34 ` William Morgan
2009-12-21 18:47 ` John Bent
2009-12-21 19:31 ` William Morgan
2009-12-21 20:02 ` Tarko Tikan
2009-12-20 2:17 ` Tero Tilus
2009-12-21 13:45 ` William Morgan
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=1261261488-sup-6981@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-talk@rubyforge.org \
/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