Re: Problem with color
Submitted 04-Aug-00 by Ben Roberts: > I'm trying to compile mutt 1.2.5i on RedHat 6.0 with either ncurses or slang, I > don't care. I just want color! RedHat's mutt versions don't have color They don't? That's odd. Every single version that I know of has had color support; you may want to check your terminfo settings, or try setting some colors in your .muttrc. Bill
Re: Problem with color
Submitted 04-Aug-00 by Ben Roberts: > I'm trying to compile mutt 1.2.5i on RedHat 6.0 with either ncurses or slang, I > don't care. I just want color! RedHat's mutt versions don't have color If you're running a Pentium or higher, (I'm assuming x86 architecture here :/) you might want to try grabbing the Mandrake package (from the "Cooker" mirrors). It is compiled with color support. -- _ _|_|_ ( ) *Anton Graham /v\ / <[EMAIL PROTECTED]> /( )X (m_m) GPG ID: 18F78541 Penguin Powered!
Problem with color
I know this is a FAQ, but I tried everyhting in the FAQ itself and I couldn't solve my problem. I'm trying to compile mutt 1.2.5i on RedHat 6.0 with either ncurses or slang, I don't care. I just want color! RedHat's mutt versions don't have color and so I tried compiling it from the tarball on mutt.org. It compiles and runs fine, but no color. Just black text on white background for any library, any #defines I manipulate in acconfig.h, any terminal mode I want including linux, nothing seems to work. after configure runs, config.h includes HAVE_COLOR #defined in it. So I know configure is working, and checking the source (specifically color.c) I don't know what could not be working here. I also tried compiling with slang and setting COLORTERM; no such luck. Maybe I should just sneak onto the system in the middle of the night and install Debian; it has a color mutt package :-) On that topic, I have been able to get mutt to display color on the same terminal on the same machine with the same $TERM when logged into my home machines with Debian and mutt. I also just tried upgrading to ncurses 5.0 in case there was some incompatibility; didn't work. - Ben Roberts, Class of 2001 (1st of millenium), founding member of MBLUG "If your motherboard smells like carcinogens it's time to get a new motherboard." -- Ben Roberts, refering to his SPARC
Re: mime viewer
Le mar 01 aoû, 2000 à 06:38:12 -0400, David T-G dit : > From: David T-G <[EMAIL PROTECTED]> > To: "Mutt Users' List" <[EMAIL PROTECTED]> > Subject: Re: mime viewer > > ...and then J-C Hendrickx said... > % I receved a mail from a Mac OS, with an attachment file > % that Mutt recognise as : > % Image 2 [image/x-pict, base64, 174k] > % > % My question is how can I see this image ? > % Mutt show it as a text data. > > You need, of course, to get a program that can view it; in the absence of > anything that will work, mutt will let you look at the item in its > encoded form. > > You might try ImageMagick; it works for darned near everything. > HTH & HAND > -- > David T-G * It's easier to fight for one's principles > (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie > (work) [EMAIL PROTECTED] > http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! > The "new millennium" starts at the beginning of 2001. There was no year 0. > Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* > Hello, Thanks to people who answered me. Searching 'ImageMagick', I came accros with picttoppm - convert a Macintosh PICT file into a portable pixmap It works fine when I configure mailcap as : 'image/x-pict; picttoppm -fullres '%s' | xv - So, searching may lead to inexpected good results :-) Bye, -- --_- (o-Jean-Claude Hendrickx //\[EMAIL PROTECTED] v_/_
Re: Configuring Mutt Dialup Modem Connection ?
On Thu, Aug 03, 2000 at 05:19:55PM -0400, Roger Gordon wrote: > Hello all! I'm new to the Mutt users list. And I have some > configuration questions about Mutt for use with the Vim editor to > compose messages, then send them off using with sendmail over a dial up > network connection. I have the /etc/Muttrc configuration working ok for > use with pop mail server and it retreives then just fine. But composing > a message with Vim creates an error bouncing messages due to incorrect > date and localhost error that doesn't exist over the modem connection. > At first, it could be interessant to fix if the problem comes from the sendmail configuration, from Mutt or Vim. Being off-line, try to send a message to your own adress by your ISP with the archaic "mail" commmand : [id@yourmachine]$ mail [EMAIL PROTECTED] Subject: test some words . Cc: (message is closed when you insert a single point at beginning of line) Then, if sendmail is running (!) and correctly configured, this message will be waiting in the "queue" : [id@yourmachine]]$ mailq Mail Queue (1 request) --Q-ID-- --Size-- -Q-Time- Sender/Recipient IAA003976 Fri Aug 4 08:41 id [EMAIL PROTECTED] It will leave at your next connection. Try also to send a message to your_user_name@localhost : if all is correct with sendmail, the message will be delivered immediately without trying to transit via "external world". Configuring sendmail is a real headache. Have you done it, or are you using a "out-the-box" /etc/sendmail.cf ? One thing at a time ! Regards, Gauthier
Re: Configuring Mutt Dialup Modem Connection ?
Roger Gordon muttered: > Hello all! I'm new to the Mutt users list. Welcome! > And I have some configuration questions about Mutt for use with the > Vim editor to compose messages, then send them off using with > sendmail over a dial up network connection. I have the /etc/Muttrc > configuration working ok for use with pop mail server and it > retreives then just fine. But composing a message with Vim creates an > error bouncing messages due to incorrect date and localhost error > that doesn't exist over the modem connection. Set your ISP's SMTP host as smart host in /etc/sendmail.cf (DSmail.isp.com) and set $envelope_from in your muttrc. See mutt's manual for details. HTH, Michael -- A modem is a baudy house. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: [OT] Re: Anyone has a good mailcap RunningX test?
On Fri, Aug 04, 2000 at 12:42:59AM +0300, Mikko H?nninen wrote: > Jan Houtsma <[EMAIL PROTECTED]> wrote on Thu, 03 Aug 2000: > > Only thing that works is manually unsetting $DISPLAY. > > Having $DISPLAY defined usually means that there's an X session running. > Why do you have it defined anyway (in that telnet session) if you're not > doing stuff from inside an X environment? I'd look into fixing whatever > is setting that environment variable for your telnet session... > Yes you are completely right. Thats exactly what i overlooked. I wasn't aware that it was set from my /etc/zshenv file and i have no idea why i ever put it in there anyways (must have been years ago already). I removed it and now its fine. Thanks, jan
