Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: matt.fowles@gmail.com (Matt Fowles)
Subject: [sup-talk] incrementally loading large messages
Date: Mon, 28 Jul 2008 15:03:13 -0400	[thread overview]
Message-ID: <fbf191170807281203h1f505959h8ffd62dd7704253c@mail.gmail.com> (raw)
In-Reply-To: <1217269028-sup-6714@entry>

William~


On Mon, Jul 28, 2008 at 2:22 PM, William Morgan
<wmorgan-sup at masanjin.net> wrote:
> Reformatted excerpts from Matt Fowles's message of 2008-07-28:
>> I have a feature request for sup which block my ability to use it in a
>> work context.  Extremely large emails, must download fully before
>> being displayed at all.  Unfortunately, my work emails out nightly
>> test results which are so large that they can take minutes to load in
>> sup.  I would like it if sup showed the incrementally as it loaded.
>
> Wow. That's a large email.

Yeah, it is 5.3 MB.


> This is a good time for such a feature request, because I'm in the
> middle of designing the Sup server protocol. Consider it added.
>
>> Also, does sup have a bug tracker where features can be submitted,
>> because I have a preference to be able to file bugs that I find
>> without being on the mailing list.
>
> Oh yes, it's very simple. Clone the Sup repo, add a ditz issue, and send
> a merge request to me. No mailing list usage required whatsoever. :)

Is there no web interface?  Perhaps, that is a ditz feature request...

Matt


      reply	other threads:[~2008-07-28 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 15:04 Matt Fowles
2008-07-28 18:22 ` William Morgan
2008-07-28 19:03   ` Matt Fowles [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=fbf191170807281203h1f505959h8ffd62dd7704253c@mail.gmail.com \
    --to=matt.fowles@gmail.com \
    /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