From: philsnow@gmail.com (Phil Snowberger)
Subject: [sup-talk] PATCH: make each thread's snippet come from the latest reply, not the earliest
Date: Tue, 23 Oct 2007 17:55:58 -0400 [thread overview]
Message-ID: <6ab4c98f0710231455w68f89232r527b8d4b43e9e16f@mail.gmail.com> (raw)
Attached is a patch (against the SVN trunk) that makes each thread's
snippet come from the latest reply instead of the earliest.
I thought about providing a configuration option for it, but this
really seems like the Right Thing To Do, so I'll both avoid needless
work (figuring out how to add an option to sup) and go along with
William's reluctance to turn sup's configuration into a huge soupy
mess.
The motivation behind this change was that when I receive a one-line
response to an email, that one line is the most important information
about that thread at the moment, so the precious screen space in the
thread index should go to that line.
--Phil
p.s. Thanks for sup, William! It's just what I wanted, but I hadn't
realized what I wanted until I saw it :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-snippet-last.diff
Type: text/x-diff
Size: 618 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071023/777d97b5/attachment.bin
next reply other threads:[~2007-10-23 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 21:55 Phil Snowberger [this message]
2007-10-27 22:24 ` 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=6ab4c98f0710231455w68f89232r527b8d4b43e9e16f@mail.gmail.com \
--to=philsnow@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