Richard Russon

> Unable to open mailbox /Users/ahmedelgabri/.mail You need to point it at a maildir mailbox, i.e. a directory that contains `cur`, `new` and `tmp` subdirs (and hopefully LOTS of emails)

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

> /Users/ahmedelgabri/Mail does not exist. Create it? ([yes]/no): That can be ignored

ah, no worries :-) > This command works as expected and it's fast… without any configs. Great. That's easily debug-able > I wonder what could be the culprit here that...

> `tree ...` How many mailboxes are we talking? 10s, 100s, 1000s? What are you settings for the following config? ```sh neomutt -Q check_new -Q mail_check -Q mail_check_recent -Q mail_check_stats...

> 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 processed and the...

> ... 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" "b" ...` (temporarily)...

> If I understood correctly, it should look like > > ``` > mailboxes "a" -nopoll "b" … > ``` It's a prefix option, so above the `-nopoll` affects "b"...

**Update**: Renamed functions -- Prior art in BSD. Thanks, @alejandro-colomar.

> Maybe we should also clear the freed space if new_size < cur_size? Hmm... I hadn't considered _that_. I can't actually think of any cases that we shrink an array;...