From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] background or queue msg sending
Date: Thu, 17 Mar 2011 15:15:30 -0400 [thread overview]
Message-ID: <1300385916-sup-3971@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1300375667-sup-4657@panda>
Hi Bruno.
Excerpts from Bruno d'Arcangeli's message of Thu Mar 17 11:32:12 -0400 2011:
> Le 17/03/2011 à 15:17, Philippe LeCavalier a écrit:
> > Hi All.
> >
> > Does anyone know of a way to background or perhaps queue
> > sending mail. Sup has me so efficient I've even lost the patience to
> > wait for msgs to be sent. I really want to hit 'y' and move on.
> >
> > Any thoughts, experiences? My first though was manipulating the buffers
> > so that the previous buffer would get called back before the mail gets
> > confirmed as sent and then the confirmation itself could still be
> > displayed in the notification area.
>
> Try with a real mta like postfix or exim. There are simple to use/configure.
> Personnaly, i've a little preference in exim.
>
I've used both and can't really say I prefer one over the other but I'm
not certain I understand how that would help me background or queue
sending mail in sup. Like right now, after I press 'y', I want sup to
_immediately_ bring me to either my inbox-mode or this thread in
thread-mode. Either buffer would be fine with me though I suspect for
continuity proposes return to the thread might be more logical. I just
don't want to wait for the 'Message Sent!'.
Even if Exim or Postfix might act faster than msmtp(what I'm using now)
sup is set up in a way that it waits for the process to terminate before
bringing me to the previous buffer. What I'd like to suggest is that sup
should immediately bring you to the previous buffer.
--
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-03-17 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:17 Philippe LeCavalier
2011-03-17 15:32 ` Bruno d'Arcangeli
2011-03-17 19:15 ` Philippe LeCavalier [this message]
2011-03-17 19:55 ` Ben Walton
2011-03-17 20:16 ` Kevin Riggle
2011-03-17 23:10 ` Philippe LeCavalier
2011-03-17 19:54 ` Tero Tilus
2011-03-17 20:10 ` Philippe LeCavalier
2011-03-17 22:32 ` Sascha Silbe
2011-03-17 23:08 ` Philippe LeCavalier
2011-03-18 1:34 ` Philippe LeCavalier
2011-03-18 0:53 ` Tero Tilus
2011-03-18 1:31 ` Philippe LeCavalier
2011-03-17 22:42 ` Sean Escriva
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=1300385916-sup-3971@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--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