From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Sup annoyances
Date: Sat, 06 Jun 2009 02:54:01 -0400 [thread overview]
Message-ID: <1244270435-sup-9288@javelin> (raw)
Having just submitted my first patch, I feel entitled to gripe and
moan about certain aspects of Sup. The hope is that I'll get some
pointers on what code to look at to fix these gripes. These gripes
are independent of the hanging/other behavior in my other monster
thread. (I'd say the asynchronous polling hang is my other biggest
gripe, but that's not an issue for here).
1. Threads should be lazy-loaded (possibly in the background), with
visible messages first. If a conversation got a new message, Sup
should only take its time to load that message, and not the frickin'
24 other messages that were also incidentally there. I suspect
this will require some pretty major refactoring. As a stop-gap,
I should have the option of cancelling when I open a long thread
(right now, I think it causes sup to crash).
2. Auto-completion sucks and should be improved. I should be able
to press "c", type two letters, and then mash tab. If auto-completion
actually works, then I'll blame it on dismal contacts.txt support
(if I send mail to someone, there should be a configuration twiddle
that saves it to contacts.txt. And then remembers it the next
time I want to compose mail to them).
3. Polling and loading of threads should started, asynchronously, at
the same time. Loading of threads should not hose my CPU. Loading
of threads should do smart things, instead of doing an O(n) time warp.
It takes forever for a mail from two months ago that is still in my
inbox, because it still hasn't been addressed, to show up. This could
probably be fixed with a cache file. This isn't as big of a deal
if asynchronous polling hang and crashing is fixed.
4. Sup should prompt me whether or not I want to Reply All or Reply on
appropriate cases, like pine.
Cheers,
Edward
next reply other threads:[~2009-06-06 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 6:54 Edward Z. Yang [this message]
2009-06-06 6:56 ` Edward Z. Yang
[not found] ` <1244308338-sup-4735@cabinet>
2009-06-06 18:17 ` Edward Z. Yang
2009-06-08 18:00 ` William Morgan
2009-06-08 23:14 ` Edward Z. Yang
2009-06-08 23:46 ` William Morgan
2009-06-09 2:13 ` Edward Z. Yang
2009-06-09 2:23 ` Edward Z. Yang
2009-06-09 2:35 ` Edward Z. Yang
2009-06-09 17:40 ` William Morgan
2009-06-11 3:18 ` Edward Z. Yang
2009-06-09 17:48 ` William Morgan
2009-06-11 3:19 ` Edward Z. Yang
2009-06-09 17:32 ` William Morgan
2009-06-09 2:38 ` Edward Z. Yang
2009-06-09 17:45 ` William Morgan
2009-06-09 3:00 ` Edward Z. Yang
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=1244270435-sup-9288@javelin \
--to=ezyang@mit.edu \
/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