Richard Russon

Sounds like a great idea! I notice that `` does better as it relies on `iswalnum()`, not just `iswspace()`. Perhaps an easy first step would be to make the functions...

I'm reminded of a Vim internet meme from long ago: 

### Bad News OK, I've done a bit of digging, including installing Alpine and building NeoMutt under it (which was surprisingly simple). There are two problems here. First, NeoMutt doesn't...

> conventions for handling UTF-8 There are a bunch of functions in [mutt/mbyte.c](https://github.com/neomutt/neomutt/blob/main/mutt/mbyte.c) But we might not need them, if we keep the regexes. We `getch()` a number of times...

| Locale | Yes Expression | No Expression | | :---------- | :-------------------------- | :------------------------------ | | bg_BG.utf-8 | `^[+1yYdDoOДд]` | `^[-0nNkKНн]` | | ca_ES.utf-8 | `^[+1sSyY]` | `^[-0nN]` |...

Unfortunately not (and you're not the first to ask). Possible **workarounds**, change your index_format / sidebar config: - Using a `folder-hook` If, in certain folders some information is more important...

The `resize-hook` would be simpler -- we already have plenty of hooks to cut'n'paste and `SIGWINCH` (the signal sent on resize is already caught). Let me just get a second...

As for the multi-line `Menu`s... It's a great idea, but I hate to think how many 1-line assumptions have been made in the `Menu` code. I'll keep thinking and have...

Great. OK, @afh, I'm still thinking through some of the details, but here's a load to get you started. This is a **lot** to take in, so have a look...

That would be lovely, but nobody's come up with a plan of how to do it. The current doc build looks like this: (see: https://neomutt.org/dev/build/make)  (This is actually simpler...