From: Hamish Downer <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Mail-to-self does not end up in inbox
Date: Mon, 20 Jun 2011 00:39:24 +0100 [thread overview]
Message-ID: <1308526747-sup-5729@whisper> (raw)
Excerpts from Amadeusz Żołnowski's message of Mon Mar 07 08:27:56 +0000 2011:
> Excerpts from Ico Doornekamp's message of Sun Mar 06 18:34:56 +0000 2011:
> > Back in the old days when using mutt, I regularly used to send mails to
> > myself as reminders or short notes. Sup however shows intelligent
> > behaviour, recognizes the message is both sent and received, and
> > attaches a 'sent' label to it, and thus the mail does not show up in the
> > inbox.
>
> Why not have requested behaviour (sent mail in inbox) and hook for
> archiving? E.g. I am usually modyfing labels on sent mail. And it's
> easier to archive sent mail than unarchive it.
I've thought about this more and added an option ":archive_sent" to
allow this. The default value is "true", so sent mail will continue to
be archived if you do nothing. Change it to false if you want to have
sent mail show up in your inbox.
This is in the archive_sent branch and has been merged into next.
I may at some point have a go at making it possible to edit labels while
composing messages, but that may be overly complex ...
And as a side note, I've looked through the history and it looks like
the sent source has always been set up to archive the mail, but maybe a
bug elsewhere in the code "fixed" it so that the sent mail really was
archived.
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-06-19 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 23:39 Hamish Downer [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-06 18:34 Ico Doornekamp
2011-03-06 19:15 ` Steve
2011-03-06 23:36 ` Hamish
2011-03-07 6:51 ` Ico Doornekamp
2011-03-07 8:27 ` Amadeusz Żołnowski
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=1308526747-sup-5729@whisper \
--to=dmishd@gmail.com \
--cc=sup-devel@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