I have mutt-1.4-r3 but the messages don't show up, only their title (see following screenshots). Someone on the mailing list suggested to remove slang USE="-slang" emerge mutt But that didn't help. I first thought it was a foreground color == background color issue but playing with gpm showed that it's not the case. gpm's selection is correctly visible which means that foreground != background (gpm's selection inverses foreground and background). More over, when I try to paste the selection somewhere it doesn't show the message which means that there is no message on the screen. Pasting the menubar (which is visible) works. The screenshots below show a personnal .muttrc in color because it shows the problem a little more cleary I think. My .muttrc doesn't change anything except the colors. If I don't use a .muttrc (default config), I still have the exact same problem except that it's in black and white.
Created attachment 7481 [details] Main screen showing the problem
Created attachment 7482 [details] Message screen
I've been giving more thoughts to my problem. When I compile I get some warnings about "implicit declaration of function" for functions like iswprint, iswspace, towlower,... . I manually run the configure application adding the parameter --without-wc-funcs and now I get the text correctly. The weird thing is that the normal configure did say that those functions exist. How come configure detect them but the compilation phase doesn't find them?
I'm observing the same bug with both ncurses and slang version and both terminal and xterm. Probably not coloring problem - text cannot be clipped. Taking another binary dynamically linked in different Linux with the same options, all works OK.
I added --without-wc-funcs to the .configure command in the mutt-1.4.1.ebuild, remerged, and voila! It works now!! I've been waiting to use mutt for months now! Thanks guys!
In installed the latest version (1.4.1) and it worked out of the box. While it was compiling, I saw one warning about an implicit declaration for one of the function but I didn't look to see if they were other.
Reporter says this works now with 1.4.1 which is in portage, so I'm closing this bug.
mutt 1.4.1 does NOT solve this problem. Still showed up here with mutt 1.4.1, glibc 2.2.5-r8, slang 1.4.5-r2. Adding --without-wc-funcs to the ebuild fixed it.