From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Jonas H. <jonas@lophus.org>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Help me getting started.
Date: Sun, 19 Dec 2010 18:34:35 -0500 [thread overview]
Message-ID: <1292801467-sup-5115@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <4D0E8DDD.20505@lophus.org>
Excerpts from Jonas H.'s message of Sun Dec 19 17:57:33 -0500 2010:
Hi Jonas,
> 1. `sup-configure` asked me for my primary e-mail address. I have no
> primary e-mail address. In fact, I have several "personalities"
> being myself in in different contexts. It is very important to me
> to make sure those personalities, represented by different e-mail
> addresses, will *never* be accidentally mixed. Can Sup make me
> force to chose the e-mail address I want to send from for every mail
> I start writing? (Of course, when answering a mail, I would answer
> with the address it was sent to.)
You can add and use multiple email accounts. The 'primary' label is
more of a 'default' than a primary. You'll want to use the various
hooks to automatically set the email address used. You can also
change this while editing the message you're sending.
> 2. How can I display my own email bodies in thread view? Sometimes
> someone digs up thread so ancient I don't remember what I wrote back
> then.
Sup does this automatically.
> 3. I hate mbox. Can I use other mailbox formats for sent e-mails?
Maildir is an option.
> 4. For incoming mails, I used to use POP3, and I want keep storing
> my mail locally (only). Which MDA solution is the best as far as
> performance is concerned? My netbook has very poor CPU and HDD
> performance (loooong HDD wakeup times), so that's what matters most
> in this regard.
I'd say fetchmail, but I think it still requires a local mail delivery
system. There is likely some pop3 fetch tool, but I'm not familiar
with any of them.
> 5. As it worth using Ruby 1.9 for Sup? I have no idea about Ruby 1.8
> vs Ruby 1.9 -- any bug fixes, performance improvements,
> ... affecting Sup?
I'm still using a really old 1.8. I've tried to go to 1.9, but I
don't have xapian working yet...
> 6. Vertical scrolling is *very* laggy. The terminal emulator doesn't
> matter; as soon as I do a vertical scroll CPU usage jumps up to
> 100%. Am I missing any important tweaks?
Not sure.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-19 23:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:57 Jonas H.
2010-12-19 23:34 ` Ben Walton [this message]
2010-12-20 7:57 ` Tero Tilus
2010-12-20 13:39 ` Jonas H.
2010-12-20 18:24 ` Marc Hartstein
[not found] ` <4D0F5C5E.7030809@lophus.org>
2010-12-20 13:57 ` Tero Tilus
2010-12-23 10:17 ` Jonas H.
2010-12-30 13:14 ` Jonas H.
2010-12-30 15:31 ` Tero Tilus
2010-12-30 21:33 ` Tero Tilus
2010-12-30 23:09 ` Tero Tilus
2010-12-30 23:03 ` Tero Tilus
2010-12-30 23:37 ` Jonas H.
2010-12-31 0:45 ` Tero Tilus
2010-12-31 10:14 ` Jonas H.
2011-03-22 18:01 ` Jonas H.
2010-12-20 13:41 ` Mark Alexander
2010-12-20 14:10 ` Shadowfirebird
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=1292801467-sup-5115@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=jonas@lophus.org \
--cc=sup-talk@rubyforge.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