Mutt stops showing mail contents

Josef Wolf jw at raven.inka.de
Tue Dec 22 19:32:06 UTC 2020


On Tue, Dec 22, 2020 at 04:58:53PM +0100, Matthias Apitz wrote:
> And what is this repeated asking with lseek(2) from line 22 to 89 in
> both cases with
> 
> 22617 lseek(4, 0, SEEK_CUR)    = 4096
> 
> always getting "yes, next byte to read is number 4096" I don't know where
> maildir files in mutt are handled.

As I wrote in my prevous post, this are 68 invocations to lseek() and the mail
file contains 68 header lines. I guess those lseek() calls are somewhere deep
inside fgets() which mutt uses to read the header line-by-line.

In the good case, mutt rewinds and reads the whole file again. In the bad case
mutt gives up.

-- 
Josef Wolf
jw at raven.inka.de


More information about the Mutt-users mailing list