From: ingmar@exherbo.org (Ingmar Vanhassel)
Subject: [sup-talk] [PATCH 2/2] ui responsiveness tweaks
Date: Thu, 27 Aug 2009 04:54:36 +0200 [thread overview]
Message-ID: <1251341498-sup-428@cannonball> (raw)
In-Reply-To: <1251318620-sup-3031@yoom.home.cworth.org>
Excerpts from Carl Worth's message of Wed Aug 26 23:15:36 +0200 2009:
> My message here really has nothing to do with Rich's patches
> specifically, (so sorry about that), but his patches happened to
> provide the perfect context for an issue I wanted to bring up. As is
> typical of git-formatted patches, Rich's emails have subject lines
> from his commit messages:
>
> [sup-talk] [PATCH 1/2] preemptively load messages when scrolling
> [sup-talk] [PATCH 2/2] ui responsiveness tweaks
>
> As far as the git commits go, this subject line is one of the most
> essential pieces of metadata to accompany the patch. Yet by default
> sup doesn't display it at all, (requiring keypresses to display the
> header and find the subject line). I think what I would like is for
> sup to display the subject line everytime it changes significantly in
> a thread, (specifically not regarding things like an initial "Re: "
> getting added as significant).
>
> I think I'd be willing to spend an entire line's worth of screen real
> estate for this information---it's quite useful when people do
> meaningful subject changes for sub-threads.
Yeah, I completely agree. That would make sup even better for me.
Maybe this could be implemented as a 3-way toggle, toggling between
- don't show subjects (current default?)
- only show interesting subject changes
- always show subject
in a threadview.
-Ingmar
--
Exherbo KDE, X.org maintainer
next prev parent reply other threads:[~2009-08-27 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 18:46 [sup-talk] [PATCH 1/2] preemptively load messages when scrolling Rich Lane
2009-08-23 18:46 ` [sup-talk] [PATCH 2/2] ui responsiveness tweaks Rich Lane
2009-08-26 21:15 ` Carl Worth
2009-08-27 2:54 ` Ingmar Vanhassel [this message]
2009-09-02 3:59 ` Rich Lane
2009-09-03 17:58 ` 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=1251341498-sup-428@cannonball \
--to=ingmar@exherbo.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