Re: forcing mutt to think in mono
On Fri, Jun 28, 2002 at 09:02:42PM -0500, David T-G wrote: Hi! ...and then William Park said... % % On Fri, Jun 28, 2002 at 08:44:09PM -0500, David T-G wrote: ... % For one, now mutt insists on being all colorful, which just sucks for me. % Is there any way to force mutt into mono mode? % % Mutt defaults to colour in Linux too. So, copy over your .muttrc to new % machine. No dice; I did (and found that BSD regexps are different from GNU regexps, so I had to rewrite some of it -- and I've added this color junk, too!). I found that some of this (for me) was due to a new /etc/xemacs when I upgraded. Is your editor doing new colorization stuff? Adam
Re: Signature
and how would I go about doing this? [05/07/2002] - Michael Tatge - [mutt-users]: Make you editor delete it for you. HTH, Michael -- Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs. (By Dennis Ritchie) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key -- Nelson D. Guerrero
Re: Signature
At 10:54 AM EDT on July 8 Nelson D. Guerrero sent off: and how would I go about doing this? [05/07/2002] - Michael Tatge - [mutt-users]: Make you editor delete it for you. One way would be to install post mode for emacs: http://astro.utoronto.ca/~reid/mutt/ -- Half the lies the opponents tell about us are not true. - Sir Boyle Roche Robert I. Reid | PGP/GPG Keys: http://astro.utoronto.ca/~reid/pgp.html
Re: Signature
[08/07/2002] - Rob Reid - [mutt-users]: One way would be to install post mode for emacs: http://astro.utoronto.ca/~reid/mutt/ -- Half the lies the opponents tell about us are not true. - Sir Boyle Roche Robert I. Reid | PGP/GPG Keys: http://astro.utoronto.ca/~reid/pgp.html I'm currentlly using VIM as my editor. -- Nelson D. Guerrero
Auto sync-mailbox
Hi! I was just wondering if mutt have some options for autorunning sync-mailbox ($)? -- |Mail address |Home telephonenumber|E-mail address | |Johan Svedberg |+46 (0)90 49 139|[EMAIL PROTECTED]| |Hästhagsvägen 2|| | |905 96 Umeå|Cellular telephonenumber|WWW address | |Sweden |+46 (0)70 639 49 82 |http://www.acc.umu.se/~winkle| --
Re: Signature
On Mon, Jul 08, 2002 at 10:54:41AM -0400, Nelson D. Guerrero wrote: and how would I go about doing this? http://hermitte.free.fr/vim/ressources/vimfiles/ftplugin/mail/Mail_Sig_set_vim.html -- Bernard Massot msg29437/pgp0.pgp Description: PGP signature
Re: Mutt users ml downloadable archives
Hello David, On Friday, July 5, 2002 at 10:05:21 AM -0500, David Thorburn-Gundlach wrote: Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] To: Mutt users ml mutt-users@m ^^ Fu... Yah... mung...: Fu... spa... I can [...] heartily endorse yahoo2mbox.pl from http://freshmeat.net/projects/yahoo2mbox/ (thanks again, Adam!). Thanks for the suggestion, it works surprisingly well. Version 0.07 even has an addresses unmunging function, taking models in a normal existing mailbox. It unmunges only email addresses, not Message-IDs or other @.\.\.\. strings. The only problem I have is with the From_ separator line: It's format is not recognised by Mutt. How have you solved this? It's with the full name, like that: | | From Michael Elkins [EMAIL PROTECTED] Fri Jul 31 00:32:50 1998 | Bye!Alain.
Re: Display problems with non-7bit text
You may recall that some weeks ago I posted that I couldn't read a UTF-8 message in my UTF-8 terminal even though everything appears to be set up properly: $charset, locale environment variables, locale definition matching those variables, message's Content-Type: header, wide-character version of ncurses, etc. Well, I did some debugging, and the problem appears to be this: Mutt is not treating incoming UTF-8 messages as UTF-8. It is finding and parsing the the charset=utf-8 parameter in the Content-Type: header, but the multibyte-to-wide character conversion is just returning each individual byte as a separate character instead of converting from UTF-8 and returning the transformed Unicode characters. So it's sabotaged long before it is even trying to convert the characters into something my terminal can display. For instance, my test message is some Latin text, and one of the characters in it that falls outside of the Latin-1 range is LATIN SMALL LETTER A WITH MACRON, U+0101. This is encoded in UTF-8 as the two-byte sequence 0xC4 0x81. Instead of returning the single character U+0101, the multibyte decoder is returning two characters: U+00C4 followed by U+0081. U+00C4 is LATIN CAPITAL LETTER A WITH DIARESIS (�) which is what I see if I run mutt in a Latin-1 terminal instead of a UTF-8 one; but U+0081 is a reserved control character which fails the iswprint() test and is therefore replaced by a backslash-octal sequence. So instead of the single character it should be sending (a small 'a' with a line over it), mutt is sending the five-character sequence �\201. (And since in UTF-8, � followed by \ is an invalid multibyte sequence, I see an invalid character glyph instead of the � in my UTF-8 terminal.) Any tips on where to look further to figure out why it's not recognizing the incoming message as UTF-8? -- Mark REED| CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- One is not superior merely because one sees the world as odious. -- Chateaubriand (1768-1848)
Re: Display problems with non-7bit text
[Resending with downgraded character set. I don't know why mutt thought it needed to use UTF-8 to encode this message; I avoided anything outside of the Latin-1 range, and I have $send_charset set to us-ascii:iso-8859-1:utf-8. But here's take two.] You may recall that some weeks ago I posted that I couldn't read a UTF-8 message in my UTF-8 terminal even though everything appears to be set up properly: $charset, locale environment variables, locale definition matching those variables, message's Content-Type: header, wide-character version of ncurses, etc. Well, I did some debugging, and the problem appears to be this: Mutt is not treating incoming UTF-8 messages as UTF-8. It is finding and parsing the the charset=utf-8 parameter in the Content-Type: header, but the multibyte-to-wide character conversion is just returning each individual byte as a separate character instead of converting from UTF-8 and returning the transformed Unicode characters. So it's sabotaged long before it is even trying to convert the characters into something my terminal can display. For instance, my test message is some Latin text, and one of the characters in it that falls outside of the Latin-1 range is LATIN SMALL LETTER A WITH MACRON, U+0101. This is encoded in UTF-8 as the two-byte sequence 0xC4 0x81. Instead of returning the single character U+0101, the multibyte decoder is returning two characters: U+00C4 followed by U+0081. U+00C4 is LATIN CAPITAL LETTER A WITH DIARESIS (Ä) which is what I see if I run mutt in a Latin-1 terminal instead of a UTF-8 one; but U+0081 is a reserved control character which fails the iswprint() test and is therefore replaced by a backslash-octal sequence. So instead of the single character it should be sending (a small 'a' with a line over it), mutt is sending the five-character sequence Ä\201. (And since in UTF-8, Ä followed by \ is an invalid multibyte sequence, I see an invalid character glyph instead of the Ä in my UTF-8 terminal.) Any tips on where to look further to figure out why it's not recognizing the incoming message as UTF-8? -- Mark REED| CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- One is not superior merely because one sees the world as odious. -- Chateaubriand (1768-1848)
Recording outbound messages
I'm puzzled... Doing a, :set ?record in mutt, displays, record=/home/deb/Mail/.record Which is exactly what I expected, as it is defined in my .muttrc as, set record=+.record But, nothing is being recorded there. :-( I reset it to point to +obox, and :set ?record displays record=/home/deb/Mail/obox, which is correct, but again nothing is being saved there. Should I be setting up some kind of a hook as well? Best Regards, deb -- If it dies, it's biology. If it blows up, it's chemistry, and if it doesn't work, it's physics. -- University bathroom graffito ô¿ô ~
Re: Recording outbound messages
* Deb [EMAIL PROTECTED] [2002-07-08 11:27 -0700]: I'm puzzled... Doing a, :set ?record in mutt, displays, record=/home/deb/Mail/.record What's the output of :set ?copy ? Nicolas
Re: Recording outbound messages
Hi, * Deb [02-07-08 20:38:12 +0200] wrote: :set ?record in mutt, displays, record=/home/deb/Mail/.record But, nothing is being recorded there. :-( 'set ?copy' says what? And what is displayed as the value for 'fcc' in the compose menu? bye, Rocco
Re: Signature
On Mon, Jul 08, 2002 at 10:54:41AM -0400, Nelson D. Guerrero wrote: | and how would I go about doing this? First you bottom quote so that a new member of the list can have a clue what you're asking. I think I've figured it out by combining the keywords signature and editor and delete, but it is better when you don't remove the original question. Now for the answer,in your .vimrc : augroup Mail au! au FileType mail set tw=70 fo=tcrq2 nomodeline clear the old sig and go back to the beginning of the buffer au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1d gg augroup END (that is a literal ^M charcter between the 'd' and 'g', on one line ) -D -- A man of many companions may come to ruin, but there is a friend that sticks closer than a brother. Proverbs 18:24 http://dman.ddts.net/~dman/ msg29445/pgp0.pgp Description: PGP signature
Re: Recording outbound messages
* Rocco Rutte [EMAIL PROTECTED] says, 'set ?copy' says what? And what is displayed as the value Thanks for replying. 'set ?copy' is copy=yes for 'fcc' in the compose menu? Please excuse my ignorance - how do I get to the compose menu? Thank you, deb
Re: Recording outbound messages
Ah!!! So obvious... but I wasn't sure. Okay, I'm looking at it now - Nope, there's no Fcc: I'll set that up next. Thanks!! deb * Mark J. Reed [EMAIL PROTECTED] [2002-07-08 15:54:48 -0400]: On Mon, Jul 08, 2002 at 12:41:09PM -0700, Deb wrote: for 'fcc' in the compose menu? Please excuse my ignorance - how do I get to the compose menu? By writing a new email message - you don't have to actually send it, but the compose menu is the screen from which you do so (the one you get to after you're done typing the message). It has y:Send q:Abort t:To . . . up top (with your key bindings substituted for y/q/t) followed by a list of some of the headers in the message you're about to send, followed by any attachments, followed by the identification bar at the bottom (Mutt: Compose . . ., which is where the menu gets its name). One of the headers is Fcc, which stands for Folder carbon copy, and should contain the value of your $record variable, e.g. Fcc: +.record. -- Mark REED | CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- Bond reflected that good Americans were fine people and that most of them seemed to come from Texas. -- Ian Fleming, Casino Royale -- If it dies, it's biology. If it blows up, it's chemistry, and if it doesn't work, it's physics. -- University bathroom graffito ô¿ô ~
Re: Recording outbound messages
Yes!! That did it! The configs are all starting to come together. I'll get this. Soon. Really, I will... Muchos Gracias, Amigo! deb * Mark J. Reed [EMAIL PROTECTED] [2002-07-08 15:54:48 -0400]: On Mon, Jul 08, 2002 at 12:41:09PM -0700, Deb wrote: for 'fcc' in the compose menu? Please excuse my ignorance - how do I get to the compose menu? By writing a new email message - you don't have to actually send it, but the compose menu is the screen from which you do so (the one you get to after you're done typing the message). It has y:Send q:Abort t:To . . . up top (with your key bindings substituted for y/q/t) followed by a list of some of the headers in the message you're about to send, followed by any attachments, followed by the identification bar at the bottom (Mutt: Compose . . ., which is where the menu gets its name). One of the headers is Fcc, which stands for Folder carbon copy, and should contain the value of your $record variable, e.g. Fcc: +.record. -- Mark REED | CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- Bond reflected that good Americans were fine people and that most of them seemed to come from Texas. -- Ian Fleming, Casino Royale -- If it dies, it's biology. If it blows up, it's chemistry, and if it doesn't work, it's physics. -- University bathroom graffito ô¿ô ~
Re: Recording outbound messages
On Mon, Jul 08, 2002 at 12:57:51PM -0700, Deb wrote:
Ah!!! So obvious... but I wasn't sure.
Okay, I'm looking at it now - Nope, there's no Fcc: I'll set
that up next.
While you can set it up manually, that wasn't what I meant.
The value of $record should automatically appear as the value of
the Fcc: header, unless it is overridden by an fcc-save-hook or
you manually add a different Fcc: value in your editor.
I have $record set to '=sent' ('=' and '+' are synonymous in folder names)
and $copy set to yes, and when I get to the compose menu,
I see Fcc: =sent. Not sure why you're not seeing the same behavior.
--
Mark REED| CNN Internet Technology
1 CNN Center Rm SW0831G | [EMAIL PROTECTED]
Atlanta, GA 30348 USA | +1 404 827 4754
--
If one cannot enjoy reading a book over and over again, there is no use
in reading it at all.
-- Oscar Wilde
Re: Signature
Hi, * Derrick 'dman' Hudson [02-07-08 21:54:24 +0200] wrote: Now for the answer,in your .vimrc : augroup Mail au! au FileType mail set tw=70 fo=tcrq2 nomodeline clear the old sig and go back to the beginning of the buffer au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1d gg ^^ augroup END Just to mention it: You have to replace '| ' (yes, the symbol and the space) by the value of your $indent_string. Another solution is to use: http://cedricduval.free.fr/download/vimrc/mail like: au BufRead /tmp/mutt-* :source $path_to_the_file (replacing /tmp with the value of $tmpdir of ~/.muttrc) The only thing I don't like about this solution is that it only removes one level of quoted empty lines. This surely is on purpose but I like to remove all quote characters on empty lines (small fix required). Also, it only recognizes '' as a quoting character. bye, Rocco
Re: Recording outbound messages
Hi, * Deb [02-07-08 22:19:06 +0200] wrote: Okay, I'm looking at it now - Nope, there's no Fcc: I'll set that up next. To give you one more hint: Your text is much more readable if you put your answer within and/or under the quoted text. Never above. bye, Rocco [funny that the reply arrived before the parent...]
Re: Display problems with non-7bit text
On Mon, Jul 08, 2002 at 05:17:25PM -0400, Thomas Dickey wrote: You said you were running Mandrake 7.1, but did not say what version of glibc - and if you are using libiconv. One of your comments regarding compile problems left me with the impression that the glibc may be too old to properly support libiconv. I'm using glib 1.2. But I have no difficulty using iconv (GNU libiconv 1.8) to convert to and from UTF-8 in other applications. -- Mark REED| CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- I am a jelly donut. I am a jelly donut.
aliases
Hello, I'm wondering if it's possible to have mutt aliases _without_ a proper alias. sounds weird maybe, but i have a big contact list with email adresses which I want to use in Mutt as an addressbook to walk through when I press tab to bring up the aliases. the problem is that if I don't supply an alias for the alias (which sort of is the idea I guess) Mutt will make it like... FirstnameLastname [EMAIL PROTECTED] is there any way to avoid this? cheers, /rikard
Re: Signature
--5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Nelson D. Guerrero spake thus: [08/07/2002] - Rob Reid - [mutt-users]:=20 One way would be to install post mode for emacs: =20 http://astro.utoronto.ca/~reid/mutt/ =20 --=20 Half the lies the opponents tell about us are not true. - Sir Boyle Roc= he Robert I. Reid | PGP/GPG Keys: http://astro.utoronto.ca/~reid/pgp.html =20 I'm currentlly using VIM as my editor. Then do some RTFMing and find out how to make vim automatically delete it whenever you start vim on an email. --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- The longer the title, the less important the job. --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9Kj5BPTh2iSBKeccRAt8iAJ9H70Eu62JkecXNGIdF4DpK1KDlHQCaAgSM qxTLg8rLFAamP4ZarIHW05o= =55+6 -END PGP SIGNATURE- --5vNYLRcllDrimb99--
mutt-1.4: make fails
Hi: this is my first attempt to compile mutt, so please bear with me. I tried to compile mutt-1.4i under Solaris 2.6. Our mail spool has 1775 permissions: # ls -ld /var/mail drwxrwxr-t 6 root mail 479232 Jul 8 18:48 /var/mail I used the following configure command: CC='gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail which proceeds without errors. When I run make, however, it fails with gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE -Wall -pedantic -g -O2 -L/usr/LOCAL/lib -L/usr/LOCAL/ssl/lib -o mutt patchlist.o addrbook.o alias.o attach.o base64.o browser.o buffy.o color.o commands.o complete.o compose.o copy.o curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o from.o getdomain.o handler.o hash.o hdrline.o headers.o help.o hook.o keymap.o main.o mbox.o menu.o mh.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o rfc822.o rfc1524.o rfc2047.o rfc2231.o score.o send.o sendlib.o signal.o sort.o status.o system.o thread.o charset.o history.o lib.o muttlib.o editmsg.o utf8.o mbyte.o wcwidth.o url.o ascii.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o resize.o dotlock.o pop.o pop_lib.o pop_auth.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl.o md5c.o -Limap -limap -lncurses -lssl -lcrypto ./intl/libintl.a -lsocket -lnsl ld: fatal: symbol `main' is multiply defined: (file main.o and file dotlock.o); ld: fatal: symbol `ReleaseDate' is multiply defined: (file muttlib.o and file dotlock.o); ld: fatal: File processing errors. No output written to mutt collect2: ld returned 1 exit status make[2]: *** [mutt] Error 1 make[2]: Leaving directory `/usr/LOCAL/src/mutt-1.4' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/LOCAL/src/mutt-1.4' make: *** [all-recursive-am] Error 2 What is wrong? [BTW: the same error occurs when I configure with CC='gcc -R/usr/LOCAL/lib' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail then modify config.h to define USE_DOTLOCK and DL_STANDALONE and then run make. There does not seem to be a configure option set causes USE_DOTLOCK and DL_STANDALONE to be set, is there?] Thanks for your help in advance. Cheers, Martin Martin Siegert Academic Computing Servicesphone: (604) 291-4691 Simon Fraser Universityfax: (604) 291-4242 Burnaby, British Columbia email: [EMAIL PROTECTED] Canada V5A 1S6
Re: mutt-1.4: make fails
Sorry for replying to my own mail. But I finally figured out what was going wrong: the configure script looks at permission of the mail spool (/var/mail in our case) in order to decide whether mutt needs to run setgid mail or not. This procedure only works, if the machine on which you compile mutt, is also the machine on which you run mutt. Which is not the case here (I cannot compile/install mutt on the machine where it is used, because on that machine those directories are not writable). In our case that directory was neither world nor group writable. Thus, configure decided that setting setgid mail wouldn't do any good. Anyway, the solution to this mess is to temporary make /var/mail groupwritable on the machine where you compile. Then run CC='gcc -R/usr/LOCAL/lib' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail --enable-external-dotlock After that make runs without errors and make install will install the mutt_dotlock program to do the mailbox locking. After all that you can remove the group write permission on /var/mail again. It would be nice though to have something like a --setgid configure option that would overwrite the default configure behaviour. Cheers, Martin Martin Siegert Academic Computing Servicesphone: (604) 291-4691 Simon Fraser Universityfax: (604) 291-4242 Burnaby, British Columbia email: [EMAIL PROTECTED] Canada V5A 1S6 On Mon, Jul 08, 2002 at 07:03:14PM -0700, Martin Siegert wrote: Hi: this is my first attempt to compile mutt, so please bear with me. I tried to compile mutt-1.4i under Solaris 2.6. Our mail spool has 1775 permissions: # ls -ld /var/mail drwxrwxr-t 6 root mail 479232 Jul 8 18:48 /var/mail I used the following configure command: CC='gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail which proceeds without errors. When I run make, however, it fails with gcc -R/usr/LOCAL/lib -DUSE_DOTLOCK -DDL_STANDALONE -Wall -pedantic -g -O2 -L/usr/LOCAL/lib -L/usr/LOCAL/ssl/lib -o mutt patchlist.o addrbook.o alias.o attach.o base64.o browser.o buffy.o color.o commands.o complete.o compose.o copy.o curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o from.o getdomain.o handler.o hash.o hdrline.o headers.o help.o hook.o keymap.o main.o mbox.o menu.o mh.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o rfc822.o rfc1524.o rfc2047.o rfc2231.o score.o send.o sendlib.o signal.o sort.o status.o system.o thread.o charset.o history.o lib.o muttlib.o editmsg.o utf8.o mbyte.o wcwidth.o url.o ascii.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o resize.o dotlock.o pop.o pop_lib.o pop_auth.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl.o md5c.o -Limap -limap -lncurses -lssl -lcrypto ./intl/libintl.a -lsocket -lnsl ld: fatal: symbol `main' is multiply defined: (file main.o and file dotlock.o); ld: fatal: symbol `ReleaseDate' is multiply defined: (file muttlib.o and file dotlock.o); ld: fatal: File processing errors. No output written to mutt collect2: ld returned 1 exit status make[2]: *** [mutt] Error 1 make[2]: Leaving directory `/usr/LOCAL/src/mutt-1.4' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/LOCAL/src/mutt-1.4' make: *** [all-recursive-am] Error 2 What is wrong? [BTW: the same error occurs when I configure with CC='gcc -R/usr/LOCAL/lib' ./configure --prefix=/usr/LOCAL --enable-pop --enable-imap --with-ssl=/usr/LOCAL/ssl --with-curses=/usr/LOCAL --with-mailpath=/var/mail then modify config.h to define USE_DOTLOCK and DL_STANDALONE and then run make. There does not seem to be a configure option set causes USE_DOTLOCK and DL_STANDALONE to be set, is there?] Thanks for your help in advance. Cheers, Martin Martin Siegert Academic Computing Servicesphone: (604) 291-4691 Simon Fraser Universityfax: (604) 291-4242 Burnaby, British Columbia email: [EMAIL PROTECTED] Canada V5A 1S6
Re: aliases
* Rikard Florin [EMAIL PROTECTED] [2002-07-09 00:30]: I'm wondering if it's possible to have mutt aliases _without_ a proper alias. no. Sven
Re: Auto sync-mailbox - no way!
* Johan Svedberg [EMAIL PROTECTED] [2002-07-08 15:24]: I was just wondering if mutt have some options for autorunning sync-mailbox ($)? no. we'd rather not have people lose mails that way. besides, you can use rm with 'crontab to get rid of some mail periodically if you wish. *ehem* Sven
Re: mutt window copy/paste (Correction)
Thomas Dickey [EMAIL PROTECTED] had this to say, On Fri, Jul 05, 2002 at 01:13:47PM -0700, Deb wrote: I forgot to mention that I'm using xterm-166, with terminfo xterm-color, on Solaris, Sparc. Not sure the xfree86 is appropriate for this platform? But xterm-color usually says that the terminal doesn't implement back color erase (bce). In that case, most full-screen applications will write explicit blanks, which xterm's select/paste will preserve. Hold on. The behavior holds for *both* xterm and xterm-color, and I just tested F-secure ssh Windoze client - and it also exhibits the same behaviour - the only common denominator is using mutt and copying/ pasting text from a displayed message. Mutt, in all cases I think, is using my color defaults, even when there is no color. I could eliminate that from the mix and test, I suppose. Next on the drawing board... deb I would consider this a bug. ( sure - but not in mutt or xterm ;-) I still respectfully disagree (see above). Kind Regards, deb
Re: new mail question..
On Sat, Jun 29, 2002 at 09:45:01PM -0700, Geoff Ludwiczak wrote: That's odd. I ran a test before where I had my main mailbox open. I email myself, run fetchmail, and i watch the mutt window with mail_check set to 1. I waited to see if mutt would pick up on the new message and automatically say new mail and show the message in the index. So I have to manually go into the window and hit up or down in the index, and then the message shows. I want the message to show without me having to go up or down in the index. Any idea? The variable you're looking for is 'timeout'. Putting this in your muttrc set timeout=10 will cause mutt to timeout after 10 seconds of no activity from the keyboard and to check for new mail. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
