On 20201126, tech-lists wrote:
Right now I don't know if the old mutt to new mutt is the cause or if there's
been a change that they at the mail hosting have done which has occurred
at the same time as mutt v1 -> mutt v2. It might not be an issue with
mutt at all.
There was a warning that the
On Thu, Nov 26, 2020 at 04:03:53PM -0800, Kevin J. McCarthy wrote:
I'd normally say to double check $imap_check_subscribed is unset, but
that option is quite old. Perhaps something has changed in the code
there, but I'm not recalling anything right now.
Well, you were right, it was enabled!
On Thu, Nov 26, 2020 at 11:48:28PM +, tech-lists wrote:
What was happening before (mutt v.1.x) was mutt would log in, scan the
imap folders i'd configured for it in .muttrc-lists (and *only* those
folders, no others) then return and this was quick on an average dsl
line.
What is
Hi,
I *think* i've found the reason for the lagginess. Hopefully what's here will
be of use to others.
With mutt, for this address I make a config file, launch mutt in a screen with
-F.
On the remote system, I have a lot of different folders which I'll use
with different email addresses.
Hi,
ktrace shows (as best I can interpret it) when mutt is "woken up"
it re-uses the connection to the imap server somehow. It's
exchanging information, not sure what. But it's a big
segment like a half page full in kdump. So maybe the answer is in
idle parameters. I'll re-do the muttrc with
On Thu, Nov 26, 2020 at 10:34:30AM +1100, Cameron Simpson wrote:
Probably. I don't have a FreeBSD box to hand. Is yours a Raspberry?
yup, rpi4 with 8GB
Have you got ktrace and kdump? Less interactive, but IIRC the process is
to ktrace your mutt command and kdump the resulting log file.
I
On 25Nov2020 22:33, tech-lists wrote:
>On Thu, Nov 26, 2020 at 09:01:03AM +1100, Cameron Simpson wrote:
>>A way to check this would be to have another window open running:
>>
>> strace -p pid-of-idle-mutt-process
>>
>>Get that ready. Wait for idleness. Resume. See where it stalls.
>>
>>If that
On 25Nov2020 17:56, Patrick Shanahan wrote:
>* tech-lists [11-25-20 17:55]:
>> On Wed, Nov 25, 2020 at 05:43:21PM -0500, Patrick Shanahan wrote:
>> > possibly reinstall strace. for my openSUSE Tumbleweed system I
>> > show: strace-5.9-1.1.x86_64
>> >
>> > your version is quite old and version
* tech-lists [11-25-20 17:55]:
> Hi,
>
> On Wed, Nov 25, 2020 at 05:43:21PM -0500, Patrick Shanahan wrote:
>
> > possibly reinstall strace. for my openSUSE Tumbleweed system I show:
> > strace-5.9-1.1.x86_64
> >
> > your version is quite old and version number appear to reflect the kernel
>
Hi,
On Wed, Nov 25, 2020 at 05:43:21PM -0500, Patrick Shanahan wrote:
possibly reinstall strace. for my openSUSE Tumbleweed system I show:
strace-5.9-1.1.x86_64
your version is quite old and version number appear to reflect the kernel
version. what kernel are you running, 4.5.x ??
I'm
IIRC I just went with the ports/mail/mutt defaults.
I selected ispell because I'm more used to the ispell interface.
Now-a-days it's all aspell under the covers.
On Wed, Nov 25, 2020 at 10:19:57PM +, tech-lists wrote:
> Hello,
>
> On Wed, Nov 25, 2020 at 09:59:30AM -0600, Hokan wrote:
>
>
* tech-lists [11-25-20 17:36]:
> Hi,
>
> On Thu, Nov 26, 2020 at 09:01:03AM +1100, Cameron Simpson wrote:
> > A way to check this would be to have another window open running:
> >
> >strace -p pid-of-idle-mutt-process
> >
> > Get that ready. Wait for idleness. Resume. See where it stalls.
Hi,
On Thu, Nov 26, 2020 at 09:01:03AM +1100, Cameron Simpson wrote:
A way to check this would be to have another window open running:
strace -p pid-of-idle-mutt-process
Get that ready. Wait for idleness. Resume. See where it stalls.
If that is hard to observe interactively, strace has
Hello,
On Wed, Nov 25, 2020 at 09:59:30AM -0600, Hokan wrote:
I am running a month-old FreeBSD-CURRENT on an RPI-4 (8GB) and could not
replicate the problem.
thanks for posting yr config.
Your mutt is compiled just slightly differently:
hcache backend: Berkeley DB 5.3.28: (September 9,
On 25Nov2020 14:19, tech-lists wrote:
>I'm finding mutt significantly more laggy to resume on later
>versions (=>2.x) than say 1.5.21.
>
>Let's say there's the list of emails in a folder already selected. If
>I use up or down arrow for example, it'll sit for 3-4 seconds doing
>nothing and then
I am running a month-old FreeBSD-CURRENT on an RPI-4 (8GB) and could not
replicate the problem.
Mutt 2.0.2 (2020-11-20)
Copyright (C) 1996-2020 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to
16 matches
Mail list logo
