public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] recommended applications
Date: Sun, 24 May 2015 15:01:20 +0300	[thread overview]
Message-ID: <20150524150120.859e421a8154e97616e84b81@gentoo.org> (raw)
In-Reply-To: <CAO5-k+qJ5bw4Ke7-x_D=F38b--rA3sL3ouqs+daqzYgYFnj-mA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

Hi,

On Sun, 24 May 2015 15:02:13 +0430 behrouz khosravi wrote:
> Hello everyone. After spending about a year in the world of linux (and
> mostly beloved gentoo!) I have realized that the key to a stable and fast
> machine is to keep the system as small as possible.
> So I am going to use console based tools mostly. I will also replace KDE
> with i3wm.
> 
> What do you recommend as a replacement for kmail? (is mutt a good choise?)

I depends on personal preferences. I'm not sure why, but I always
had problems with intensive mail traffic and mutt. Also many mails
are html-base and mutt is not the best way to deal with them.
(I know that html mails are disgusting, but too many people use
them these days to disregard this trend completely.)

So I use sylpheed. It is GUI-based, can read html mails (but not
write them, he-he). So it suits me well. Your mileage may vary, of
course.

> What about IRC client?

Use irssi. It is a reliable and highly configurable CLI solution.
 
> Torrent client?

Use transmission. Just compile it without qt* and gtk flags. This
is a client-server application, so transmission-daemon runs as
system service as unpriviledged user and all management is done via
nice CLI tool transmission-remote. Also transmission is
fully-fledged solution supporting all trends like dht, utp and
so on. You'll love it.

> I know that I can use google! but I would like to know your opinion.

Browser-based solution can't be lightweight, so I try to avoid them
whenever possible.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-05-24 12:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 10:32 [gentoo-user] recommended applications behrouz khosravi
2015-05-24 10:44 ` Meino.Cramer
2015-05-24 11:07   ` behrouz khosravi
2015-05-24 13:35     ` Nuno Magalhães
2015-05-24 13:41       ` Vladimir Romanov
2015-05-24 16:19   ` Alan Grimes
2015-05-24 17:25     ` behrouz khosravi
2015-05-24 12:01 ` Andrew Savchenko [this message]
2015-05-24 12:17   ` rhannek
2015-05-24 13:18 ` Ramdziana Feri Y
2015-05-24 13:38 ` Heiko Baums
2015-05-24 14:14 ` wabenbau
2015-05-24 14:19   ` Heiko Baums
2015-05-24 15:04     ` wabenbau
2015-05-24 14:35 ` [gentoo-user] " »Q«
2015-05-24 14:40 ` [gentoo-user] " Sebastián Pedersen
2015-05-24 15:02 ` Lee
2015-05-24 19:25 ` Walter Dnes
2015-05-24 20:49 ` Alec Ten Harmsel
2015-05-24 21:30 ` Volker Armin Hemmann
2015-05-24 21:53   ` Emanuele Rusconi
2015-05-25  3:08     ` Volker Armin Hemmann
2015-05-25  8:01 ` Franz Fellner
2015-05-25  9:08   ` Emanuele Rusconi
2015-05-25 12:33     ` Guy-Laurent Subri
2015-05-25 14:09       ` Emanuele Rusconi

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=20150524150120.859e421a8154e97616e84b81@gentoo.org \
    --to=bircoph@gentoo.org \
    --cc=gentoo-user@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