Re: Ideal 'xterm' for mutt/vim combination...
On Wed, Apr 18, 2001 at 01:56:54PM -0400, Thomas E. Dickey wrote: On Wed, 18 Apr 2001, Hanif Ladha [4355] wrote: Dear Muttophiles, I am in search for an ideal (yep very subjective i know) 'xterm' that will let me to setup pretty colours for mutt/vim combination. I am running Solaris 8 on a Ultrasparc 5 (very nice machine BTW), alas it only has a 4Mb frame bugger card so I am stuck with 8-bit color (I need the high res.) I am running CDE (the other choice I had was OpenWindows - this I understand may not be supported in future releases of Solaeis - so I was required to use CDE). Under CDE I have access to dtterm, which is okay for color display of mutt/vim. I would like to use say xterm (by dickey) or rxvt. Alas I am having difficulty in getting color on them (need to do more digging). If you got them to compile/run, then they both are ready to do color. Likely the problem is that the $TERM is set to 'xterm', which normally is installed as a non-color terminfo entry. (XFree86 xterm comes with a terminfo file which can be compiled using "tic", and would overwrite the "xterm" terminfo entry with a link to "xterm-xfree86"). I'm running mutt in rxvt windows on Solaris (2.6 at the moment) and have got colours set up OK. It did take a bit of fiddling about to get it all to work correctly though. Feel free to E-Mail me direct if you want more information. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Ideal 'xterm' for mutt/vim combination...
I'm using xterm XFree86 3.3.6(88c) currently, with $TERM set to xterm-xf86-v33 from ~/.Xresources: #ifdef COLOR *customization: -color XTerm*termName: xterm-xf86-v33 #endif Works like a charm. -- Thomas Roessler [EMAIL PROTECTED]
Re: Orphaned tmp files?
* Rich Lafferty [EMAIL PROTECTED], 2001-04-19 09:53 +0200: On Thu, Apr 19, 2001 at 12:10:54AM -0400, Wade A. Mosely ([EMAIL PROTECTED]) wrote: I've noticed mutt files building up in /tmp too. I use vim for the editor, and nobackup seems to be the default. In any case, I have nobackup set, but I still get the files accumulating in /tmp so I'm not sure what the story is about that. I've seen that constantly in the couple of years I've been using mutt. They're not emacs backup files (no tilde); I've just left it up to the tmp cleaner. -Rich I had this "problem" too, it's gone since I've set "nobackup" expilcitely. Here's my complete setting for Vim 5.7, as reference: set editor="vim -c 'set nobackup' -c 'set tw=72 et' -c 'syn on' '+/: $'" Andre Berger[[EMAIL PROTECTED]] PGP signature
Re: Orphaned tmp files?
Rich Lafferty [EMAIL PROTECTED], 2001-04-19 09:53 +0200: They're not emacs backup files (no tilde); On Thu, Apr 19, 2001 12:36:31PM +0200, Andre Berger ([EMAIL PROTECTED]) wrote: set editor="vim -c 'set nobackup' -c 'set tw=72 et' -c 'syn on' '+/: $'" Given that (1) they're not backup files from my editor, and (2) I don't use vi, I don't think that's going to help much. -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
temporarily reply with all headers
I need an advice how I would best do this: 0. default is: take all headers out 1. for a mailinglist reply to mailinglist [EMAIL PROTECTED] -. put all headers in the beginning -. then reply blahblah I need this only in some very special cases to track some bouncing which should not occur. So I would like not to do any big changes in my rc files. Any suggestions how to accomplish that best? Thanks. -- Erika
Re: Orphaned tmp files?
* Rich Lafferty [EMAIL PROTECTED], 2001-04-19 16:33 +0200: Rich Lafferty [EMAIL PROTECTED], 2001-04-19 09:53 +0200: They're not emacs backup files (no tilde); On Thu, Apr 19, 2001 12:36:31PM +0200, Andre Berger ([EMAIL PROTECTED]) wrote: set editor="vim -c 'set nobackup' -c 'set tw=72 et' -c 'syn on' '+/: $'" Given that (1) they're not backup files from my editor, and (2) I don't use vi, I don't think that's going to help much. Yes. You could try to set the tmp path explicitely and see what happens? Andre Berger[[EMAIL PROTECTED]]
Re: temporarily reply with all headers
You can hit 'h' within pager window to see the full message header. Is that what you are talking about ? igor On Thu 19 Apr 2001, Erika Pacholleck wrote: I need an advice how I would best do this: 0. default is: take all headers out 1. for a mailinglist reply to mailinglist [EMAIL PROTECTED] -. put all headers in the beginning -. then reply blahblah I need this only in some very special cases to track some bouncing which should not occur. So I would like not to do any big changes in my rc files. Any suggestions how to accomplish that best? Thanks. -- Erika
Re: Orphaned tmp files?
* Duke Normandin [EMAIL PROTECTED] [2001-04-18, 21:14 -0600]: On Wed, Apr 18, 2001 at 09:58:58AM -0400, Jim Lambert wrote: I've noticed that mutt occasionally forgets to clean up tmp files. It seems to be an intermittent problem and I was wondering if other users had seen it. -Jim I have exactly the same problem using Joe as my editor, which BTW, is set to make no backups. Sometimes the Mutt temp. files are empty, and at other times they contain the entire message. When the file contains an entire message, is it one that you have viewed in a pager (internal or external?) or one that you have composed in your editor? I had the problem that every message viewed in the pager got left behind when I run Mutt on MS Windows'2000. (and, if i recall, the same happened with cygwin if the temp directory was on a fat drive but not when it was on an ntfs drive) Since it was very consistent it might not be the same, but it seemed as if unlink misbehaved when unlinking open files. A small change in pager.c to not unlink until after the file is closed solved my temp-file mysterium. /Ulf
Re: temporarily reply with all headers
* Igor Pruchanskiy [[EMAIL PROTECTED]] on [19-04-01] wrote: You can hit 'h' within pager window to see the full message header. Is that what you are talking about ? I do not think that is what is needed in this case. Try using the "weed" variable. Do the following 1. ":unset weed" 2. forward/reply to message 3. ":set weed" Brian. -- Brian Foley -- [EMAIL PROTECTED] -- www.maths.tcd.ie/~brianf Visit the Intervarsity Track Field web-site: www.iv2001.com
Re: Ideal 'xterm' for mutt/vim combination...
On Thu, Apr 19, 2001 at 08:53:26AM +0100, Chris Green wrote: I'm running mutt in rxvt windows on Solaris (2.6 at the moment) and have got colours set up OK. It did take a bit of fiddling about to get it all to work correctly though. Feel free to E-Mail me direct if you want more information. I find that the XFree86 xterm works better for mutt (also Solaris 2.6), as the xterm provides the graphical characters which make threading look a lot nicer - I haven't seen that working in a rxvt so far. Cheerio, Thomas -- - Thomas Ribbrock http://mutt.linuxatwork.at (mutt RPMs) http://www.bigfoot.com/~kaytanICQ#: 15839919 "You have to live on the edge of reality - to make your dreams come true!"
Re: Ideal 'xterm' for mutt/vim combination...
On Thu, Apr 19, 2001 at 10:28:36PM +0200, Thomas Ribbrock wrote: I find that the XFree86 xterm works better for mutt (also Solaris 2.6), as the xterm provides the graphical characters which make threading look a lot nicer - I haven't seen that working in a rxvt so far. I get the same graphical characters in rxvt as I do in xterm (this is under XFree on Linux). -- Luke
Re: Ideal 'xterm' for mutt/vim combination...
On Thu, Apr 19, 2001 at 03:47:30PM -0700, Luke Ravitch wrote: On Thu, Apr 19, 2001 at 10:28:36PM +0200, Thomas Ribbrock wrote: I find that the XFree86 xterm works better for mutt (also Solaris 2.6), as the xterm provides the graphical characters which make threading look a lot nicer - I haven't seen that working in a rxvt so far. I get the same graphical characters in rxvt as I do in xterm (this is under XFree on Linux). it depends on the font (not all have line-drawing characters, xterm provides them if they're not available) -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: vim and a junk sig
Joe Rice wrote: hi, I'm using vim as the editor for mutt. just recently i started to get this huge line of random characters at the bottom of all the email i compose. This had never happened before. I upgraded vim to the latest version thinking it had something to do with "Malicious embedded VIM control codes". the problem still persisted. I then upgraded mutt to 1.3.17i and it is still happening. I've never used a sig and i don't have any thing in my .muttrc that would include one. If anyone can help solve this problem i would appreciate it. Thanks joe I believe the $signature variable defaults to "~/.signature" if you have not specified something else. Have you checked to see if somehow you or something has created a ~/.signature file, perhaps unintentionally? -- Mr. Wade -- Linux: The Choice of the GNU Generation
