From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] 0.5 thoughts
Date: Fri, 25 Jan 2008 08:52:20 -0800 [thread overview]
Message-ID: <1201279056-sup-4012@south> (raw)
In-Reply-To: <1201241373-sup-5327@tangerine.lanl.gov>
Reformatted excerpts from John Bent's message of 2008-01-24:
> Excerpts from William Morgan's message of Thu Jan 24 22:59:43 -0700 2008:
> > - Mbox filehandle closing (currently every mbox gets its own
> > filehandle which is kept open for the duration of the program)
>
> Is this a good thing? I'd rather set my open filehandle limit really
> high and have them kept open. Isn't it slower to constantly have to
> reopen them? Well, I guess the unusual ones certainly don't need an
> open handle.
It will introduce a very minor slowdown, but I don't think it will
really be that noticeable. And the current approach basically prevents
people from having large numbers of mbox sources, which is a little
contrary to the Sup philosophy of "put every email you've ever read in
one program."
> > - Date conversion to the local timezone, for sorting and display
> Yeah, there's something wrong with my timestamps. Everything shows up
> as PM. The time is right but it always says PM in the display...
That's weird. Is this in thread-index-mode? What about when you expand
the header ('h') in thread-view-mode? Does the time appear correctly?
> I don't know what your philosophical feelings are about this but it
> might be nice to combine IM into sup. It'd be a bunch more protocols
> to incorporate and the model might be completely different though.
Iiiinteresting. Making Sup an IM client proper is almost certainly
a world of misery. Getting the current textfield stuff working was a
goddamn nightmare, and it's still very wonky. It does seem a little
weird, philosophically speaking, but I wouldn't throw such code away if
it were dumped on my lap. :)
That said, what WOULD be easy is to treat IM logs as a message source,
and put conversations in the index, gmail style.
> Also, is there a way to go from one thread-view directly to another?
> I always have to 'x' to go back to the search-results-mode or the
> inbox-mode and then scroll to the message I want.
Try the comma-commands. ",n", etc.
> I thought 'n' and 'p' would do this but I've never been able to get
> them to do anything for me.
These jump between individual open messages in a thread.
> Thanks again for all your hard work. I'm very happy about sup; it's
> made me much more productive and much better organized. I really
> appreciate the efforts of you and all the other contributors.
Glad to hear it. Sup is mostly to scratch my own itch.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-25 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 5:59 William Morgan
2008-01-25 6:22 ` John Bent
2008-01-25 16:52 ` William Morgan [this message]
2008-01-25 20:37 ` Nicolas Pouillard
2008-01-25 22:31 ` John Bent
2008-01-25 11:12 ` Sho Fukamachi
2008-01-25 11:26 ` Nicolas Pouillard
2008-01-31 13:24 ` Giorgio Lando
2008-02-08 1:09 ` William Morgan
2008-02-08 8:42 ` Giorgio Lando
2008-01-26 5:03 ` Daniel Wagner
2008-01-26 5:12 ` Daniel Wagner
2008-01-25 13:22 ` vasudeva
2008-01-26 0:37 ` John Bent
2008-01-26 1:00 ` vasudeva
2008-01-25 14:46 ` John Bent
2008-01-26 3:56 ` Christopher Warrington
2008-01-26 5:05 ` Daniel Wagner
2008-01-27 16:16 ` Giorgio Lando
2008-01-27 20:29 ` Marcus Williams
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=1201279056-sup-4012@south \
--to=wmorgan-sup@masanjin.net \
/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