Config tool for mutt (Was: Email client poll)
Quoting Brandon Ibach [EMAIL PROTECTED]: A reasonable complaint, for someone just wanting to get into it quickly. A good template .muttrc with comments on each variable is a good way to go, but something a little better couldn't hurt. Perhaps someone would be interested in putting together a sort of "Mutt configuration tool [...] How about writing a module for the dotfile generator..? There already is a module for Elm, I think. Dotfile generator - http://www.imada.ou.dk/~blackie/dotfile/ Morten
upgraded from 0.93 to 0.95.4i
Good day all, I upgraded from 0.93 and I used to type mutt -y and get a list of folders that I could easily monitor. When I went into the a folder, and I pressed "i" to get to the index again - it used to show the same index that I had with mutt -y. After the upgrade that no longer works - am I doing something wrong - so I need to change a setting ? Thanks! Salvatore -- [EMAIL PROTECTED] | http://salvo.reaper.org | ICQ #8084066
Re: Config tool for mutt (Was: Email client poll)
Quoting Randall J. Million [EMAIL PROTECTED]: How about writing a module for the dotfile generator..? There already is a module for Elm, I think. Dotfile generator - http://www.imada.ou.dk/~blackie/dotfile/ It does not support text based configuration... only TCL/Tk. Sure, but what's wrong with having an X GUI config tool for producing the .muttrc ? If you think it should be purely text based and have some ideas on how to do it then that's o.k. too - one doesn't rule out the other. I suggested dotfile because it already contains the framework for making a nice GUI config tool for mutt. Morten
Re: a hook question
On 990720, at 14:40:58, Robert Chien wrote: basically, i want to set signature to .signature.work when sending email to people at work, and set signature to just .signature for the rest. [...] when i send email to co-workers, i can address it as "foo" or "foo@west" (notice the unqualified domain name) or "[EMAIL PROTECTED]" or "[EMAIL PROTECTED]". send-hook . "set signature=.signature" send-hook @(west|(west\.)?sun\.com)$ "set signature=.signature.work" -- David Ellement [EMAIL PROTECTED]
Re: replying w/out signature?
On 0, Aris Mulyono [EMAIL PROTECTED] wrote:
On Tue, Jul 20, 1999 at 01:18:49PM -0600, Steve Talley wrote:
When replying to someone with a quoted (" ") message, is it
possible for mutt to automatically remove their signature (as
denoted with "-- ")?
Assuming you use vi editor,
Try this in .muttrc:
set editor ="vi +'/^[ ,\t]* --/,/^-- /-2d'"
and for jed...
define kill_sig ()
{
push_spot ();
if (bol_fsearch ("--"))
{
push_mark ();
forward_paragraph ();
del_region ();
}
pop_spot ();
}
then just bind this to a key, or run it automatically run the command line,
ie in set editor="jed -f kill_sig".
--
UK Independance Party (NOW WITH 3 MEP's!!): http://www.IndependenceUK.org.uk
Re: Config tool for mutt (Was: Email client poll)
On 0, Morten Bo Johansen [EMAIL PROTECTED] wrote: How about writing a module for the dotfile generator..? There already is a module for Elm, I think. Dotfile generator - http://www.imada.ou.dk/~blackie/dotfile/ It does not support text based configuration... only TCL/Tk. Sure, but what's wrong with having an X GUI config tool for producing the .muttrc ? If you think it should be purely text based and have some ideas on how to do it then that's o.k. too - one doesn't rule out the other. This may be useful, but I think a text based one would be more useful, I for one use X less than once a week, and I use my PC at least 8 hours a day, seeing as Mutt is text based, I think it best to keep any GUI tool also text based, and if any one decides to give it ago, I am sure willing to help. I suggested dotfile because it already contains the framework for making a nice GUI config tool for mutt. I am checking it out now :) cya -- UK Independance Party (NOW WITH 3 MEP's!!): http://www.IndependenceUK.org.uk For GnuPG pupblic key, reply with Subject "request key"
Re: replying w/out signature?
On Jul 21, [EMAIL PROTECTED] wrote:
if (bol_fsearch ("--"))
Actually there should be a space after the dashes:
if (bol_fsearch ("-- "))
Regards,
Holger
Printing through telnet to Windows desktop printer
This is probably old hat to most of you, but I didn't know
about this nifty trick myself and discovered it worked very
well with mutt.
Problem: You ssh/telnet from a Windows machine and use Mutt
for reading mail. You want to easily print your
mail on your local Windows desktop printer.
Solution: ANSI supports printing, if you use e.g. SecureCRT
for ssh connection, you can have SecureCRT trap
print-sequences and send them to your local
printer. And if you use a2ps for formatting, it
will look good too (and you can add "page 1 of 4"
etc.)
This is how:
We found a small code-snippet in the (ugh) Pine
contribution directory. We compiled it simply
with "cc ansiprt.c -o lpransi".
In the .muttrc file you must add something like
set print_cmd="a2ps options | lpransi"
or if you don't want postscript, simply:
set print_cmd="cat - | lpransi"
(do we need the "cat -", or is print_cmd="lpransi" enough?)
This worked perfectly with our local printers. Note
that you can use this (probably) on any system, but
we only tested on Windows (probably depends on your
telnet/ssh client, printer settings, and so on).
This is the file ansiprt.c that we found is attached.
Apologies to those who are grimacing right because this was completely
mandatory to all people that use Mutt. :-)
Cheers!
--
Christian Stigen Larsen -- http://www.sublevel3.org
[EMAIL PROTECTED]http://www.stud.ntnu.no/~chrisl/
/*
* ansiprt.c
*
* Simple filter to wrap ANSI media copy escape sequences around
* text on stdin. Writes /dev/tty to get around things that might be
* trapping stdout. This is actually a feature because it was written
* to be used with pine's personal print option set up to take "enscript"
* output and send it displayward to be captured/printed to a postscript
* device. Pine, of course, uses popen() to invoke the personal print
* command, and interprets stdout as diagnostic messages from the command.
*
* Michael Seibel, [EMAIL PROTECTED]
*
* 21 Apr 92
*
*/
#include stdio.h
#include sys/file.h
#define BUFSIZ 8192
main(argc, argv)
int argc;
char **argv;
{
char c[BUFSIZ];
int n, d;
int ctrld = 0;
if(argc 1){
n = 0;
while(argc ++n){
if(argv[n][0] == '-'){
switch(argv[n][1]){
case 'd':
ctrld++;
break;
default :
fprintf(stderr,"unknown option: %c\n", argv[n][1]);
break;
}
}
}
}
if((d=open("/dev/tty",O_WRONLY)) 0){
perror("/dev/tty");
exit(1);
}
write(d,"\033[5i", 4);
while((n=read(0, c, BUFSIZ)) 0)
write(d, c, n);
if(ctrld)
write(d, "\004", 1);
write(d,"\033[4i", 4);
close(d);
}
Re: Unconfusing mutt about messages from me
Brad Appleton [EMAIL PROTECTED] wrote: As a result, mutt seems to think any and every piece of mail forwarded from my ISP was sent by me, when it reality it wasn't 90% of the time: it was sent by someone else, and forwarded from an alternate address. Can you show us the headers from such a forwarded message? This doesn't sound right at all. I don't want mutt to think its from me unless I'm in the From: header (as opposed to the From_ header). I tried unsetting my $alternates variable but that didn't change anything. As far as I know, Mutt doesn't care what's in the From_ envelope separator unless the From: header is missing. I imagine there might be a way for me to do some header munging, but I'd like to do it without munging headers It sounds to me like some other program already munged the headers when it forwarded the mail between accounts! Are you using a simple .forward file, or is there something more? So is there a way I can configure mutt so that it doesn't use the From_ or Received: headers to see if a message is from me, and uses just the From: header instead? As far as I know, Mutt only uses the From: header if it's there, and never uses the Received: headers to figure out anything. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Command line Mutt question
Chris Zimmerman [EMAIL PROTECTED] wrote: How can I send a message with an attachment from the command line? echo "Here is the enclosing text" | \ mutt -s "Here is your subject" -a attach_filename [EMAIL PROTECTED] -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: a hook question
Robert Chien [EMAIL PROTECTED] wrote: basically, i want to set signature to .signature.work when sending email to people at work, and set signature to just .signature for the rest. I do that, too. Here's my setup: I want to use "localsig" if the message is one in which ALL of the recipients are local users, or "remotesig" if the message has any recipients which are external to my company. My logic might seem weird, but it's because of the "any recipients" part. The send-hook is evaluated for each address in the message to see if it's true. So, I set the signature to the "local" signature, then the next send-hook looks for recipients that are not in my local organization. Since that's the majority of where my mail gets sent, the "remotesig" is usually chosen. send-hook ~A"set signature=~/.localsig" send-hook '! ~C "@.*(convex|(convex|rsn)\.hp)\.com$"' \ "set signature=~/.remotesig" The expression matches [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc. Now that I look at it, though, it needs an update on domain names, but basically it works. :) I'm wondering if my backslashes are in the right places, though, or if I have the right number of them. Since there are two levels of quotes used, maybe I should use "\\." for a dot, or "\\\." to get the proper effect. Any quote/regexp experts know for sure? :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Email client poll
On Jul/20/1999, Brandon Ibach wrote: you really have so many mailboxes that the longer format used by Mutt is that much of a problem? In my case, yes. I've got ... (counting ...) 20 mailboxes defined in my .muttrc (and a few more for archiving purposes, as you said you have too). A way to see them in columns would be very appreciated, and it's one of the very few things that I miss in Mutt. In fact, I think that's the only one :-) -- Roberto Suarez Soto |flame -- reply to Usenet News posting mailto:[EMAIL PROTECTED]| automatically * Corgo - Lugo - Galicia - Spain |
Re: Config tool for mutt (Was: Email client poll)
On Jul/21/1999, Morten Bo Johansen wrote: Sure, but what's wrong with having an X GUI config tool for producing the .muttrc ? If you think it should be purely text based and have some ideas on how to do it then that's o.k. too - one doesn't rule out the other. The perfect solution would be to have both, indeed :-) I think that a purely text-based one could be easily done with Dialog+Perl (or sh, but I think Perl is better for this task). IMHO, at least. -- Roberto Suarez Soto | "You cannot enter here," mailto:[EMAIL PROTECTED]|Said Gandalf, * Corgo - Lugo - Galicia - Spain | And the huge shadow halted.
Re: Config tool for mutt (Was: Email client poll)
on Thu, Jul 22, 1999 at 02:04:44AM +0200, Roberto Suarez Soto [EMAIL PROTECTED] wrote: On Jul/21/1999, Morten Bo Johansen wrote: Sure, but what's wrong with having an X GUI config tool for producing the .muttrc ? If you think it should be purely text based and have some ideas on how to do it then that's o.k. too - one doesn't rule out the other. The perfect solution would be to have both, indeed :-) I think that a purely text-based one could be easily done with Dialog+Perl (or sh, but I think Perl is better for this task). IMHO, at least. And someone could wrap it up in a cgi script so a web interface is used with the config file mailed to the user. BB -- Bevan Broun ph (08) 9380 1587 Computer Systems Officer fax (08) 9380 1065 Dept. Electrical and Electronic Engineering University of Western Australia rm. G70
Re: Config tool for mutt (Was: Email client poll)
On Thursday, 22 July 1999, at 02:04:44 (+0200), Roberto Suarez Soto wrote: The perfect solution would be to have both, indeed :-) I think that a purely text-based one could be easily done with Dialog+Perl (or sh, but I think Perl is better for this task). IMHO, at least. How about Perl for text and Perl/Gtk+ for the GUI? Michael -- "I am not running for office here. I won't keep it purposefully vague. I've heard New Age Life-force trip; I'd rather be dipped in bubonic plague. Take back your free advice I don't accept. I will not play those games. God is not a secret to be kept." -- Newsboys === Michael Jennings [EMAIL PROTECTED] www.tcserv.com PGP Key ID: BED09971 Software Engineer, VA Linux Systems Author, Eterm (www.eterm.org) PGP signature
Re: Email client poll
Quoting Roberto Suarez Soto ([EMAIL PROTECTED]) from Thu, Jul 22, 1999 at 01:57:12AM +0200: On Jul/20/1999, Brandon Ibach wrote: you really have so many mailboxes that the longer format used by Mutt is that much of a problem? In my case, yes. I've got ... (counting ...) 20 mailboxes defined in my .muttrc (and a few more for archiving purposes, as you said you have too). A way to see them in columns would be very appreciated, and it's one of the very few things that I miss in Mutt. In fact, I think that's the only one :-) I'll agree to this. I store messages for each project I'm working on in their own folder, and between that and mailing lists and so forth, I'm up to... hmmm.. $ ls ~/mail | wc -l 57 Wow. Yes, please, columns. -- -- Rich Lafferty --- Sysadmin/Programmer, Information and Instructional Technology Services Concordia University, Montreal, QC (514) 848-7600 - [EMAIL PROTECTED] --
Re: Email client poll
Brandon Ibach [[EMAIL PROTECTED]] wrote: From: dannyman [EMAIL PROTECTED] 2) You can configure it without reading the man page ... errr, I mean, going to the web site, errr, I mean finding the manual, err, I mean, reading the whole fucking manual to find the keyword you want ... errr, I mean, going to the mailing list for an explanation or finding an excellent .muttrc from someone else ... A reasonable complaint, for someone just wanting to get into it quickly. A good template .muttrc with comments on each variable is a good way to go, but something a little better couldn't hurt. Perhaps someone would be interested in putting together a sort of "Mutt configuration tool" which presents all the options through a series of menus, similar to the menu-config tool for Linux kernels (maybe even using the same "dialog" package, or something like it). Then we'd just need to make sure to update the file which drives this system when options are added, changed, obsoleted, etc. I'm curious what benefit you think there is in a menu system over just a well-annotated .muttrc? Presumably what a menu system would do is let you see what each variable does (theoretically using the manual entry for it so we stay consistent) and then let you set the value you want. A .muttrc annotated with the manual entries does the same thing and is viewable/useful on any platform that has any text editor. If you want to group options together in some way to make it easier to find what you're looking for you can do it just as well in a text file as with menus, IMHO. But maybe I'm missing something. Of course, right now we have neither, really. I keep my .muttrc annotated with the manual info, but at the moment it's for .95i. Anyway, some people in this thread have mentioned it being helpful to see good sample .muttrcs, so I'll plug the web site: http://www.mutt.org/links.html#config has links to ~10 different .muttrcs. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "Would you fight to the death, for that which you love? In a cause surely hopeless ...for that which you love?" -- D. McKiernan, _Dragondoom_ PGP signature
Re: Config tool for mutt (Was: Email client poll)
Execellent idea. Then you can have the same functions for both X and text based interfaces, but wrapped up differently. On Wed, Jul 21, 1999 at 06:05:23PM -0700i, Michael Jennings wrote: On Thursday, 22 July 1999, at 02:04:44 (+0200), Roberto Suarez Soto wrote: The perfect solution would be to have both, indeed :-) I think that a purely text-based one could be easily done with Dialog+Perl (or sh, but I think Perl is better for this task). IMHO, at least. How about Perl for text and Perl/Gtk+ for the GUI? Michael -- === Michael Jennings [EMAIL PROTECTED] www.tcserv.com PGP Key ID: BED09971 Software Engineer, VA Linux Systems Author, Eterm (www.eterm.org) -- _ Patrick Seal|"Microsoft isn't evil, they just make [EMAIL PROTECTED] | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds
how do I have outgoing messages copied to outbound folder
I don't think my outgoing email is being copied anywhere. The default folder I have incoming mail to is ~/Mail using procmail. I would like the outbound messages copied into a file such as ~/Mail/outbound My config file is in ~/.mutt/muttrc so far I just have aliases in the file. I found the copy command, in the documentation, but I am not sure how to specify it. How do I specify in my muttrc so outbound messages get copied to ~/Mail/outbound ? brian -- Brian Lavender http://www.brie.com/brian/
