Bug#991873: neomutt: Input fields are left when backspacing in position 0
Hi Markus, set abort_backspace = no will stop this new feature. It was introduced to make the input field work more like vim's. > clear the To: field using backspace (or ^U) As you've discovered, many Readline commands are supported, for navigation, text clearing, etc: https://neomutt.org/guide/gettingstarted#4-%C2%A0editing-input-fields Cheers, Rich / FlatCap signature.asc Description: PGP signature
Bug#857687: closed by Antonio Radici <anto...@debian.org> (Bug#857687: fixed in mutt 1.8.0-1)
Hi Ivam > the problem with the password field is still present. Argh! Sorry, that's my fault. The release was good, but I messed up the diff somehow. I've regenerated the diff and uploaded it. https://github.com/neomutt/neomutt/releases/download/neomutt-20170306/neomutt-20170306.diff.gz sha256sum: da0c1ac6c656b1a3c8140d1c687249a15bb61a1d3b021b4a413259274b74207f neomutt-20170306.diff.gz This one applies cleanly and includes the password fix. I've checked. Sorry, Rich / FlatCap (NeoMutt maintainer/packager) signature.asc Description: PGP signature
Bug#857433: mutt: Garbage in chdir prompt due to unescaped string
Hi Guillem, > I tracked it down to an unescaped string handling. > Attached a patch fixing the issue. Thanks for the bug report and thank you very much for the fix. I've tidied the surrounding code a little and tested your fix. You can follow its progress in the pull-request: https://github.com/neomutt/neomutt/pull/463 Cheers, Rich / FlatCap signature.asc Description: PGP signature
Bug#837982: mutt: sort order different in sidebar
Hi Philipp, > The IMAP folders in the sidebar are ordered differently than those in the > browser (sorted alphanumerically, of course) Ah, good. A nice easy, entertaining bug :-) I've changed the Sidebar to "collate" the strings, rather than just "sort" them. This is what the browser does. This is fixed in NeoMutt commit: 5e146b1 Rich / FlatCap NeoMutt maintainer signature.asc Description: PGP signature
Bug#837045: mutt: wrong handling of symbol '>' in conditional expression
Hi Andrey, Thanks for the bug report. > The problem is in part '%?M?<%M> ?'. Number of hidden messages in thread are > only shown it thread is collapsed, like this '<10>'. This is a known issue which comes from the "nested-if" patch. Mutt allows you to nest conditionals, but the syntax is very scary -- requiring a LOT of escaping. The solution was nested-if, which introduces the %<> notation. I've attempted to document it, here: http://www.neomutt.org/feature/nested-if/ I haven't decided how to fix this problem, yet, so you have two options. Escape the <> chars, or choose different ones. The upstream (NeoMutt) bug is tracked, here: https://github.com/neomutt/neomutt/issues/113 Cheers, Rich / FlatCap NeoMutt maintainer signature.asc Description: PGP signature
Bug#834903: mutt: No news server defined!
Hi Kurt, > I regularly get to see this message: > No news server defined! That's from the NNTP patch. It mapped the 'i' key to look for news servers. > I never get that before, it started showing up recently. Debian recently adopted the NeoMutt patches and we're still ironing out some problems. NeoMutt 2016-08-20 was released this morning and removes the problem keymappings. It'll probably be available very soon. Rich / FlatCap NeoMutt Maintainer signature.asc Description: PGP signature
Bug#834818: mutt: Saving a mail into a compressed mbox deletes all existing mails in this mbox
Hi Stephan, Thanks for the bug report. > Severity: critical > Justification: causes serious data loss I'm really sorry to hear that. > I had to restore the mbox from backup. I'm glad you had the backup. > It doesn’t matter if your mbox is compressed with xz or gzip. > I can always reproduce this bug Me, too. This is fixed in commit: https://github.com/neomutt/neomutt/commit/9f06971bc0a1de06ef2db8d3d3f51baf0a2370dc This will be included in the next release of NeoMutt. The release was planned for today, but it's likely to be tomorrow. Rich / FlatCap NeoMutt Maintainer signature.asc Description: PGP signature
Bug#834408: mutt: segfault/crash on displaying attached message
Hi Andreas, Thanks for the detailed bug report -- that's made it very quick to track down the problem. > mutt crashes when trying to display attached message. A quick test shows that this bug was introduced with the first version of NeoMutt, 6 months ago! The problem is caused by the "fmemopen" patch, but I don't yet know why. Fortunately, you can disable this patch at compile time: ./configure --disable-fmemopen I'll keep looking for the cause and let you know. Cheers, Rich Russon NeoMutt maintainer signature.asc Description: PGP signature
Bug#834024: mutt: "double free or corruption" when closing a compressed mbox
Hi Berto, Thanks for the bug report. > mutt is crashing with compressed mbox files. I think this is quite > recent since I use these often and I only noticed the crash now. Hmm... I fixed something like this recently. And, I can't reproduce it in the latest version. I saw a lot of version info, but not that of mutt/neomutt. mutt -v | head -n 1 Known broken: Mutt 1.6.2-neo (2016-07-23) Latest version: Mutt 1.6.2-neo (2016-08-08) If you're able, please give this a try. Cheers, Rich / FlatCap NeoMutt Maintainer signature.asc Description: PGP signature
Bug#832971: It is not possible to reset X-Labels
Hi Klaus, I'm Rich/FlatCap -- Maintainer of NeoMutt. I've just tested the labels and they work for me. There seem to be a LOT of quotes in your config example. I've removed a few and everything works as expected: ifdef edit-label "macro index 'M0' '^U!' 'Clear priority (X-Label) of message'" In this email I've typed out ^U as two separate characters, but in the config file it's the literal character -- kill line. Please can you try this config and let me know if it works. Cheers, Rich signature.asc Description: PGP signature
