Re: Problem with folder-hook - ~r vs ~d
Sven Guckes ([EMAIL PROTECTED]) muttered: * Eric Blau [EMAIL PROTECTED] [2002-08-17 15:17]: I have the following folder-hook in my muttrc file: folder-hook =INBOX 'push T~r1m\n\;s=archive/INBOX\n' ~r takes *no* argument and is for *all* read messages. i think you want to use ~d which takes a date range as an argument. No Sven ~r is date-received. ~R read messages ~r [MIN]-[MAX] messages with ``date-received'' in a Date range ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range Michael -- All language designers are arrogant. Goes with the territory... (By Larry Wall) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: CC: folder-hook with same From:
Saku Ytti ([EMAIL PROTECTED]) muttered: This works here, too. Sure you don't have send-hooks which set From: in any way? Nope, no send-hooks. If I write new mail via 'm' I get the From and Cc formatted as expected by configartion above but if I reply via 'r' the Cc doesn't appear unless I change it to something different than From. Even replying works like charm. Please test with 'mutt -F /dev/null' to be sure it's not your setup. HTH, Michael -- Linux! Guerrilla UNIX Development Venimus, Vidimus, Dolavimus. (By [EMAIL PROTECTED], Mark A. Horton KA4YBR) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: PGP Outlook
Alan -- ...and then Alan Batie said... % % I was wondering if something can't be done to fix the interaction In addition to what Sven has provided, note that $p_c_t requires an additional patch up through v1.4 to really work seamlessly with Outhouse; in the 1.5 tree that patch has been merged in and you can use stock code for your LookOut! exchanges. You can pick up patch-1.3.28.dw.pgp-traditional.2 from http://mutt.justpickone.org/mutt-build-cocktail/ or in the list archives (where, BTW, this has been discussed quite a bit already). HTH HAND :-D -- 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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg30363/pgp0.pgp Description: PGP signature
Re: Mutt color limitations
On Sun, 18 Aug 2002, Lee J. Moore wrote: Oh woah is me for following up to my own followup but this is driving me nuts. ;) [..] Trying to use color8 and above, results in [sic] errors. [..] This is despite the fact that color8 and above is available with slrn in the same terminal. I can use color8, color9, etc., - in slrn's actual config file and the results can clearly be seen when slrn is launched. I'm using Mutt 1.4-r2 (compiled/installed from source with Gentoo's Portage) if that's relevant. Further to this, mutt is compiled with slang and apparently this alone should apparently make lightgray available, but Mutt says this is an invalid colour. Sixteen colours are available to all of my terminal apps, bar mutt which only allows colours in the range of [color0-color7]. It doesn't seem to matter what terminal I'm using either. ldd /usr/bin/mutt libslang.so.1 = /usr/lib/libslang.so.1 (0x4002e000) libm.so.6 = /lib/libm.so.6 (0x40092000) libssl.so.0.9.6 = /usr/lib/libssl.so.0.9.6 (0x400b4000) libcrypto.so.0.9.6 = /usr/lib/libcrypto.so.0.9.6 (0x400e1000) libc.so.6 = /lib/libc.so.6 (0x4019d000) libdl.so.2 = /lib/libdl.so.2 (0x402cc000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) mutt -v Mutt 1.4i (2002-05-29) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.19-gentoo-r7 (i686) [using slang 10405] Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=Maildir PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc/mutt EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28) msg30364/pgp0.pgp Description: PGP signature
RE : Mutt color limitations
Hmm.. I compiled mutt with slang, and I discovered that contrary to ncurses, the headers now had background colour to the end of the line, but brightblack no longer worked. (tried with xterm, rxvt, aterm and konsole) I'd love it of mutt could use the standard unix rgb.txt color names and a higher selection of colours. Philip Wittamore, using outhouse because he's at work :-( -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Lee J. Moore Envoyé : mardi 20 août 2002 13:52 À : [EMAIL PROTECTED] Objet : Re: Mutt color limitations On Sun, 18 Aug 2002, Lee J. Moore wrote: Oh woah is me for following up to my own followup but this is driving me nuts. ;) [..] Trying to use color8 and above, results in [sic] errors. [..] This is despite the fact that color8 and above is available with slrn in the same terminal. I can use color8, color9, etc., - in slrn's actual config file and the results can clearly be seen when slrn is launched. I'm using Mutt 1.4-r2 (compiled/installed from source with Gentoo's Portage) if that's relevant. Further to this, mutt is compiled with slang and apparently this alone should apparently make lightgray available, but Mutt says this is an invalid colour. Sixteen colours are available to all of my terminal apps, bar mutt which only allows colours in the range of [color0-color7]. It doesn't seem to matter what terminal I'm using either. ldd /usr/bin/mutt libslang.so.1 = /usr/lib/libslang.so.1 (0x4002e000) libm.so.6 = /lib/libm.so.6 (0x40092000) libssl.so.0.9.6 = /usr/lib/libssl.so.0.9.6 (0x400b4000) libcrypto.so.0.9.6 = /usr/lib/libcrypto.so.0.9.6 (0x400e1000) libc.so.6 = /lib/libc.so.6 (0x4019d000) libdl.so.2 = /lib/libdl.so.2 (0x402cc000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) mutt -v Mutt 1.4i (2002-05-29) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.19-gentoo-r7 (i686) [using slang 10405] Compile options: -DOMAIN -DEBUG +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=Maildir PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc/mutt EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28)
Re: CC: folder-hook with same From:
Michael Tatge [EMAIL PROTECTED] wrote: Hello Michael, Nope, no send-hooks. If I write new mail via 'm' I get the From and Cc formatted as expected by configartion above but if I reply via 'r' the Cc doesn't appear unless I change it to something different than From. Even replying works like charm. Please test with 'mutt -F /dev/null' to be sure it's not your setup. Umm, I'm puzzled. If I use the -F /dev/null how do I get the folder-hook readen which don't work properly. To summarize: if I use this I do not get Cc header when replying with 'r'. folder-hook folder 'my_hdr From: Me listdomain' folder-hook folder 'my_hdr Cc: List list@domain' if I use this I do get Cc header when replying with 'r'. folder-hook folder 'my_hdr From: Me listdomain' folder-hook folder 'my_hdr Cc: List foo@domain' I do not have any other hooks for '.' nor 'folder'. Global configuration is from Debian/Unstable which doesn't contain anything that should conflict with these. I really think that this is some sanity check, haven't check the source code though. Maybe mutt just doesn't allow setting From and Cc as same addresses with hooks? I can duplicate this on my other Debian/Unstable system. -- ++ytti
Re: CC: folder-hook with same From:
Saku Ytti ([EMAIL PROTECTED]) muttered: Michael Tatge [EMAIL PROTECTED] wrote: Even replying works like charm. Please test with 'mutt -F /dev/null' to be sure it's not your setup. Umm, I'm puzzled. If I use the -F /dev/null how do I get the folder-hook readen which don't work properly. Enter them? Source a file which contains these hooks only? To summarize: if I use this I do not get Cc header when replying with 'r'. folder-hook folder 'my_hdr From: Me listdomain' ^@? folder-hook folder 'my_hdr Cc: List list@domain' This does work. Are you using any patch? HTH, Michael -- ...Deep Hack Mode--that mysterious and frightening state of consciousness where Mortal Users fear to tread. (By Matt Welsh) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Two questions
Greetings! Two questions. First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? Kind Regards, -Noesis -- _ ___ / | / /___ ___ _(_) / |/ / __ \/ _ \/ ___/ / ___/ / /| / /_/ / __(__ ) (__ ) /_/ |_/\/\___//_// noesis at darktide dot com http://www.darktide.com/noesis/ DigitalNoesis.com - Darktide.com msg30368/pgp0.pgp Description: PGP signature
not a mailbox
Greetings! I have a problems with mutt. My procmail filter all mail and putting it from /var/spool/mail/username to ~/mail/Inbox. Mutt is setting up to look to ~/mail/Inbox, but when I start mutt, it says ~/mail/Inbox - not a mailbox. Why ? -- Best regards, Oleg Lukashin mailto:[EMAIL PROTECTED]
Re: not a mailbox
Oleg Lukashin ([EMAIL PROTECTED]) muttered: I have a problems with mutt. My procmail filter all mail and putting it from /var/spool/mail/username to ~/mail/Inbox. but when I start mutt, it says ~/mail/Inbox - not a mailbox. Why ? Hard to say. Blame procmail I suppose. Does ~/mail/Inbox start with a From_ Line? That is FromSPACE. 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
Re: New mail notification problems
John Iverson said: * On Mon, 19 Aug 2002, Mike Leone wrote: I use Maildir with IMAP, and I see *no* new mail notifications on the folders at all. When I open the mailbox (maildir), yes - the index or pager shows new messages. But using the c command to switch folders only ever shows the name of the folder, and not a new mail notification symbol. You're saying that you do see a new mail indicator on Maildir (i.e., IMAP) folders? Maildir, but not IMAP (perhaps I misused a term somewhere). No, you can use Maildir format when not using IMAP. I used to use local Maildir format mailboxes (which are, in reality, directories) with a POP account. I'm referring to the mailbox browser screen which appears when you press ? after pressing c. Yes, that's what I'm referring to, as well. Yes, I do see the new mail indicators, except for the mailbox I just came from. (Doesn't matter if I press tab to switch between mailbox and file views.) When I first start mutt with mutt -y (i.e. there is no last-visited mailbox), the new mail indicators for all mailboxes seem to work. My indicators never work, but perhaps that's because they're IMAP folders, on a remote machine (my mail server). Just curious if this is normal behavior or not. There did not seem to be a conclusion last time it was discussed, and I thought it possible that this is what the original poster was experiencing. -- PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF Member, LEAF Project http://leaf.sourceforge.netAIM: MikeLeone These are the memories which make me a wealthy soul ... Random Thought: --
Re: [OT] Re: spamassassin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Michael Leone on Mon, Aug 19, 2002 at 03:42:58PM -0400: Can it be set to delete spam automatically (I'm not so interested in just *marking* spam, because if it only marks spam I still have to sift through it), without getting too many false positives? No. The next version of SA - due out this week - removes the capability to do delivery of email, so you'll have to rely on procmail or maildrop to do delivery or deletion. And there's no way to delete without getting too many false positives - you either delete things marked as spam, or not delete. It's not really conditional. :-) You do run the risk of losing legitimate mail if you delete. If you don't, ... well, you should be able to tell legit mail merely by quickly looking at the subject lines. No need to read the mail. For those who are curious, the link below also has a quick guide I wrote to Mutt + SpamAssassin and some neat tricks, FWIW. - -- [!] Justin R. Miller [EMAIL PROTECTED] Encrypted email preferred (key 0xC9C40C31) Mutt/GnuPG guide at http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9YmxS94d6K8nEDDERArddAKCMXyCQJ4Iq5ZKtTWyMmM8OJPJ2HgCeJXCY jbU+Hjl5y7+USynBJg2OY7w= =Rck9 -END PGP SIGNATURE-
Re: PGP Outlook
I use the mailcrypt library from within Emacs to clear sign a regular text message for outlook folks. I also try and remind them when I can about using a more standards compliant email client :-. It has come to my attention... ...that Alan Batie said on Monday, Aug 19 2002: I was wondering if something can't be done to fix the interaction between PGP/MIME and Outlook et al that refuse to show signed messages. They apparently know enough MIME to recognize that they can't handle multipart/signed and don't look inside for the text/plain part. I wonder if a separate unsigned text/plain with a small warning about the contents not being verified would be appropriate? -- Alan Batie __alan.batie.orgMe [EMAIL PROTECTED] \/www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A\ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ spamassassin.taint.org NO SPAM! You just wish sometimes that the [Catholic] Church protected children as much as it protects fetuses. -- Lesbian comedian Kate Clinton writing in The Progressive, July issue. -- --Sam UC Davis, California USA
Re: Two questions
Not sure about the error 13, but to keep a transparent background, use the default color as the background color for everything when setting your colors. Just make sure not to use mutt in a white background terminal after the change though :-. HTH It has come to my attention... ...that Noesis said on Tuesday, Aug 20 2002: Greetings! Two questions. First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? Kind Regards, -Noesis -- _ ___ / | / /___ ___ _(_) / |/ / __ \/ _ \/ ___/ / ___/ / /| / /_/ / __(__ ) (__ ) /_/ |_/\/\___//_// noesis at darktide dot com http://www.darktide.com/noesis/ DigitalNoesis.com - Darktide.com -- --Sam UC Davis, California USA
send-hook and subject
Send-Hooks, and the Subject, revisited. ___ I have asked a similar question before, with no clear answer. I will try to rephrase it. I hope that perhaps some developer is reading, and can say 'this is not possible' or 'it should be possible'. Now, the question: Is it possible to use a send hook to set the subject? My common sense tells me it is possible. However, I have tried several combinations of send-hooks without success. Examples: send-hook '~t ^[EMAIL PROTECTED]$' 'my_hdr Subject: [test] ' send-hook [EMAIL PROTECTED] 'my_hdr Subject: [test] ' ... This does not result in the subject line set to start with [test] as expected. However, and strangely enough, every one in a hundred messages or so (i.e. very infrequently) the subject line will start with [test], even though I'm not sending the message to the magic incantation of [EMAIL PROTECTED] Using 'unmy_hdr Subject' or not doesn't appear to affect this behaviour. Perhaps my_hdr can be used with other headers, but not with the subject. I'm not a developer myself, so I cannot read mutt's sources and figure this out, but I guess it should be possible ... right? I've tried several options to make mutt avoid asking for the subject upon hitting 'm' to start a new message. No change. Upon searching google with 'unmy_hdr Subject:' I see that most of the hits are to documents with the words 'unmy_hdr' and 'Subject' not connected (not near). One document, however contains the following send-hook (it's from a mailing list archive): send-hook '[EMAIL PROTECTED]' \ 'set mime_forward ; set pgp_autosign=no ; set editor=/bin/true ; \ my_hdr Fcc: /dev/null ; my_hdr From: [EMAIL PROTECTED] ; my_hdr Subject: spam ; \ push y' However, a comment on top of the send-hook says: # mystery: The subject isn't being set. Why?!? We're two now. Any idea why the Subject header doesn't like being set this way? Thanks in advance, Fernan. -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan -BEGIN GEEK CODE BLOCK- Version: 3.1 GS d- s:+ a C++ BU++ P+++ L- E- W+++ N o? K? w- !O M+ !V PS+ PE Y+ PGP t- 5? X- R- tv+ b++ DI+ !D G e h r+++ y+++ --END GEEK CODE BLOCK--
Re: PGP Outlook
yes - someone ought to tell the creators or outlook about RFC2015.. It would help if they cared about interoperating... so i think you should upgrade. ;-) apparently ;-) I'm actually using check-traditional now, so I guess I'll break down and send it also... In addition to what Sven has provided, note that $p_c_t requires an additional patch up through v1.4 to really work seamlessly with Outhouse; in the 1.5 tree that patch has been merged in and you can use stock code for your LookOut! exchanges. You can pick up patch-1.3.28.dw.pgp-traditional.2 from http://mutt.justpickone.org/mutt-build-cocktail/ Thanks! or in the list archives (where, BTW, this has been discussed quite a bit already). I thought it must've, but couldn't find the archives despite, the fact that there they are, just down the page. I blame it on the fact that I've been doing accounting for the last couple of days, and it's rotted my brain ;-) -- Alan Batie __alan.batie.orgMe [EMAIL PROTECTED] \/www.qrd.org The Triangle PGPFP DE 3C 29 17 C0 49 7A\ / www.pgpi.com The Weird Numbers 27 40 A5 3C 37 4A DA 52 B9 \/ spamassassin.taint.org NO SPAM! You just wish sometimes that the [Catholic] Church protected children as much as it protects fetuses. -- Lesbian comedian Kate Clinton writing in The Progressive, July issue. msg30376/pgp0.pgp Description: PGP signature
Reducing duplication
Hey all ;) I have a bit of a problem -- When I send a mailing list, one copy of the message is stored in my sent-mail mbox, and then another copy is stored in that ml's mbox when I get it off the list again. The problem is that I've written an mbox parsing utility (for the purposes of reporting statistics), and there is a huge amount of duplication in my own mails. So what I want to know is, is there a way to get mutt to save messages to sent-mail only if it's not addressed to a mailing list that I'm subscribed to? -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Darth Vader sleeps with a Teddywookie. msg30377/pgp0.pgp Description: PGP signature
Re: Reducing duplication
--OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! darren chamberlain spake thus: * Rob 'Feztaa' Park [EMAIL PROTECTED] [2002-08-20 16:22]: The problem is that I've written an mbox parsing utility (for the purposes of reporting statistics), and there is a huge amount of duplication in my own mails. =20 So what I want to know is, is there a way to get mutt to save messages to sent-mail only if it's not addressed to a mailing list that I'm subscribed to? =20 Why not do it in the script? The mailing list folders and sent-mail folders serve fundamentally different purposes; why intermix them? Keep a hash table of message ids in the script, and process the message the first time you see it only. I do, though. For every message id, I keep track of how many times the script encountered it. I also have 'total' and 'unique' counts for every person, mbox, date, and MUA. The problem is that the 'total' count of all of my messages is nearly 1,000 greater than the 'unique' count, which really bothers me (it looks ugly in the statistics, not to mention that the duplication is a waste of disk space). Maybe I'm crazy, but it just seems silly and inefficient to keep copies of my ml messages in two places. Or skip your sent-mail folder altogether. I wanted to avoid this for portability; if I just skip my own sent mail folder, then I'm limiting the script to my own machine. I want it to work for other people as well ;) --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Space tells matter how to move and matter tells space how to curve. -- Wheeler --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9YrUvPTh2iSBKeccRAhZHAJ95hgdHC3Qyj7xWhB3coMRm5V6xMgCeIDLO rPkgQV1jjnKI+dFdsGJeY5o= =d/t0 -END PGP SIGNATURE- --OXfL5xGRrasGEqWY--
Re: Mutt color limitations
On Tue, 20 Aug 2002, Philip Wittamore wrote: Hmm.. I compiled mutt with slang, and I discovered that contrary to ncurses, the headers now had background colour to the end of the line, but brightblack no longer worked. (tried with xterm, rxvt, aterm and konsole) Yep, same here. Considering the number of terminals I've used and the fact that they all support sixteen colours with other apps, I find it difficult to believe it's not Mutt at fault. No amount of googling turns up solutions, nor posting to the list. Maybe it's only a minority of Mutt users who want more than eight colours. I've got one ugly mutt here atm. ;( I'd love it of mutt could use the standard unix rgb.txt color names and a higher selection of colours. A nice idea! Philip Wittamore, using outhouse because he's at work :-( You should complain to the council. Indoor toilets are required for health and safety reasons thesedays. ;-) -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28) msg30380/pgp0.pgp Description: PGP signature
Re: Mutt color limitations
On Tue, Aug 20, 2002 at 11:16:55PM +0100, Lee J. Moore wrote: On Tue, 20 Aug 2002, Philip Wittamore wrote: Hmm.. I compiled mutt with slang, and I discovered that contrary to ncurses, the headers now had background colour to the end of the line, but brightblack no longer worked. (tried with xterm, rxvt, aterm and konsole) ROFL (slang, cited as a standard) Yep, same here. Considering the number of terminals I've used and the fact that they all support sixteen colours with other apps, I find it difficult to believe it's not Mutt at fault. No amount of googling turns up solutions, nor posting to the list. Maybe it's only a minority of Mutt users who want more than eight colours. 8 colors are standard (the majority of those 16-color applications are assuming that bold colors are bright - which is not a valid assumption in many cases). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt color limitations
Le (20/08/02 23:16), Lee J. Moore à ecrit: Maybe it's only a minority of Mutt users who want more than eight colours. do you think that some believe that colour is too un-nerdy ? me, I'm a brand of monkey, and colour is just as important for my mail as it was when my great-grandaddy was picking out ripe fruit up in the trees. tastefull use of colour makes for easy reading selecting, and we are built to use it, so it's important where interfaces are concerned. Phil -- Philip Wittamore [EMAIL PROTECTED] http://perso.wanadoo.fr/aposit
Re: Mutt color limitations
On Tue, 20 Aug 2002, Thomas Dickey wrote: [..] 8 colors are standard (the majority of those 16-color applications are assuming that bold colors are bright - which is not a valid assumption in many cases). Well, as an example, in slrn, I've got a lightgray statusbar with white text. Easier to read than you might think. In Mutt, I'm finding it impossible to achieve. 'brightwhite' creates *bold* white text, whereas 'white' creates grey text (the grey I see, is actually lightgray according to slrn). If I change the status bar to 'white' (ahem, cough, cough, lightgray), and the text to 'brightwhite', the status bar actually ends up *black*! Is Mutt trying to hold my hand here or something? If I want to use difficult colour combinations (and I don't think they are difficult), I'd like to make that decision/mistake myself. -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28) msg30383/pgp0.pgp Description: PGP signature
Re: Mutt color limitations
--Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Lee J. Moore spake thus: I've got one ugly mutt here atm. ;( I seem to be able to get by with only 8 colors. Although, I did implement the hack that lets you have a 256 color xterm... and it worked, because the test programs were printing all wild color shizzit... but I can't for the life of me figure out how to make any of my applications *use* those extra colors, so the 256 colors are useless ;) --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Satire is what closes Saturday night. -- George Kaufman --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9YtyrPTh2iSBKeccRAlN3AJ4sXR/aWX3tko+qMCY/BAysTF8wJgCfSREJ zpmNmL5lk89d2LUVZA81yDM= =wm9s -END PGP SIGNATURE- --Pk6IbRAofICFmK5e--
Re: Mutt color limitations
On Wed, 21 Aug 2002, Philip Wittamore wrote: Le (20/08/02 23:16), Lee J. Moore à ecrit: Maybe it's only a minority of Mutt users who want more than eight colours. do you think that some believe that colour is too un-nerdy ? Um...no! I don't care about others perceptions. If I did, I wouldn't tell anybody but my psychaitrist. ;) [..] tastefull use of colour makes for easy reading selecting, and we are built to use it, so it's important where interfaces are concerned. I agree 100%. I've already decided upon a tasteful colour scheme in slrn. It's getting the same colours in Mutt (in particular color8-color15) that is the problem. -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28) msg30385/pgp0.pgp Description: PGP signature
Re: send-hook and subject
* Fernan Aguero [EMAIL PROTECTED] [2002-08-20 16.39 -0300]: Hi Fernan. Is it possible to use a send hook to set the subject? Yes, but you must have 'unset autoedit' in your muttrc; if not set, there isn't any data for the send-hook to work with. HTH -- _ Martin Karlsson ( ) \ ASCII Ribbon Campaign / \Against HTML and proprietary attachments in e-mail msg30386/pgp0.pgp Description: PGP signature
Re: send-hook and subject
At 16:39 -0300 20 Aug 2002, Fernan Aguero [EMAIL PROTECTED] wrote: Is it possible to use a send hook to set the subject? No. To quote the manual: ] Note: the send-hook's are only executed ONCE after getting the initial ] list of recipients. Adding a recipient after replying or editing the ] message will NOT cause any send-hook to be executed. Also note that ] my_hdr commands which modify recipient headers, or the message's ] subject, don't have any effect on the current message when executed ] from a send-hook. -- Aaron Schrab [EMAIL PROTECTED] http://www.schrab.com/aaron/ Besides, including std_ice_cubes.h is a fatal error on machines that don't have it yet. Bad language design, there... :-)--Larry Wall
Re: send-hook and subject
* Martin Karlsson [EMAIL PROTECTED] [2002-08-21 03.02 +0200]: Yes, but you must have 'unset autoedit' in your muttrc; if not set, there isn't any data for the send-hook to work with. s/unset/set And it doesn't work if you're replying, only when you write a new mail. I think. -- _ Martin Karlsson ( ) \ ASCII Ribbon Campaign / \Against HTML and proprietary attachments in e-mail msg30388/pgp0.pgp Description: PGP signature
Re: send-hook and subject
* Martin Karlsson [EMAIL PROTECTED] [2002-08-21 03.19 +0200]: * Martin Karlsson [EMAIL PROTECTED] [2002-08-21 03.02 +0200]: Yes, but you must have 'unset autoedit' in your muttrc; if not set, there isn't any data for the send-hook to work with. s/unset/set And it doesn't work if you're replying, only when you write a new mail. I think. I need a vacation. Just ignore me. *sigh* -- _ Martin Karlsson ( ) \ ASCII Ribbon Campaign / \Against HTML and proprietary attachments in e-mail msg30389/pgp0.pgp Description: PGP signature
Re: Two questions - error 13 - terminal transparency
* Noesis [EMAIL PROTECTED] [2002-08-20 13:37]: First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? os, mutt version [1], setup, commands, error messages? which MTA? changed its setup? checked the logs? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? use a terminal which allows transparency?! ps: spamassassin reported your mails as spam. makes you think - i hope. Sven [1] (yes, i have seen the header. still - you never know..)
Re: not a mailbox - check the folder
* Oleg Lukashin [EMAIL PROTECTED] [2002-08-20 13:47]: I have a problems with mutt. My procmail filter all mail and putting it from /var/spool/mail/username to ~/mail/Inbox. Mutt is setting up to look to ~/mail/Inbox, but when I start mutt, it says ~/mail/Inbox - not a mailbox. Why ? because that file/folder is not a mailbox. ;-) does the same happen when you try to start mutt on the folder directly? mutt -f ~/mail/Inbox does that file start with From_? or does it happen to start with an empty line? but if you are using maildir style then try: mutt -f ~/mail/Inbox/ more info! Sven
Complex fcc-hook?
I have procmail and mutt set up so mails for lists are automatically put in =lists/listname, and mutt recognizes every subdirectory name in that directory as a list. listname is the part before the , like mutt-users for this one. Default save for other things, people, mainly, is in =people/name, where again, name is the part before the . How can I create fcc-hooks to put sent mail in the right directories?
