Ahmed El Gabri

> Please can you try NeoMutt without any config, on a large mailbox, e.g. > > ```shell > neomutt -n -F /dev/null -f ~/mailbox/big > ``` When I run this...

I did both the root folder and my account folder. The result is the same. For example if I run this where personal contains all my emails. It yields the...

> er... I don't understand. Can you run that again with debugging, to see if you can find out _why_ it's failing. > > ```shell > neomutt -n -F /dev/null...

I found the issue, I didn't need to debug too much. I had a hunch because this gave me issues before too. It was `mailboxes` So I have this in...

> How many mailboxes are we talking? 10s, 100s, 1000s? 21 ~~~ $ tree ~/.mail/Work -l -d -I "Archive|cur|new|tmp|certs|.notmuch|INBOX|[Gmail]" -afinQ --noreport | awk '{if(NR>1)print}' | wc -l 21 ~~~ >...

> > set mail_check = 0 > > _That_ may be a problem. It's telling NeoMutt to check for new mail **every** loop. Every keypress is an event that is...

> > ... removing the line where it sets `mailboxes` dynamically > > We can rule this out if you evaluate this and replace it with the static `mailboxes "a"...

> i'd `dtruss` the thing, and/or run it in gdb and interrupt it during the delay - multiple times, and compare the backtraces. even just looking at `top` in parallel...

@zetashift @saadparwaiz1 you need to pass `absolute = true` & that should work. ```lua general(request, {absolute = true, args = {'--type=file', '--hidden', '--no-ignore'}, cwd = cwd}) ```

@zetashift I think if you want to change `cwd` you have to create a custom producer using the general `ripgrep.general` or `fd.general`. Or look at the example called "Search files...