Hey guys, I've noticed something that might help us solving this problem: the display gets messed up when I get on a signed message and only then ! I don't know why I missed that until now, it seems so obvious now. So I think my problem is *not* linked to the TERM variable. I'm using gnupg and the config file by default found in /usr/share/doc/mutt/examples/ from a Debian box. I copied this file in ~/.mutt/gpg.txt and sourced it in my .muttrc. I'm trying to make it work with different profiles with corresponding profiles (classical set up I guess). The display gets messed up when gnupg tries to find the public key, the bottom of the display not going up as expected (and strange caracters being displayed at random places on the screen). How could I troubleshoot this ? Thanks for the help! Le 30-11-2007, à 09:04:24 -0600, Kyle Wheeler (kyle-mutt@xxxxxxxxxxxxxx) a écrit : > Lignes : 59 > > On Friday, November 30 at 07:30 AM, quoth Steve: > > If you have an application which is supposed to use 256-colour mode > > and it isn't working, you may find you need to tell your server that > > your terminal supports 256 colours. On Unix, you do this by ensuring > > that the setting of TERM describes a 256-colour-capable terminal. > > You can check this using a command such as infocmp: > > > > $ infocmp | grep colors > > colors#256, cols#80, it#8, lines#24, pairs#256, > > If you do not see ‘colors#256’ in the output, you may need to > > change your terminal setting. On modern Linux machines, you > > could try ‘xterm-256color’. > > > > > > So I tried this commande on my linux box : > > > > infocmp | grep color > > colors#8, cols#80, it#8, lines#24, pairs#64, > > > > No "color256". Coulf this have an effect on my problem ? > > Possibly. Try setting TERM to putty-256color, or if that doesn't work, > xterm-256color. > > > I tried to run mutt in a xterm (locally) and I got exactly the same > > behaviour. And now I'm really becoming completely confused (and a > > bit frustrated: I showed mutt to a friend yesterday night, telling > > him that "All mail clients suck. This one just sucks less." but this > > problem suddenly arised, all he said is "well this one sucks > > too!"... > > Heh, I understand the frustration. :) We'll figure it out eventually. > > Anyway, hrm, if it has the same problem in an xterm, as long as your > TERM was something obvious like 'xterm', then we're dealing with > something more insidious than a bad terminal emulation... but > unfortunately we're beginning to get out of my depth. I'd say try to > reproduce the problem inside a `script` environment (i.e. run 'script' > before running mutt, and after the problem develops, close the > terminal) and post it somewhere so that people who know what's going > on can examine things more closely. > > ~Kyle > -- > We all grow up with the weight of history on us. Our ancestors dwell > in the attics of our brains as they do in the spiraling chains of > knowledge hidden in every cell of our bodies. > -- Shirley Abbott >
Attachment:
signature.asc
Description: Digital signature