1 |
On Sunday 05 Jun 2011 12:17:08 Indi wrote: |
2 |
> On Sun, Jun 05, 2011 at 01:01:22PM +0200, Volker Armin Hemmann wrote: |
3 |
> > On Sunday 05 June 2011 06:43:37 Indi wrote: |
4 |
> > > On Sun, Jun 05, 2011 at 11:46:49AM +0200, Alan McKinnon wrote: |
5 |
> > > > Apparently, though unproven, at 23:59 on Saturday 04 June 2011, Indi |
6 |
> > > > did opine |
7 |
> > > > |
8 |
> > > > thusly: |
9 |
> > > > > On Sat, Jun 04, 2011 at 11:44:30PM +0200, Sebastian Beßler wrote: |
10 |
> > > > > > Am 04.06.2011 23:10, schrieb Indi: |
11 |
> > > > > > > Every single GUI MUA I ever tried would lock up and become |
12 |
> > > > > > > unresponsive at times when dealing with IMAP. |
13 |
> > > > > > |
14 |
> > > > > > I use Thunderbird and IMAP for 3 years now and in all that time |
15 |
> > > > > > became TB never unresponsive. So this point seems to have |
16 |
> > > > > > improved since your testing. |
17 |
> > > > > |
18 |
> > > > > That's good to know, thanks. |
19 |
> > > > > I'm unlikely to switch from mutt (due in part to so many macros and |
20 |
> > > > > customizations accumulated the last couple of years), but am always |
21 |
> > > > > keeping an eye out for those I support. |
22 |
> > > > > |
23 |
> > > > > Maybe I'll put the next person who complains about evolution on |
24 |
> > > > > thunderbird and see how they do with it... |
25 |
> > > > |
26 |
> > > > Evolution just sucks, all the time. The only feature that sets is |
27 |
> > > > apart is the Exchange support, and it's precisely that which crashes |
28 |
> > > > is. We enabled POP/IMAP on Exchange and non-Outlook users use that. |
29 |
> > > > |
30 |
> > > > Thunderbird - I itried this a while back when KMail-4.5.9999 pissed |
31 |
> > > > me off extremely. Capable enough except it does something weird with |
32 |
> > > > it's internal indexing - shows there's mail in folder, click the |
33 |
> > > > folder and it decides there isn't mail after all. S simple this, but |
34 |
> > > > a |
35 |
> > > > deal-breaking annoying one. |
36 |
> > > > |
37 |
> > > > Mutt - my networks guys use this on a dedicated mail server just for |
38 |
> > > > them |
39 |
> > > > (networks guys really are special) and they have no issues at all. 2 |
40 |
> > > > of them are hard-core crazy and choose pine instead. The only |
41 |
> > > > problem with pine is finding who is supported and maintaining it |
42 |
> > > > lately (as repine) |
43 |
> > > > |
44 |
> > > > Claws is fast, very fast. I didn't like the way it dealt with mail |
45 |
> > > > accounts and enable/disable them quickly and easily. |
46 |
> > > > |
47 |
> > > > KMail was always the best of the lot for me. It read and composed |
48 |
> > > > mail, it had all the features of a pine/mutt and shows it in a GUI. |
49 |
> > > > No weird bling-bling (it *could* do HTML mail but you had to jump |
50 |
> > > > through a hoop first) and made sensible use of the extra screen |
51 |
> > > > space and all the information that could be shown. But in the last |
52 |
> > > > year, I don't know so much anymore. KDEPIM has a "corporate sponsor" |
53 |
> > > > which I take to mean "works like Outlook". It's two whole minor |
54 |
> > > > releases behind KDE and they don't have a incremental feature set |
55 |
> > > > they can release for the interim. And then there's that text-search |
56 |
> > > > aspect that kills Akonadi. |
57 |
> > > > |
58 |
> > > > I see room for a KDEPIM fork from the 4.4 codebase in maintenance |
59 |
> > > > mode that does not add deep features. |
60 |
> > > |
61 |
> > > Thanks, Alan. Of course kmail is out of the question, as it requires a |
62 |
> > > ginormous application framework be built (and rebuilt weekly, it looks |
63 |
> > > like). |
64 |
> > > |
65 |
> > > I got pretty fed up with wasting time fooling with anything qt, |
66 |
> > > to the point it's now officially banished entirely from my systems. |
67 |
> > > That decision alone has saved me hours of extra work updating (and |
68 |
> > > subsquent repairing of the inevitable fallout) per week. |
69 |
> > > |
70 |
> > > For a long time I built vlc with qt4 (it's very convenient when you're |
71 |
> > > exhausted and just want to play a video), but finally got sick of |
72 |
> > > having to rebuild it every time the qt guys change anything (which |
73 |
> > > they seem to do about every two hours). Now I just use nvlc and cvlc |
74 |
> > > instead. |
75 |
> > > |
76 |
> > > Since I started building vlc without qt I go weeks without having to |
77 |
> > > rebuild it. |
78 |
> > > |
79 |
> > > It's too bad, really. Potentially, qt4 and kde could totally rock. |
80 |
> > > I don't suppose the corporate shenanigans with Nokia and Microsoft |
81 |
> > > have helped, either... |
82 |
> > > |
83 |
> > > Of course, I am using ~x86. It might be less hectic on stable... |
84 |
> > |
85 |
> > funny - last qt update did not require any rebuilds. |
86 |
> > |
87 |
> > I wish I could get rid of gtk. Now THAT is a mess. |
88 |
> |
89 |
> Yes, gtk also sucks but I find it far less work far less often |
90 |
> than using qt, and I've got a selection of custom themes that |
91 |
> help mitigate the ugliness. |
92 |
> |
93 |
> If I were driven strictly by aesthetic concerns qt and kde4 |
94 |
> might be my choices, as they can be extremely pleasant to look |
95 |
> at. Heh, reminds me of my ex -- he was very pleasant to look at |
96 |
> (and a huge amount of constant maintenance work) as well. ;) |
97 |
|
98 |
I think that your problem is that you are running ~arch and this comes with |
99 |
frequent updates. These days I'm running stable and my qt, kde or OOo updates |
100 |
are quite infrequent (like twice a year or may be less). |
101 |
|
102 |
I have to admit though that now the mutt can work as a multi-function client I |
103 |
am tempted to reinstall it and give it a another go ... |
104 |
-- |
105 |
Regards, |
106 |
Mick |