public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Can't Emerge Thunderbird-5.0/6.0
Date: Wed, 24 Aug 2011 01:51:59 -0400	[thread overview]
Message-ID: <20110824015159.09ff4018.frank.peters@comcast.net> (raw)
In-Reply-To: <pan.2011.08.24.03.43.05@cox.net>

On Wed, 24 Aug 2011 03:43:05 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> 
> So I've been wondering what the rest of the story might be, and why 
> people, at least non-Japanese (no offense, just that info's easier to 
> absorb if it's not filtered thru google translate or the like), might 
> prefer sylpheed to claws.  If you could shed some light on either the 
> difference in emphasis and split, or why you personally prefer sylpheed, 
> I'd be quite interested. =:^)
> 

When I first began using Linux, I tried a few of the console email clients
such as pine, mutt, and nmh.  These programs were useful, but I really
preferred a GUI approach to composing and organizing, yet I also did
not want to lose the simplicity of the console clients.  Sylpheed (the
name connotes "light weight" in Japanese) was the answer.  It is graphical
without being bloated.

Sylpheed reminds me of a MS Windows email client called Pegasus, which has
a very similar style, ease, and functionality.

The Sylpheed web site describes its attractive attributes, I think, nicely: 

# Simple, beautiful, and well-polished user interface
# Comfortable operationality which is built in detail
# Well-organized, easy-to-understand configuration
# Lightweight operation
# High reliability with one-mail-corresponding-to-one-file format

Sylpheed has undergone a lot of development over the years, but I really
haven't noticed.  Email is a simple medium and my Sylpheed has always
been simply configured.  I don't bother with any of the advanced features.

As I mentioned, if I need more complex functionality, such as certificates
or encryption, I can always use thunderbird which I keep in reserve, but
Sylpheed is my regular email workhorse.

I cannot comment on claws which I haven't used, but it is essentially
Sylpheed with a lot of extra features incorporated, and, again, it is
those features which I don't require.

In the end, preferences are based on philosophy and philosophy is based
on knowledge.  I see, in my mind, every email message for what is is:
a string of text.  Even MIME attachments, like images or sounds, are there
as text strings.  I don't need, or prefer, a complex program to dissect
all the pieces and "magically" present them to me.  It is somehow more
appealing to my digital sense to approach these things from a basic level
where nothing else will interpose itself.  This is why I appreciate
software that does not attempt to "do it all" for me and to conceal the
details of the process.  Others may find this strange, but to me it is
the only way.

In fact, there was a time when I sent email messages directly from the
command line using sendmail clones.  The appeal to this was a complete
transparency of the process.  However, this soon proved to be too much
of a burden.  Sylpheed restores the ease, but it remains simple and
straightforward.


> > But there are times when I need to communicate to someone that is using
> > MS Outlook 
> 
> Argh!  If they want to read my mail, they can very well read it in plain 
> text, 

I also often shriek when I have to deal with the average MS Outlook user.
These people don't even understand computers in the least, let alone
email.  I could relate many horror stories about their antics, but
it really is not appropriate here.  However, what peeves me the most
is that every MS Outlook user will invariably top post (it is the default
in Outlook), and top posting is taboo in email communication.  But any
attempt at explanation of this is futile.  The Outlook user has no comprehension
of top posting or any thing else about the email standard, and probably
believes that Outlook is the only email client that exists.

Frank Peters



  reply	other threads:[~2011-08-24  5:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 18:47 [gentoo-amd64] Can't Emerge Thunderbird-5.0/6.0 Frank Peters
2011-08-23 18:55 ` [gentoo-amd64] " Nikos Chantziaras
2011-08-23 19:05 ` [gentoo-amd64] " Agostino Sarubbo
2011-08-23 20:02   ` Frank Peters
2011-08-23 20:13     ` [gentoo-amd64] " Nikos Chantziaras
2011-08-23 20:45     ` [gentoo-amd64] " Frank Peters
2011-08-23 23:07       ` Drake Donahue
2011-08-23 23:46         ` Frank Peters
2011-08-24  3:43           ` [gentoo-amd64] " Duncan
2011-08-24  5:51             ` Frank Peters [this message]
2011-08-24  6:39               ` Duncan
2011-08-24 15:27                 ` Frank Peters
2011-08-24 17:32                   ` Lie Ryan
2011-08-24 18:49                     ` Homer Parker
2011-08-25  8:37                       ` Lie Ryan
2011-08-25 12:24                         ` Rich Freeman
2011-08-25 19:07                         ` Homer Parker
2011-08-26  2:05                           ` Duncan
2011-08-24 17:35                   ` Duncan
2011-08-23 23:40       ` [gentoo-amd64] " Agostino Sarubbo

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=20110824015159.09ff4018.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.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