Ok Thanks.
On 2017-10-25 20:48, David Woodfall wrote:
Yes I have shell access. I have tried just setting mutt without imap
to use maildir, but It only sees my Inbox and no other folders.
Perhaps there's a way of doing it but I haven't managed yet.
Sync the store to your local box by other
On 2017-10-25 20:48, David Woodfall wrote:
> Yes I have shell access. I have tried just setting mutt without imap
> to use maildir, but It only sees my Inbox and no other folders.
> Perhaps there's a way of doing it but I haven't managed yet.
Sync the store to your local box by other means (see
No unusual headers. But I tried the options on that webpage and it
seems to have improved. Thanks.
On Di, 24 Okt 2017, David Woodfall wrote:
I've been using mutt a fair while now. Lately I've been using it with
imap and find that it can take a while to read headers.
Are there any tricks to
On 17-10-25 09:41:23, Christian Brabandt wrote:
> Also you might want to check this article:
> http://www.codeblueprint.co.uk/2016/12/19/a-kernel-devs-approach-to-improving.html
Nice, thanks for sharing!
Cheers,
Georg
signature.asc
Description: Digital signature
Yes I have shell access. I have tried just setting mutt without imap
to use maildir, but It only sees my Inbox and no other folders.
Perhaps there's a way of doing it but I haven't managed yet.
On 2017-10-24 18:43, David Woodfall wrote:
I've been using mutt a fair while now. Lately I've been
On Di, 24 Okt 2017, David Woodfall wrote:
> I've been using mutt a fair while now. Lately I've been using it with
> imap and find that it can take a while to read headers.
>
> Are there any tricks to speeding up imap?
>
> I do have a header cache, but it still takes some time opening a
>
On 2017-10-24 18:43, David Woodfall wrote:
> I've been using mutt a fair while now. Lately I've been using it with
> imap and find that it can take a while to read headers.
>
> Are there any tricks to speeding up imap?
Is IMAP a hard requirement? Do you have shell access to the server?
--
I don't know if it's an option for your situation, but you might
consider offlineimap. For a folder of size about 1000, it took 2 seconds
to open it. Of course, this is after using offlineimap to download the
messages locally.
Scott
--
Scott Kostyshak
Assistant Professor of Economics
Thanks I'll give that a shot.
On Tue, Oct 24, 2017 at 06:43:03PM +0100, David Woodfall wrote:
I've been using mutt a fair while now. Lately I've been using it with
imap and find that it can take a while to read headers.
Are there any tricks to speeding up imap?
I do have a header cache, but
On Tue, Oct 24, 2017 at 06:43:03PM +0100, David Woodfall wrote:
> I've been using mutt a fair while now. Lately I've been using it with
> imap and find that it can take a while to read headers.
>
> Are there any tricks to speeding up imap?
>
> I do have a header cache, but it still takes some
Thus spake Rocco Rutte [05/21/08 @ 09.18.56 +0200]:
* [EMAIL PROTECTED] wrote:
Thus spake Rocco Rutte [05/15/08 @ 16.16.10 +0200]:
http://dev.mutt.org/trac/ticket/2978
I just downloaded the source and built. I don't use macports at all.
BerkeleyDB compiles flawlessly on Panther and
Hi,
* [EMAIL PROTECTED] wrote:
Thus spake Rocco Rutte [05/15/08 @ 16.16.10 +0200]:
http://dev.mutt.org/trac/ticket/2978
I just downloaded the source and built. I don't use macports at all.
BerkeleyDB compiles flawlessly on Panther and Tiger for me.
Good, thanks for the feedback.
Thus spake Rocco Rutte [05/15/08 @ 16.16.10 +0200]:
* [EMAIL PROTECTED] wrote:
FWIW: I built using the BerkeleyDB libraries, since the other choices
refuse to work with OSX. (Actually, I finally got mutt to build with gdb,
but mutt behaved *really* weird with screen-drawing, so gdb is a
Hi,
* [EMAIL PROTECTED] wrote:
FWIW: I built using the BerkeleyDB libraries, since the other choices
refuse to work with OSX. (Actually, I finally got mutt to build with
gdb, but mutt behaved *really* weird with screen-drawing, so gdb is a
no-go on OSX).
How do you do that exactly? qdbm
[...]
That's why they recently added $time_inc (it's not in a released
version of mutt yet; just in the current development tree). Here's the
description from the development manual:
Sweet. My INBOX opens nearly instantaneously now. And I thought that
it's the hcache being slow.
Thank you
* [EMAIL PROTECTED] on Saturday, May 10, 2008 at 18:07:04 -0400
1.5.17 with header caching enabled. I've got read_inc and
write_inc set to 1000. Nevertheless, I've noticed that the
process of evaluating the cache (when I switch into a big
folder) is significantly slower when I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, May 10 at 06:07 PM, quoth [EMAIL PROTECTED]:
1.5.17 with header caching enabled. I've got read_inc and write_inc
set to 1000. Nevertheless, I've noticed that the process of
evaluating the cache (when I switch into a big folder) is
* [EMAIL PROTECTED] [EMAIL PROTECTED] [05-10-2008]:
1.5.17 with header caching enabled. I've got read_inc and write_inc
set to 1000. Nevertheless, I've noticed that the process of
evaluating the cache (when I switch into a big folder) is
significantly slower when I use Terminal.app
On 2001-08-22 17:01:40 +0200, Alexander Skwar wrote:
Also the load when opening the Maildir is WAY higher compared to
the mbox file. Load when opening the mbox is about 2, Maildir is
about 6. Okay, I've got setiathome running, so one may substract 1
(? right?).
Ouch. PLEASE make sure that
On 23.08.2001 10:45:25 Thomas Roessler wrote:
Ouch. PLEASE make sure that (1) swapping isn't necessary, (2) your
CPU is mostly idle when you do measurements, (3) mutt (or, for that
matter, evolution) is the only process which competes for disk
access.
Yes, I do know this. But, the system
So sprach »Thomas Roessler« am 2001-08-23 um 10:45:25 +0200 :
On 2001-08-22 17:01:40 +0200, Alexander Skwar wrote:
[ mutt 1.3.19i ]
MUCH longer, to be exact, it took about 2 minutes 30 seconds.
Try a newer version. Someone has contributed a patch which improves
mutt's threading algorithm
On 2001-08-21 23:02:13 +0200, Alexander Skwar wrote:
While on the topic of Maildir. I also just recently checked out
Maildir support in mutt 1.3.19i again. And, well, I'm not at all
impressed :( To test, I've converted a 50 MB mbox with ~5000
messages to Maildir. Opening the mbox in mutt
So sprach »Thomas Roessler« am 2001-08-22 um 10:23:05 +0200 :
Did you do the mutt test several times, so kernel caches could kick
in?
No, I did not. But in Evolution it's also very fast the very first time
a Maildir is opened.
Alexander Skwar
--
How to quote: http://learn.to/quote
On 2001-08-22 13:50:42 +0200, Alexander Skwar wrote:
No, I did not. But in Evolution it's also very fast the very
first time a Maildir is opened.
Right after you read it with mutt? I'm not talking about mutt
caches, but about operating system caches.
Please perform the timing experiment
So sprach »Thomas Roessler« am 2001-08-22 um 14:04:14 +0200 :
Please perform the timing experiment with both mutt and Evolution
several times, without doing much in between.
Timing sheet:
Mailer| Action | Time
--+-+--
On 2001-06-15 12:31:30 -0600, Troy Heber wrote:
If I select the text portion of the message and press enter it
comes up instantly. However, when I select the message and press
enter from the main inbox (I think it's called the pager or the
inbox) it takes 4 minutes 28 seconds! If I press Q to
On Fri, Jun 15, 2001 at 12:31:30PM -0600, Troy Heber wrote:
I'm running mutt 1.2.5i and I am experiencing a very strange problem.
When I attempt to read messages from certain senders it takes minutes to
display the message. For example if I press v on the message to see the
attachments it
Thanks for the suggestion, but I complete disabled all of my autoviews (I never
had any for this MIME type anyway) and that did not resolve the problem.
Any other suggestions?
Thanks,
Troy
On 06/15/01, Hanif Ladha wrote:
On Fri, Jun 15, 2001 at 12:31:30PM -0600, Troy Heber wrote:
I'm
28 matches
Mail list logo
