Richard Russon

Yes, I see that. What's displayed is always one step behind. ``, `` shows that the calculations are working, but the refresh isn't.

**Update**: I'd hoped there would be a quick fix for this, but it's a little more involved. The Pager doesn't have a clean divide between the code that calculates the...

It's a reasonable request, but it's a little tricky. Behind a simple `mutt_debug()` is quite a lot of machinery. Firstly, `mutt_debug()` and friends are macros. They're defined to include `__FILE__`,...

If you want something simple, like: ```c struct Buffer *msg; mutt_debug_buffer(LL_DEBUG1, msg); ``` Then we can probably get away with: ```c #define mutt_debug_buffer(LEVEL, BUF) MuttLogger(0, __FILE__, __LINE__, __func__, LEVEL, "%s",...

I've just fixed a few typos

> suddenly appeared an error messages That's because I accidentally cut'n'pasted some **error** log levels. I've fixed the param to `LEVEL`, now.

> (Removing globals might be worth some effort. in general in neomutt...) Yes and no. There are still lots to eliminate, but `MuttLogger` needs to be global. > A "\n"...

Sample code ```c struct Buffer buf = mutt_buffer_make(256); mutt_buffer_strcpy(&buf, "hello %d world\n"); mutt_debug_buffer(LL_DEBUG1, &buf, 42); mutt_buffer_dealloc(&buf); ```

(Sorry for the slow reply, I've been on holiday) Hmm... I don't see this problem. I've just tried edb4b93af and main (9639bfaf3) and the history seems to work correctly. With...

Hmm... A lot of the colour code has been re-written recently. There are still a few quirks, though. When this happens, does Ctrl-L refresh everything correctly? If not, try opening...