See "steps to reproduce" and "actual results". Reproducible: Always Steps to Reproduce: 1. Create or receive an inline PGP signed message in a folder that can be viewed from within muttng 2. Try to view the message mentioned in (1) in the muttng pager Actual Results: Message gets passed to gpg which verifies the signature and gpg output is displayed in the pager as normal, but no message content is shown. Message content still exists in mailbox on disk. Expected Results: Message content should have been shown in the pager. muttng-devel-r392 fixes this problem, and the attached ebuild updates portage to build that version instead.
Created attachment 65919 [details] Updated ebuild for muttng Should be proofread by someone familiar with portage ebuild syntax. Builds fine for me on AMD64, but no guarantees.
(In reply to comment #0) > Steps to Reproduce: > 2. Try to view the message mentioned in (1) in the muttng pager Apologizes, this is perhaps better phrased as: 2. Open message mentioned in (1) in the muttng pager 3. Execute muttng function check-traditional-pgp, manually or by message-hook
IMHO it would be foolish to apply patches locally to muttng while upstream is in snapshot phase. Instead I'll just update the snapshot in portage. muttng bumped to 20050814, enjoy!
