From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 5
Date: Tue, 12 Jul 2016 15:27:36 -0400 [thread overview]
Message-ID: <20160712192736.GC1285@ca.inter.net> (raw)
In-Reply-To: <3808019.JuIJNGuGPj@dell_xps>
160712 Mick wrote:
> On Tuesday 12 Jul 2016 20:06:05 Jens Reinemuth wrote:
>> KDE 5 is usable iff you dont use kdepim/akonadi with mailing lists ...
>> As soon as my count of Mails grow over some thousands,
>> Akonadi simply stops working, ie is no longer fetching or displaying Mail.
>> The desktop is cool and stable pim is not really since some versions ago.
> I don't use the full plasma desktop, but use KDEPIM and some other KDE apps
> with all their unavoidable dependencies. It is usable for me,
> on two machines where akonadi is running on MySQL
> and on my laptop with PostgreSQL. I use Enlightenment as my day to day DE
> and Fluxbox as a fall back. Having to install some parts of Plasma
> does not mean you have to use it as your desktop.
I'm quite satisfied with Fluxbox & have no intention of using KDE desktop.
> You need some CPU horsepower and patience
> to let Akonadi index all messages in the database.
> If your PC is resource constrained,
> it'll have trouble managing large mail boxes.
> I remember a Pentium Duo with 4G RAM taking overnight to update mailboxes,
> which in their totality contained more than 125,000 messages.
> When I repeated the exercise with < 5000 messages, the response
> was much more reasonable : it took a few minutes, rather than hours.
I've been a contented user of Mutt since 1998, so that's no problem.
BTW Whatever is the point of keeping 125 K mail messages ?
-- at 1 min each , it would take 90 days to read them (without sleep).
As for desktop indexing, it's simply an overweight tool
for those too lazy to keep their directories + files in proper order (smile).
It seems to have been invented to try to help users of proprietary systems
which make it difficult to keep track of anything for long.
Anyone else have comments on using KDE 5 ? -- thanks so far.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2016-07-12 19:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 17:30 [gentoo-user] KDE 5 Philip Webb
2016-07-12 18:06 ` Jens Reinemuth
2016-07-12 18:33 ` Mick
2016-07-12 19:27 ` Philip Webb [this message]
2016-07-12 21:56 ` Mick
2016-07-12 23:19 ` Neil Bothwick
2016-07-13 7:14 ` Stefano Crocco
2016-07-13 17:38 ` Mick
2016-07-13 18:50 ` [gentoo-user] " Michael Palimaka
2016-07-13 22:04 ` Mick
2016-07-14 16:03 ` Michael Palimaka
2016-07-14 21:00 ` Mick
2016-07-15 15:30 ` Michael Palimaka
2016-07-15 17:52 ` Mick
2016-07-16 15:28 ` Michael Palimaka
2016-07-16 15:00 ` Mick
2016-07-16 15:29 ` Michael Palimaka
2016-07-16 15:41 ` Mick
2016-08-21 7:06 ` Mick
2016-07-12 19:23 ` [gentoo-user] " Neil Bothwick
2016-07-12 20:20 ` Raphael MD
2016-07-12 20:53 ` Raphael MD
2016-07-12 21:41 ` Fernando Rodriguez
2016-07-13 2:59 ` Dale
2016-07-13 3:51 ` konsolebox
2016-07-13 5:21 ` Bill Kenworthy
2016-07-13 18:53 ` Frank Steinmetzger
2016-07-13 9:10 ` Peter Humphrey
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=20160712192736.GC1285@ca.inter.net \
--to=purslow@ca.inter.net \
--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