multiline input for fields: To/CC
Hello! From time to time I need to either send an email to a group of people, or respond to such group e-mails. And every time I want to review the list of recipients - I need to scroll to the right. If an address consists of Name email - it gets even worse, because I can see only 2-3 addresses at a time. I looked through the documentation and didn't find any option to set displaying of To/CC fields to multiline mode. Am I missing something, or there is no way to do this in mutt? Thanks! -- Eugene N Dzhurinsky pgpEfITUmzHTd.pgp Description: PGP signature
Re: multiline input for fields: To/CC
On Tue, Feb 11, 2014 at 06:10:47PM -0500, David Haguenauer wrote: I don't know of a way to do exactly what you ask, but, in similar circumstances, I resort to calling edit-headers (bound to `E' by default) from the sending screen. Then I'm thrown back into my text editor, where I can see each To: and Cc: member neatly expanded on its own line. Allright, that might work - but it populates the whole list of headers, which isn't very convenient. Is it possible to limit the list of headers to something like From/To/CC/Subject? -- Eugene N Dzhurinsky pgpRpbwEo2XFc.pgp Description: PGP signature
Re: multiline input for fields: To/CC
On Tue, Feb 11, 2014 at 11:25:16PM -0500, Patrick Shanahan wrote: Yes, look for headers, in the fine manual. Ok, thanks, I solved it already - much better :) I can see all headers in VIM. Is it possible to have this mode to appear on reply immediately? Right now I have VIM opened on r/g keys, so I need to quit it and then press 'E'. Perhaps it mutt could open vim with all the headers populated on reply - that would be handy. Thanks! -- Eugene N Dzhurinsky pgp3zqaNMNQTY.pgp Description: PGP signature
Re: next official release?
On Fri, Jul 08, 2011 at 11:57:06AM CDT, David Champion d...@uchicago.edu wrote: * On 08 Jul 2011, Eugene wrote: Mutt 1.5.21 has been out since September 2010. Does anyone know when the next release will be, whether it's a 1.5.22 developer release or a final 1.6 release? For 1.6: http://dev.mutt.org/trac/roadmap I don't believe there's a commitment to release 1.5.22 at present. I don't recall any patches since 1.5.21 being that significant: see http://dev.mutt.org/hg/mutt/graph/tip?revcount=45 . But if you have a particular reason for rolling one out to get broader testing of recent material, please send it to mutt-...@mutt.org. I'm not subscribed to mutt-dev, so I may miss out on replies. Otherwise, I have no imperative reason to see a new release any time soon. I was concerned that Mutt would fall into Netscape's trap of waiting too long for releases. But then I checked with competing terminal-based mail clients and discovered that Pine's last stable release was in 2006, and Alpine's was in 2008. I guess Mutt's pretty much won the battle of old-school mail clients? :-) -- Computers are useless; they can only give you answers. - Pablo Picasso
next official release?
Mutt 1.5.21 has been out since September 2010. Does anyone know when the next release will be, whether it's a 1.5.22 developer release or a final 1.6 release? -- Life is a sum of all your choices. - Albert Camus
Re: Mutt on Mac Mini
On Thu, Jan 27, 2011 at 05:47:23PM CST, Tim Johnson t...@johnsons-web.com wrote: I currently use mutt on ubuntu 10.04. I am considering getting a Mac Mini - I believe that the OS is 'OS X Snow Leopard'. Is anyone aware of any issues compiling and running mutt on this OS? No issues, been running Mutt on my Macs since Mac OS X Public Beta. Also, there is a port called MacVim that is a first-class Mac OS X application (app bundle and all) that you may want to try first: http://code.google.com/p/macvim/ -- Eugene
Re: Mutt, OS X 10.6.3, and ncurses issue
On Tue, Apr 20, 2010 at 03:12:05PM CDT, Tim Gray lists+m...@protozoic.com wrote: On Apr 20, 2010 at 12:40 PM -0700, John Velman wrote: Does it help if there are more bug reports for the same bug? (Got your later email about duplicates, but replied to the fist one). No clue. I would think it would help by showing it's affecting more people, but who knows. /lurk I'm hit by the non-working arrow keys problems too after updating OS X to 10.6.3. Latest devel, mutt-1.5.20. lurk - Eugene
Re: I cringe but ask anyway: how do I download mutt for Mac 10.4?
On Fri, Feb 26, 2010 at 06:00:56PM CST, fe...@crowfix.com fe...@crowfix.com wrote: I need to download mutt for an old Mac laptop (x86) running 10.4. I tried compiling but have no C compiler. By default, Mac OS X does not install GCC or anything of that sort. If you want those kinds of goodies, find your 10.4 Tiger install disc and install the Xcode Tools package (which gets you all the standard compilers plus the Xcode developer tools) --- and even the X11 package (which gets you the X Window stuff). If you can't find said install disc, sign up for a free online membership with the Apple Developer Connection and download Xcode straight from Apple. http://developer.apple.com/ Hopefully their site will figure out that you're using Tiger and will give you the right link to download Xcode 2.5. http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=19907 Or you can Google for someone else's download of Xcode 2.5, but that's an exercise left for the gentle reader... -- eugene at fsck dot net
Re: Getting mutt to access Mac addressbook with lbdb
On Sun, Oct 25, 2009 at 02:02:22AM CDT, Cameron Simpson c...@zip.com.au wrote: On 23Oct2009 08:04, Trey Sizemore t...@fastmail.fm wrote: | Thanks. I performed a 'sudo port uninstall lbdb' and then did a 'sudo | port install lbdb'. Looking in the /opt/local/lib/lbdb/ directory, I | see: [...] | Note there is no m_osx_addressbook or ABQuery. I have Mac's | addressbook install. Any reason why these would be missing? No, but I will note that I just did this on Leopard (not SL) and although it was there I also had to add the module to this line: METHODS=m_inmail m_osx_addressbook m_passwd m_finger in the file /opt/local/etc/lbdb.rc before it was used. So even after you sort your missing module you may need to tweak a config. There is a Mac OS X Hints article that mentions this too: http://www.macosxhints.com/article.php?story=20041024163030501 -- Eugene
Re: Getting mutt to access Mac addressbook with lbdb
On Fri, Oct 23, 2009 at 11:34:25AM CDT, Trey Sizemore t...@fastmail.fm wrote: On Fri, 2009-10-23 at 08:04 -0400, Trey Sizemore wrote: On Fri Oct 23, 2009 04:26AM, Eugene wrote: On Thu, Oct 22, 2009 at 09:08:23PM CDT, Trey Sizemore t...@fastmail.fm wrote: I previously had this working but now, not so much. I have installed lbdb from MacPorts but perhaps it's missing the needed m_osx_addressbook_query piece. My main reason for asking on the list is to see if anyone has this working with lbdb-0.36. When I try to access my Mac addressbook from within mutt, I get the error: /opt/local/bin/lbdbq: line 74: m_osx_addressbook_query: command not found [...] Thanks. I performed a 'sudo port uninstall lbdb' and then did a 'sudo port install lbdb'. Looking in the /opt/local/lib/lbdb/ directory, I see: [...] Note there is no m_osx_addressbook or ABQuery. I have Mac's addressbook install. Any reason why these would be missing? I should mention as well that this is Snow Leopard, so I'll be curious to see if anyone has this working since upgrading to Snow Leopard. Mine works. Here are my details on my install of lbdb-0.36: - Installed from scratch, not from any ports, in /usr/local. - Installed on Leopard, before upgrading to Snow Leopard. Still works. - Mine installed /usr/local/lib/m_osx_addressbook, a Bourne shell script. - Above-mentioned script defines m_osx_addressbook_query() command. -- Eugene
Re: Getting mutt to access Mac addressbook with lbdb
On Thu, Oct 22, 2009 at 09:08:23PM CDT, Trey Sizemore t...@fastmail.fm wrote: I previously had this working but now, not so much. I have installed lbdb from MacPorts but perhaps it's missing the needed m_osx_addressbook_query piece. My main reason for asking on the list is to see if anyone has this working with lbdb-0.36. When I try to access my Mac addressbook from within mutt, I get the error: /opt/local/bin/lbdbq: line 74: m_osx_addressbook_query: command not found Try this page on the address book section, starting with creating a personal ~/.lbdbrc directory. http://log.antiflux.org/grant/2006/11/22/mutt-with-imap-and-ssl-on-os-x -- Eugene
Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 09:31:17PM CST, Bill [EMAIL PROTECTED] wrote:
Since I would like to add /sw/bin to my /etc/profile I opened it, but only
discovered:
___
# System-wide .profile for sh(1)
if [ -x /usr/libexec/path_helper ]; then
eval `/usr/libexec/path_helper -s`
fi
if [ ${BASH-no} != no ]; then
[ -r /etc/bashrc ] . /etc/bashrc
fi
___
This is not what I expected, and can't think of where I should add /sw/bin/
to my path.
Forget messing with /etc/profile. Did you try my suggestion?
A short time ago, Eugene wrote:
/sw indicates Fink.
http://www.finkproject.org/doc/bundled/install-fast.php
The last command runs a little script to help set up your Unix paths
(and other things) for use with Fink. In most cases, it will run
automatically, and prompt you for permission to make changes. If the
script fails, you'll have to do things by hand.
(If you need to do things by hand, and you are using csh or tcsh, you
need to make sure that the command source /sw/bin/init.csh is executed
during startup of your shell, either by .login, .cshrc, .tcshrc, or
something else appropriate. If you are using bash or similar shells,
the command you need is . /sw/bin/init.sh, and places where it might
get executed include .bashrc and .profile.)
So basically add the line . /sw/bin/init.sh into your ~/.profile or
~/.bash_profile init files. This should add /sw/bin to your PATH, and
set up other Fink-related environment variables as well.
--
Eugene
Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 08:49:04PM CST, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: From: Peter Münster [EMAIL PROTECTED] On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? Your ~/.bash_profile doesn't need any initial references to PATH, because your shell inherits the default value from its parent process. Without creating ~/.bash_profile, open a Terminal.app window and type echo $PATH to see the shell's default value. Going this way, I would go with Peter Münster's suggestion. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? /sw indicates Fink. http://www.finkproject.org/doc/bundled/install-fast.php The last command runs a little script to help set up your Unix paths (and other things) for use with Fink. In most cases, it will run automatically, and prompt you for permission to make changes. If the script fails, you'll have to do things by hand. (If you need to do things by hand, and you are using csh or tcsh, you need to make sure that the command source /sw/bin/init.csh is executed during startup of your shell, either by .login, .cshrc, .tcshrc, or something else appropriate. If you are using bash or similar shells, the command you need is . /sw/bin/init.sh, and places where it might get executed include .bashrc and .profile.) So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. -- Eugene
Re: Mailing List 'To' in Index
On Tue, Dec 11, 2007 at 08:54:48PM CST, Michael Pobega [EMAIL PROTECTED]
wrote:
On Wed, Dec 12, 2007 at 03:46:22AM +0100, Henrik Enberg wrote:
Michael Pobega [EMAIL PROTECTED] writes:
I'd like instead of seeing mutt-users@mutt.org in the 'To' area of the
index, see who the mail is actually from. I remember I used to have Mutt
set up to do this, but I lost all of my configuration files in a
partitioning accident.
Change %L to %F in index_format.
How would I go about doing that in my ~/.muttrc exactly?
The manual says that the configuration variable index_format is type string
with a default value %4C %Z %{%b %d} %-15.15L (%4l) %s.
http://www.mutt.org/doc/manual/manual-6.html#index_format
Since strings setting syntax follow the complex grammar set foo=bar,
try something like this:
set index_format=%4C %Z %{%b %d} %-15.15F (%4l) %s.
--
Eugene
Re: viewing pdf jpgeg etc attachment
On Wed, Sep 26, 2007 at 01:00:52PM CDT, Joseph [EMAIL PROTECTED] wrote: I have a problem with basic setting, it should be straight forward but I am still missing something. I have in a file autoview settings: set mailcap_path=~/.mailcap:/etc/mailcap application/pdf; xpdf %s image/jpeg; kuickshow %s but when I strt mutt I get an error message: Error in /home/joseph/.mutt/autoview, line 8: application/pdf: unknown command Error in /home/joseph/.mutt/autoview, line 9: image/jpeg: unknown command [...] Where does xpdf and kuickshow reside? If you specify the full path for each command in your mailcap, does that work? -- Eugene
Incorrect attachment displaying when message is signed
Hi all. I have a problem with multipart MIME signed messages with attachments: mutt doesn't display attached files correctly, they are displayed as the part of message. Attached file is example of such message, sent with icedove. Any advice on how to fix it? Thanks. -- WBR, Eugene Krivdyuk signed_multipart.msg.bz2 Description: Binary data
Re: Autoview images in the pager - w3m
On Sat, Oct 05, 2002 at 03:18:23PM +0200, Sven Guckes wrote: : : all you need is this auto_view text/html in your mutt setup : and the following in your mailcap file: : : text/html ; w3m -dump -force_html %s ; copiousoutput : text/htm; w3m -dump -force_html %s ; copiousoutput : message/html; w3m -dump -force_html %s ; copiousoutput : message/htm ; w3m -dump -force_html %s ; copiousoutput message/html? Is this an official MIME entry? -- Eugene Lee [EMAIL PROTECTED]
Re: Autoview images in the pager
On Sat, Oct 05, 2002 at 10:35:00PM -0400, Rob Reid wrote: : : At 8:21 AM EDT on October 5 Viktor Lakics sent off: : : I have a crazy idea, I wanted to ask you about: Has anyone ever : tried to work out how to autoview graphics inside mutt? : : You might know this already, but a common spammer tactic is to include images : in their html mails like img : src=http://spam.server.com/Viktor_actually_read_this_spam.gif; that let : them know that you actually read their spam, *if* you read the message in a : graphical browser. From then on you can count on that address receiving the : GSSSP (Gross Solar System Spam Product). If you open an HTML email with a web browser with ad-blocking features, you should be okay. Also, you can set your browser to not load images automatically. -- Eugene Lee [EMAIL PROTECTED]
looking for a better send-hook
The command: send-hook '~h address' command causes Mutt to generate an error h: not supported in this mode that isn't documented anywhere. How do I get a send-hook to match a pattern within a custom header of the current message? Thanks in advance. -- Eugene Lee [EMAIL PROTECTED]
Re: looking for a better send-hook
On Wed, Sep 25, 2002 at 03:34:50PM +0200, Sven Guckes wrote: : : * Eugene Lee [EMAIL PROTECTED] [2002-09-25 12:33]: : : The command send-hook '~h address' command : causes Mutt to generate an error h: not supported : in this mode that isn't documented anywhere. : : one more thing to fix in the documentation then. BTW, I get the same error with send-hook and ~B too. :-) : How do I get a send-hook to match a pattern within : a custom header of the current message? : : do you mean current header as in generated with 'my_hdr'? Nope. That came off as vague. Let me specify. I'm looking at the header Received: and trying to find a match within for the pattern for email_address_pattern. There's no search pattern to look at the Received: header (since Received: is almost always a multi-line header, the docs don't say whether its other search patterns match multi-line headers). That's where I'm stuck with send-hook and trying to use ~h. So to clarify what I meant above, current message is the message that I've currrently selected in index mode, or that I'm currently viewing. And I meant custom header to describe a header that's not specified by existing Mutt search patterns. I know message-hook supports ~h, but it only activates when I view the current message. And I don't want to remember to view a message to activate the hook. This wouldn't be a such problem with your standard GUI mail client because selecting the current message also means viewing the current message. But selecting and viewing are two different things according to Mutt, which IMO has unnecessarily complicated the way some hooks work. Sven, thanks for the help! -- Eugene Lee [EMAIL PROTECTED]
tabbing in change mailbox altered between 1.2.x and 1.4
When changing mailboxes, the tabbing feature that tries to autocomplete mailbox filenames got altered. Let's say I have the following mailboxes: ~/Mail/foo ~/Mail/foobar ~/Mail/food I press 'c' to change mailboxes and type in +fo then TAB. In 1.2.x, the autocompletion feature expands to +foo. I press TAB again to show all the mailboxes above as they match +foo. In 1.4, the autocompletion feature expands to +foo. I press TAB two more times to show all the matching mailboxes. That's three TABs. But if I start with +foo and press TAB twice, it lists all the matching mailboxes, like the 1.2.x behavior. The 1.2.x behavior of pressing TAB twice is guaranteed to list all the matching mailboxes. However, the 1.4 behavior is not guaranteed, is not predictable, and depends on whether the initially typed mailbox pattern gets expanded. This is bad as I have a few macros that depend on the guaranteed 1.2.x behavior of two TABs. I couldn't find anything in the manual that defines the filename autocompletion behavior. Is there anything that can be done to fix things? Or it's a feature, not a bug? Suggestions are appreciated. Thanks in advance. -- Eugene Lee [EMAIL PROTECTED]
compile errors on macosx and disable-iconv
@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mh.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_dotlock.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_sasl.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_socket.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_ssl.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_ssl_nss.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mutt_tunnel.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/muttlib.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mx.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pager.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/parse.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/patchlist.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pattern.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgp.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgpinvoke.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgpkey.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgplib.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgpmicalg.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgppacket.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgppubring.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pop.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pop_auth.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pop_lib.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/postpone.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/query.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/recvattach.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/recvcmd.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/remailer.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/resize.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/rfc1524.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/rfc2047.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/rfc2231.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/rfc822.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/score.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/send.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sendlib.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sha1.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/signal.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sort.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/status.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/system.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/thread.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/url.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/utf8.Po@am__quote@ @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/wcwidth.Po@am__quote@ -- Eugene Lee [EMAIL PROTECTED]
Re: compile errors on macosx and disable-iconv
On Fri, Sep 13, 2002 at 02:19:49AM -0700, Eugene Lee wrote: : : I'm having problems compiling mutt-1.4i on Mac OS X 10.2. I already : discovered that --without-iconv doesn't work and have applied Lars' : patch-1.4.lh.noiconv.1 patch (it says patch.1.3.28.lh.noiconv in the : patched ChangeLog) that added --disable-iconv. [...] I had a short burst of exchanges with Lars Heckling, and he helped me to resolve the problem. If anyone needs Mutt sans the recommended libiconv support, feel free to bug me for the update. Thanks Lars! Hmmm, is there an update planned for mutt-1.4 in the near future? -- Eugene Lee [EMAIL PROTECTED]
Re: replying to and quoting an HTML attachment
On Thu, Jul 11, 2002 at 09:44:53AM -0700, Gary Johnson wrote: : : On Wed, Jul 10, 2002 at 06:44:46PM -0700, Eugene Lee wrote: : : Now if I can only figure out how to keep both entries and get Mutt to : let me select between the two methods... : : You can. Just put them in you mailcap in this order: : : text/html; links %s; nametemplate=%s.html : text/html; links -dump %s; nametemplate=%s.html; copiousoutput Ahhh. At one time, I did have both entries, but in reversed order. : This is covered in the mutt manual in the section on Search Order : (5.3.3.2) under Advanced mailcap Usage (5.3.3). Another Ahhh. I think I got hung up on this line in the manual: When searching for an entry in the mailcap file, Mutt will search for the most useful entry for its purpose. Mucho thanks! -- Eugene Lee [EMAIL PROTECTED]
replying to and quoting an HTML attachment
I looked in the archives and couldn't find a specific answer this one. I receive several HTML messages that arrive as an attachment with no plain text equivalent in the main message body or another attachment. When I reply to these messages, how do I configure Mutt to convert the HTML attachment into plain text, quote it, and finally edit it? Or is this a mailcap issue? Thanks in advance. -- Eugene Lee [EMAIL PROTECTED]
Re: replying to and quoting an HTML attachment
On Wed, Jul 10, 2002 at 05:36:43PM -0700, Gary Johnson wrote: : : On Wed, Jul 10, 2002 at 05:06:12PM -0700, Eugene Lee wrote: : : I receive several HTML messages that arrive as an attachment with no : plain text equivalent in the main message body or another attachment. : When I reply to these messages, how do I configure Mutt to convert the : HTML attachment into plain text, quote it, and finally edit it? Or is : this a mailcap issue? Thanks in advance. : : It's at least partly a mailcap issue. If you already have mutt and : mailcap configured to display HTML attachments as plain text in the : pager, replying should just work as you described. Otherwise, you : will need an entry like this in your mailcap: : : text/html; w3m -dump %s; nametemplate=%s.html; copiousoutput Thanks to you and John Iverson and Will Yardley for the responses. It turned out to be my mailcap entry. I had this: text/html; links %s; nametemplate=%s.html when I really needed this: text/html; links -dump %s; nametemplate=%s.html; copiousoutput Now if I can only figure out how to keep both entries and get Mutt to let me select between the two methods... -- Eugene Lee [EMAIL PROTECTED]
Weird bug while compiling 1.4i with iconv 1.8
Hi, everybody! While running configure script it finds iconv.h Determines that type iconv_t is defined. But never finds declaration for iconv function... libiconv from ftp.gnu.org was installed ok. Gettext from the same place compiled great with libiconv. BTW There was no internal system support for icnv functions. If someone has a hint for me, please let me know about it. Thanks in advance. -- Eugene Paskevich | *==(--- | Plug me into [EMAIL PROTECTED]| ---)==* | The Matrix Public PGP key:mailto:[EMAIL PROTECTED]?subject=publicpgpkey Fingerprint: 03 BE 52 C8 41 8C 10 DC 2F 81 A2 21 28 5E D3 12
send-hook and setting To: header
I'm on a mailing list with an email address of A. The same mailing list also works with an alternate email address of B. Both addresses are listed in the lists command. And doing 'L' (list-reply) generates the appropriate To: A or To: B headers. I'd like to change this slightly. On messages sent to the mailing list via the alternate address B, I want 'L' to generate the headers using the main address A, i.e. To: A. Messages sent to the main address A are fine and can be left alone. I'm guessing a send-hook will work, but I haven't been able to divinate the right combination. Thanks in advance for any suggestions. -- Eugene Lee [EMAIL PROTECTED]
Re: send-hook and setting To: header
On Thu, Apr 04, 2002 at 01:00:40PM -0800, Michael Elkins wrote: : : Eugene Lee wrote: : : I'd like to change this slightly. On messages sent to the mailing list : via the alternate address B, I want 'L' to generate the headers using : the main address A, i.e. To: A. Messages sent to the main address A : are fine and can be left alone. I'm guessing a send-hook will work, but : I haven't been able to divinate the right combination. : : You can't do this in Mutt. If you really want to munge the headers, : your best bet is to do it with procmail before the mail gets delivered. : send-hook only allows you to change settings, not edit the recipient : list. Ahhh. I was afraid of this. But thanks for the confirmation. Do you or anyone else know if this can be done in version 1.3.28? -- Eugene Lee [EMAIL PROTECTED]
Re: send-hook and setting To: header
On Thu, Apr 04, 2002 at 05:22:51PM -0500, David T-G wrote: : : Were I you I'd have procmail recognize messages to/from B and rewrite it : as to/from A so that mutt just knows about A. Yup, that's easy enough for a single email address. But I've not figured out how to do so while preserving multiple recipients. The ideal recipe would tranform these headerfields: To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], B, [EMAIL PROTECTED] into these: To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], A, [EMAIL PROTECTED] Old-Cc: [EMAIL PROTECTED], B, [EMAIL PROTECTED] (and similarly if the address appeared in the To: header) -- Eugene Lee [EMAIL PROTECTED]
Re: Why no new stable-branch version?
On Sun, Oct 28, 2001 at 11:04:20AM +0100, Thomas Roessler wrote: : : On 2001-10-28 04:48:52 -0500, Russell Hoover wrote: : : Would someone from the mutt developer community mind giving a : heads-up as to the philosophy or current thinking about this : situation? : : 1.3.23 is pretty stable now - which is why 1.3-branch : announcements come on mutt-users, and why the 1.3 tar balls are not : in the devel/ subdirectory. [...] : In fact, you could legitimately say that there is currently no true : unstable branch - and that's basically because releasing a beta : version (and, even more so) releasing a new stable version will : inevitably uncover those bugs which don't come up with the usage : patterns of developers (or the bold hearts doing beta tests). I wonder if Russell is thinking of something more akin to the FreeBSD development cycle where there are two branches: FreeBSD-CURRENT and FreeBSD-STABLE. FreeBSD-CURRENT is basically bleeding-edge development where all the wacky new stuff is started. FreeBSD-STABLE is slow-paced development, with more bug fixes and newer features that's gone through some testing in FreeBSD-CURRENT. The releases are created from the FreeBSD-STABLE branch around 3-4 times a year. However, I don't know if Mutt or the Mutt community is large enough to warrant this system. Waiting for such a long time between releases usually means that there's too much work and too few developers, or the next release is a huge radical departure from the previous release (features, code base, etc.). -- Eugene Lee [EMAIL PROTECTED]
Re: Global Operation on Tagged Messages
On Fri, Oct 19, 2001 at 11:31:46AM -0800, Tim Johnson wrote: : : I would like to tag a number of messages, and then : perform the same operation on all of them. : : Example 1: Tag some messages, then delete them all at once. : : Example 2: Tag some messages, then save them all to a particular :archive. : : 1)How may I do this? solution 1) ;d solution 2) ;s : 2)Where is documentation on this? http://www.mutt.org/doc/manual/manual-4.html#ss4.3 -- Eugene Lee [EMAIL PROTECTED]
Re: procmail
On Sun, Aug 19, 2001 at 05:36:25AM -0400, Ken Weingold wrote: : On Sun, Aug 19, 2001, Suresh Ramasubramanian wrote: : Ken Weingold mutt [19/08/01 05:22 -0400]: : : One thing, too. It is possible that the MTA on your server is : ignoring procmail. I had this issue once on a shell account I got. : they use dmail, and it did just this. I don't have root there, and : the admin is impossible to get hold of, so I gave up. Just a thought. : : A .forward file in your homedir should have solved that? : : Nope. Completely ignored. If your MTA is not configured to use Procmail, or it's configured to ignore ~/.forward (or any other user-maintained config file), you're pretty much stuck. If your admin is physically accessible, try bribing the person with food. -- Eugene Lee [EMAIL PROTECTED]
[OT] Re: mutt porting to Max OS-X ?
On Fri, Aug 17, 2001 at 01:58:34AM -0500, Aaron Schrab wrote: : : The main problem with the normal sendmail config on there is that : sendmail doesn't like some of the permissions. This can be fixed by : adding with the following line in /etc/mail/sendmail.cf: : : O DontBlameSendmail=GroupWritableDirPathSafe OS X made the IMHO stupid decision to make / 775. The only reason AFAIK this was done was so that old Mac OS installer programs running in Classic mode within OS X could leave README docs and other miscellania in the root directory. -- Eugene Lee [EMAIL PROTECTED]
[OT] Re: mutt porting to Max OS-X ?
On Fri, Aug 17, 2001 at 12:42:55PM +0530, Suresh Ramasubramanian wrote: : Aaron Schrab mutt [17/08/01 01:58 -0500]: : : O DontBlameSendmail=GroupWritableDirPathSafe : : So it's true that / is world writeable in OSX? Ouch. Not world-writable, just group-writable. Still bad. : A chmod or two (and avoiding the use of HFS - which might break : compatiblity with older Mac OSen) might be a great idea before : compiling any *nix stuff - esp sendmail - on OS X. Actually, most Unix stuff compiles pretty well on OS X on an HFS+ volume with its case-insensitive case-preserving ways. But there are issues with a few things like Perl that installing things its HTTP script /usr/bin/HEAD, which on an HFS+ system clobbers /usr/bin/head. Java has problems because apparently some class files only differ by case (where the capitalized version has a set of classes, and the lowercase version is just code). -- Eugene Lee [EMAIL PROTECTED]
Re: mutt porting to Max OS-X ?
On Fri, Aug 17, 2001 at 10:17:04AM -0700, Seraphim Larsen wrote: : On Thu Aug 16 16:25, Eugene Lee wrote: : : Mutt compiles on Mac OS X without much problems. : : I'm glad to hear it! I've had mutt-1.2.5 compiled with ncurses-5.2 for quite some time now (it's been fine since OS X PB). I need to experiment a bit more with it and fetchmail. And I want to see if I can run both Mutt and Mail.app that ships with OS X, and have both look at the same mailboxes. Anyone else tried this already? -- Eugene Lee [EMAIL PROTECTED]
Re: set subject on send-hook?
On Thu, Aug 16, 2001 at 04:05:03PM -0300, Fernan Aguero wrote: : : So here's my first question: is it possible to set the subject on a : send-hook? [...] : I've tried the following send-hook, which failed: : : send-hook info 'set my_hdr Subject: [info]' send-hook info 'my_hdr Subject: [info]' BTW, this hook only works if the person you're sending to has the word info in the email address. So you could so something like: send-hook '(email1|email2|...)' 'my_hdr Subject: [info]' -- Eugene Lee [EMAIL PROTECTED]
Re: mutt porting to Max OS-X ?
On Thu, Aug 16, 2001 at 01:35:54PM -0700, Seraphim Larsen wrote: : : Anyone know of any attempted ports of Mutt to Max OS-X? Mutt compiles on Mac OS X without much problems. If you're talking about a GUI version, Muttzilla might compile with XFree86 installed. If you're talking about a Cocoa or Carbon version, I dunno. -- Eugene Lee [EMAIL PROTECTED]
Re: Default save-hook
On Mon, Aug 13, 2001 at 08:24:25AM -0700, David Ellement wrote: : On 010813, at 09:47:00, Andrei Zmievski wrote : : [...] Right now if I have email from : [EMAIL PROTECTED] and I hit 'save', it prompts me for where to save it to : and the default location is =joeman. What I want it to be is : =people/joeman.. : : Perhaps 'save-hook . =people/%u' or 'save-hook !~l =people/%u' will : do what you want. Is '%u' documented in the Mutt 1.2.5 docs as a valid save-hook sequence? -- Eugene Lee [EMAIL PROTECTED]
Re: Default save-hook
On Mon, Aug 13, 2001 at 11:41:48AM -0400, David T-G wrote: : ...and then Eugene Lee said... : % : % Is '%u' documented in the Mutt 1.2.5 docs as a valid save-hook sequence? : : Now that you know what it is and searching is trivial, you should look : it up for yourself and see. : : It is. Well, it's documented in index_format as well as folder_format : and pgp_entry_format, though it has different meanings in attach_format : and status_format; I would figure that those (especially index_format, : which has just about everything in it) would be good places to start when : looking for such things. I don't see anything in the Mutt 1.2.5 docs that say, Here are the valid percent sequences that are recognized and expanded by save-hooks. If it's there, it's either written in a very non-intuitive manner or I'm going blind. :) If it's not there, maybe it's a Mutt 1.3 feature? -- Eugene Lee [EMAIL PROTECTED]
Re: Max Size for Attachment
On Wed, Jul 11, 2001 at 06:41:05AM +0700, Efata wrote: : : I have fetch email from my friend with attachment file 2.8 MB. And I read : this email with mutt and I view attachment and save it. But after I save the : size change only 2M. It is right or not? This is normal. Attachments are often encoded to prevent data corruption when sent via email. But this encoding process often inflates the size of attachments by 30-40%. So with you, an inflated size of 2.8 MB and an actual size of 2 MB is quite normal. -- Eugene Lee [EMAIL PROTECTED]
Re: Documentation about signature seperator
On Sun, Jul 01, 2001 at 06:42:12PM +0200, Rafael Laboissiere wrote: : : * Vincent Lefevre [EMAIL PROTECTED] [2001/06/30 21:41]: : : In article [EMAIL PROTECTED], : Michael Elkins [EMAIL PROTECTED] wrote: : : AFAIK there is no such documentation. It's merely a tradition that was : carried over from USENET. Very few mail clients seem to do this anymore. : : AFAIK, the sig separator is documented in the latest Usenet drafts. : See http://www.landfield.com/usefor/. : : More precisely in section 4.3.2. Body Conventions of the latest : Usefor draft: : :http://www.landfield.com/usefor/drafts/draft-ietf-usefor-article-04.txt Pretty strong language too! If a poster or posting agent does append such a signature to an article, it MUST be preceded with a delimiter line containing (only) two hyphens (ASCII 45) followed by one SP (ASCII 32). -- Eugene Lee [EMAIL PROTECTED]
compiling Mutt with ncurses
When I built ncurses-5.2, I set the installation prefix to /usr/local. The libraries are in /usr/local/lib, which I expect. But the header files are grouped into a /usr/local/include/ncurses directory. The configure script for mutt-1.2.5i can't figure this out --- or maybe I can't figure out how to set --with-curses=DIR. Is there a nice way to this work? Or is it time to hack the configure script? Any suggestions are welcome! -- Eugene Lee [EMAIL PROTECTED]
unable to remove a macro
I wrote about this a few days ago, and the solution suggested looked like it worked, but actually didn't. I want to set up a keyboard macro that changes depending on the current folder; otherwise, it should do nothing in other folders. It was suggested that the noop function available to bind also works with macro. So I tried this: folder-hook . macro index X noop However, in other folders where macro is supposed to do nothing, it instead changes my sort order (the oo part is specifically the cause of this change). The docs do not claim that macro honors the special noop function that bind recognizes, and Mutt 1.2.5 works correctly according to the docs. Is there an undocumented way to remove a macro? If not, is noop recognized by macro in the 1.3 series? -- Eugene Lee [EMAIL PROTECTED]
Re: unable to remove a macro
On Thu, Jun 14, 2001 at 09:28:22AM +0100, Dave Pearson wrote: : : On Thu, Jun 14, 2001 at 01:02:57AM -0700, Eugene Lee wrote: : : [SNIP] Is there an undocumented way to remove a macro? : If not, is noop recognized by macro in the 1.3 series? : : Simply `bind' noop to the key that you've defined the macro for. [example deleted] Ah-ha! Thanks for the tip! I think I need to get some sleep and stop thinking within the box... -- Eugene Lee [EMAIL PROTECTED]
unsetting macros
Is there a way to unset a macro in Mutt? I couldn't find a noop-like sequence that bind recognizes. I have different macros set to the same keys for certain folder hooks, but I'd like for those same keys do nothing on other folders. -- Eugene Lee [EMAIL PROTECTED]
Default subject
When replying to a message with an empty subject, Mutt defaults the subject to you mail. Is there a way I can change this? Thanks, Eugene
unhook bug
When I enable this setting: folder-hook . 'unhook folder-hook' I get this: $ mutt Segmentation fault (core dumped) Bug or feature? :) $ mutt -v Mutt 1.2i (2000-05-09) Copyright (C) 1996-2000 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.2.18pre20 [using slang 10202] Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/etc" SYSCONFDIR="/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Eugene Lee [EMAIL PROTECTED]
next Mutt release?
I'm just curious to ask is there a timetable for Mutt 1.3 to go stable and be released (Mutt 1.4 I assume?). It would be neat if Mutt had a modular structure that lets people add functionality without having to significantly modify the core. -- Eugene Lee [EMAIL PROTECTED]
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 09:37:25AM +, Chris Green wrote: : : Is there a simple way to change the subject line of an incoming : message before saving it? : : It would be particularly useful to do this when saving the messages : one gets when subscribing to mailing lists. I keep these in a single : mailbox and because of the inconsistency of the subject lines used : it's often quite hard to find the subscription details for a : particular list. If I could just change the subject line before : saving the message I could make my life much easier. For mailing lists, I usually add the mailing list address to my "subscribe" line and let 's' automatically save messages to a file usually named after the mailing list. -- Eugene Lee [EMAIL PROTECTED]
Re: Changing subject line in received mail
On Thu, Mar 08, 2001 at 11:15:10AM +, Chris Green wrote: : On Thu, Mar 08, 2001 at 09:50:17PM +1100, David wrote: : Chris Green wrote: : The problem is that the subject lines from the various different : mailing list servers aren't consistent and many don't even have the : name of the mailing list in them. Thus it isn't always easy looking : at the index of my 'subscriptions' mailbox to see which message is : the one I want. : : Even doing what you suggest won't help as 's' will save the message : to a mailbox named after the From: line of the message from the : mailing list server which I suspect will be just as inconsistent as : the subject line is and won't always provide the mailing list name : either. : : Perhaps you should write a procmail recipie to add the name of the : mailing list to the subject it sounds like that would be the best : solution for you. : : No, that won't help as I only want to do this on the one or two : messages that come from the E-Mail request server not to messages : that come from the list itself. Writing a procmail recipe to modify : just one or two messages seems a little like overkill to me. At the same time, trying to write a Mutt save-hook to save just one or two messages seems a little like overkill to me, too. :-) : I definitely don't want the name of the mailing list in the subject : of normal messages from the mailing list as I already know which list : they're from because they have been routed to a specific mailbox by : procmail. Based on the same observations you made above, that "subject lines from the various different mailing list servers aren't consistent", I prefer to add the mailing list email address to Mutt's "subscribe" setting and let Mutt come up with an appropriate mailbox filename. I then manually save messages from the mailing list server software to the same mailbox. -- Eugene Lee [EMAIL PROTECTED]
Re: off-topic (printing man pages)
On Tue, Mar 06, 2001 at 02:50:23PM +0800, Horace G. Friend III wrote: : : This is off-topic but I need a quick fix so I hope you'll oblige. : I still do double-sided printing in windoze because of my printer : (HP710C). :( I'd like to convert several man pages into plain : text and save it to my windoze dir. How can I do that? You'll probably get better-looking results if you run some kind of man2html converter so that you can read stuff via a web browser. -- Eugene Lee [EMAIL PROTECTED]
Re: How to do a regexp
On Thu, Feb 22, 2001 at 10:00:51PM -0500, Joe Philipps wrote: : On Mon, Feb 19, 2001 at 06:21:58PM -0500, Bruce A. Petro wrote: : : Can you point me to some book or doc or man that says things in fairly : plain english as you did??? I'm finding a lot of docs on regexps that : are hard to translate when you are just starting out like me. : : "man 5 regexp" on HP-UX : "man grep" or "man ed" on almost all systems : The info. in info on a GNU system (e.g., GNU/Linux) is usually : helpful, or failing that, the info within GNUEmacs (providing the info : documentation for it was installed/kept on your system). By default, : Ctrl-H i gets you into GNUEmacs info mode once in the editor itself. There's a book on the VI editor by O'Reilly and Associations that has a nice section on regular expressions, with explanations and examples that are pretty novice-friendly as I've seen. -- Eugene Lee [EMAIL PROTECTED]
compiling Mutt on Mac OS X
I'm trying to compile Mutt 1.2.5i on Mac OS X and I'm getting a bunch of warnings in the compilation: In file included from extlib.c:30: lib.h:101: warning: ANSI C forbids const or volatile functions cc -DSHAREDIR=\"/usr/local/share/mutt\" -DSYSCONFDIR=\"/usr/local/etc\" -DBINDIR=\"/usr/local/bin\" -DHAVE_CONFIG_H=1 -I. -I. -Iintl -I/usr/local/include -I/usr/local/include -I./intl -Wall -pedantic -g -O2 -c sha1dgst.c In file included from /System/Library/Frameworks/System.framework/Headers/bsd/machine/types.h:30, from /System/Library/Frameworks/System.framework/Headers/bsd/sys/types.h:70, from /System/Library/Frameworks/System.framework/Headers/bsd/stdio.h:64, from sha1dgst.c:59: /System/Library/Frameworks/System.framework/Headers/bsd/ppc/types.h:75: warning: ANSI C does not support `long long' /System/Library/Frameworks/System.framework/Headers/bsd/ppc/types.h:76: warning: ANSI C does not support `long long' In file included from sha_locl.h:59, from sha1dgst.c:63: /System/Library/Frameworks/System.framework/Headers/bsd/stdlib.h:181: warning: ANSI C does not support `long long' /System/Library/Frameworks/System.framework/Headers/bsd/stdlib.h:183: warning: ANSI C does not support `long long' I'm not so worried about the overlapping function names, but I'm a bit concerned with messasges like "ANSI C does not support `long long'". It does compile, and the binary seems to work pretty well. Any thoughts or suggestions are appreciated, thanks! -- Eugene Lee [EMAIL PROTECTED]
Re: alias question
On Sat, Jan 20, 2001 at 06:57:19AM -0800, Dale Morris wrote: : : I want to be able to add a little information about some of my aliases, such : as who the person is or maybe their phone number, or whatever. Can I just : add the information, comment it out with ##, or is there a better way? : I'm not the greatest with Unix scripts.. Mutt scripts, including the aliases files, can be commented out by putting a # as the first character on the line. So you can do things like so: alias eugene "Eugene Lee" [EMAIL PROTECTED] # home phone is 987-654-3210 # work phone is 123-456-7890 # note: he is really freaky! -- Eugene Lee [EMAIL PROTECTED]
Re: reloading mutt aliases file
On Tue, Dec 26, 2000 at 11:15:30AM +0100, Jesper Holmberg wrote: : : I have tried to put an unalias statement in my alias-file, to reset : everything before reloading the file. However, no matter if I use : : unalias . : : or : : unalias * : : it doesn't seem to work: it doesn't forget all previously defined aliases : as I expect it to do. In fact, it doesn't forget anything. : : What do I do wrong? There appears to be no method to "unload" all defined aliases in memory, at least according to the current docs. The "unalias" command doesn't seem to accept wildcards or shortcuts. -- Eugene Lee [EMAIL PROTECTED]
Re: reloading mutt aliases file
On Fri, Dec 22, 2000 at 03:54:26PM -0500, Ken Weingold wrote: : : Stupid question. How do I reload my .mutt.aliases from within mutt? : I try at the ':' 'source .mutt.aliases' but it doesn't. It goes right : back into mutt with no error, but if I try to save an alias with the : same name I just deleted from it, it says I still have that alias. I : also tried 'source ~/.mutt.aliases' , etc. Once an alias is loaded into memory, it's stays there. It doesn't go away until you quit Mutt, or use the "unalias" command to remove the alias from Mutt's memory. -- Eugene Lee [EMAIL PROTECTED]
Re: folder-hook pattern matching
On Thu, Dec 21, 2000 at 07:48:20PM +0100, Michael Tatge wrote: : Eugene Lee muttered: : : If I had the following mailboxes that all start with the letter 'b': : : ~/Mail/bob : ~/Mail/bobby : ~/Mail/info/bricks : ~/Mail/network/tools/bing : : Is it possible to make a single folder-hook pattern that matches all of : these mailboxes? : : If you want to match exactly these folders: : : folder-hook =bob|=bobby|=info/bricks|=network/tools/bing '...' : assuming you set folder="~/Mail" That's a pain, because I'd have to modify my folder-hook if these folders were to move around in the filesystem. : The regexp matches any sub-string of the whole path. So : folder-hook test '...' would match ~/Mail/test as well as : /test/Mail/dummy_folder. That's why the =/+ shortcut for $folder is so : useful. But there seems to be no way to match all mailboxes that begin with the letter 'b'. In other words, I can't make a folder-hook perform a match on *only* the mailbox name itself and not the absolute pathname. If there's a way to do this, I'd love to know how. -- Eugene Lee [EMAIL PROTECTED]
folder-hook pattern matching
If I had the following mailboxes that all start with the letter 'b': ~/Mail/bob ~/Mail/bobby ~/Mail/info/bricks ~/Mail/network/tools/bing Is it possible to make a single folder-hook pattern that matches all of these mailboxes? -- Eugene Lee [EMAIL PROTECTED]
folder-hook pattern matching
I'm trying to set up a folder-hook that matches all mailboxes I read beginning with a specific character. However, the ^ metacharacter does not appear to work at all for some reason. Here's an example that should work but does not: folder-hook ^b 'save-hook . =bobby' Putting single quotes or quotation marks around the pattern has no effect. I must be missing something simple, yet I can't figure it out. Any tips would be appreciated. Mutt 1.2i (2000-05-09) Copyright (C) 1996-2000 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.2.18pre20 [using slang 10202] Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/etc" SYSCONFDIR="/etc" -ISPELL -- Eugene Lee [EMAIL PROTECTED]
Re: folder-hook pattern matching
On Sun, Dec 17, 2000 at 04:02:37AM -0800, Eugene Lee wrote: : : I'm trying to set up a folder-hook that matches all mailboxes I read : beginning with a specific character. However, the ^ metacharacter does : not appear to work at all for some reason. Here's an example that : should work but does not: : : folder-hook ^b 'save-hook . =bobby' Figured it out, with a bit of a tip from David Champion (thanks dude!) : folder-hook =^b 'save-hook . =bobby' Of course this reminds me that the pattern either matches the entire absolute filesystem pathname or any piece of the absolute pathname. There's no shortcut to match a relative pathname. For example, the above working folder-hook works for this path: /home/eugene/Mail/bob but does not work for this path: /home/eugene/Mail/info/bills It would be nice to have another mailbox shortcut that would act as a pseudo directory separator that refers to your current directory. Too bad this doesn't work: folder-hook ./^b 'save-hook . =bobby' -- Eugene Lee [EMAIL PROTECTED]
strange alias expansion
In Mutt, why does the alias: alias john John S. Doe [EMAIL PROTECTED] get expanded to: To: "John S . Doe" [EMAIL PROTECTED] And is there any way to fix it? Thanks in advance. Mutt 1.2i (2000-05-09) Copyright (C) 1996-2000 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.2.16 [using slang 10202] Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/etc" SYSCONFDIR="/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. -- Eugene Lee [EMAIL PROTECTED]
Re: Is there a Pine-to-Mutt FAQ?
On Sat, Oct 21, 2000 at 11:27:17AM +0530, Suresh Ramasubramanian wrote: [Pine-to-Mutt HOWTO or FAQ] : Mutt-Newbie list? hint, hint I'll write a bit of this if possible but : there's already a page at http://www.socha.net with pine (and another with : gnus) tips, so if Sven and Robin Socha don't mind, a little cut-n-paste seems : called for ;) One of my friends who loves his Pine tried out Mutt and hates it, because Mutt doesn't have a GUI method of configuring its settings the way Pine does. I can understand people that would prefer a low-powered editor like Pico versus something more sophisticated like Vi or Emacs because the former is just easier to use and configure, while the latter requires semi-programmers to be useful. -- Eugene Lee [EMAIL PROTECTED]
Re: color
On Fri, Oct 20, 2000 at 10:02:31AM -0700, Mike E wrote: System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] You'd better obtain more recent version of ncurses and recompile. I have version 4.2 while you have only 1.8.6. -- Eugene Paskevich | *==(--- | "Alrighty then!" [EMAIL PROTECTED]| ---)==* |-- Ace Venture Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey Fingerprint: 03 BE 52 C8 41 8C 10 DC 2F 81 A2 21 28 5E D3 12 ## A friend in need is a pest indeed. ##
Re: pgp-error...
On Tue, Oct 17, 2000 at 11:13:26PM +, Jan- Hendrik Palic wrote: I generated a new key and I I wanted to send me a test mail with a sign. In the send- menu of mutt, I hit p to use the pgp- feature in mutt and s to sign. When I hit y to send the mail, pgp wants me enter the passphrase, and I enter and then I got this errormessage: Can't open PGP subprocess!: No such file or directory (errno = 2) The passphrasse is correct, so, what is going wrong? Any suggestions? Yes, there is one: 1) find your PGP config file. 2) find the line of tmp directory there 3) set it to something where you have a right write 4) make sure that that directory exists That's all I guess. Good luck. -- Eugene Paskevich | *==(--- | "Alrighty then!" [EMAIL PROTECTED]| ---)==* |-- Ace Venture Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey Fingerprint: 03 BE 52 C8 41 8C 10 DC 2F 81 A2 21 28 5E D3 12 ## Two percent of zero is almost nothing. ##
Mutt on Mac OS X ?
Just wondering if anyone has gotten Mutt to work under the Mac OS X Public Beta. -- Eugene Lee [EMAIL PROTECTED]
Re: Incorrect encoding of letter's headings
On Tue, Sep 26, 2000 at 09:47:26PM +0400, Vitaly A. Repin wrote:
When I write the subject of my letter in russian (koi8-r encoding),
the following transformation occurs with letters of the "Subject" field:
Subject: =?koi8-r?B?9MXT1CDS1dPTy8/HzyDawcfPzM/Xy8E=?=
What's the problem? And how can I solve it?
As far a I remember this occures when the body of the message is in,
for example, in win-1251 and headers are in koi8-r.
If in the Content-Type header there is charset=win-1251 or something
like that then I'm right, if not then not right. :)
You've got to syncronize somehow charsets in headers and body.
--
Eugene Paskevich | *==(--- | "Alrighty then!"
[EMAIL PROTECTED]| ---)==* |-- Ace Venture
Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey
{Mutt 1.2.4i}Moderator of [EMAIL PROTECTED] Be afraid. ;)
##
I bought some used paint. It was in the shape of a house.
-- Steven Wright
##
About PGP public key service. (With P.S.)
I heard that people have troubles with public PGP key service.
That's why I'd like to introduce the way I did it myself.
I hope that this info will be helpful for someone.
--
1) In ~/.procmailrc:
:0
* ^Subject: publicpgpkey
| /home/eugene/bin/publicpgpkey "`formail -x 'From: '`"
2) /home/eugene/bin/publicpgpkey:
#!/bin/sh
KEYRING=/home/eugene/.pgp/pubring.pkr
PUBLIC=/tmp/publicpgpkey
USERID=Eugene
if [ "$1" == "--help" ] ; then
echo "Public PGP key utility."
echo "Usage: $0 [e-mail]"
echo "e-mail: To send public PGP key to a particular e-mail."
exit 0
fi
pgp -kxa $USERID $PUBLIC $KEYRING /dev/null 21
if [ ! -n "$1" ] ; then
cat $PUBLIC
rm -f $PUBLIC
exit 0
fi
mail "$1" -s "Public PGP key of Eugene Paskevich" $PUBLIC
if [ ! "`cat /proc/$PPID/cmdline`" == "-bash" ] ; then
echo `date ; echo "$1"` /home/eugene/.pgp/people
fi
rm -f $PUBLIC
-
Now one can make changes for him/herself and be happy.
P.S. There are two things I still can't understand.
1) Why do people post here signed messages. I think there's no need in it.
2) If they sign their messages they suppose that someone have their public
key to verify signature. Where can I get it? From public server of keys?
{I don't remember the correct name.} Again, there is no need in these
servers. 'couse noone would ask for public key of an unknown man just to
verify a signature.
It's a stupid idea as for me.
--
Eugene Paskevich | *==(--- | "Alrighty then!"
[EMAIL PROTECTED]| ---)==* |-- Ace Venture
Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey
{Mutt 1.2.4i}Moderator of [EMAIL PROTECTED] Be afraid. ;)
##
Eternal nothingness is fine if you happen to be dressed for it.
-- Woody Allen
##
Re: About PGP encryption
On Fri, Sep 22, 2000 at 08:54:44AM +, Suresh Ramasubramanian wrote:
... or use this little shell script -
#!/bin/sh
WHOAMI=`whoami`
if [ -f /tmp/sig.$USER ]
then
rm -f /tmp/sig.$USER
fi
cat $HOME/.signature /tmp/sig.$USER
/usr/games/fortune -s /tmp/sig.$USER
/usr/local/bin/mutt
That's very nice but I'd like my signature to be changed every time
I compose a new message. Not every session of mutt.
--
Eugene Paskevich | *==(--- |"Alrighty then!"
[EMAIL PROTECTED] | ---)==* | -- Ace Venture
Public PGP key:mailto:[EMAIL PROTECTED]?subject=publicpgpkey
{Mutt 1.2.4i} Moderator of [EMAIL PROTECTED] Be afraid. ;)
About PGP encryption
Hi!
I've got a problem out here with which, I hope, you can help me to cope.
Preface:
As you probably noticed I'm from Ukraine and we usually use Russian or
Ukrainian langs here. My output CP is set to Koi8-r. There is an option
in .muttrc called "charset-hook" for decoding messages on-the-fly.
The problem is:
If I recieve a normal text in charset which was hooked in .muttrc
everything decodes just fine. But in case of encrypted PGP message
which originally was in other CP than Koi8 then it just decrypts and
doesn't send it to decoder of CP's.
Possible solve:
To switch decrypting and decoding. First decrypt then decode the output of
decryption. Guess it should help.
Any other variants how to do this in other way?
P.S. How can I include cookies from fortune for example into my signature?
Answer directly please.
--
Eugene Paskevich | *==(--- |"Alrighty then!"
[EMAIL PROTECTED] | ---)==* | -- Ace Venture
Public PGP key:mailto:[EMAIL PROTECTED]?subject=publicpgpkey
{Mutt 1.2.4i} Moderator of [EMAIL PROTECTED] Be afraid. ;)
compilation warnings with mutt 1.2.5i and freebsd 4.0 release
I did a straight configure and make. The configure was pretty clean. The make generated some warnings, like: In file included from bindtextdom.c:48: gettextP.h:50: warning: ANSI does not permit the keyword `inline' In file included from localealias.c:74: gettextP.h:50: warning: ANSI does not permit the keyword `inline' localealias.c: In function `read_alias_file': localealias.c:259: warning: pointer targets in passing arg 1 of `fgets' differ in signedness localealias.c:265: warning: pointer targets in passing arg 1 of `strchr' differ in signedness localealias.c:318: warning: pointer targets in passing arg 1 of `strlen' differ in signedness localealias.c:319: warning: pointer targets in passing arg 1 of `strlen' differ in signedness explodename.c: In function `_nl_explode_name': explodename.c:113: warning: pointer targets in passing arg 1 of `_nl_normalize_codeset' differ in signedness And then when building the final binary: gcc -Wall -pedantic -g -O2 -o mutt 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 pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o resize.o -lncurses ./intl/libintl.a muttlib.o: In function `mutt_adv_mktemp': /private/home/eugene/src/mutt-1.2.5/muttlib.c(.text+0xb3): warning: mktemp() possibly used unsafely; consider using mkstemp() Here are the verbose descriptions: bash-2.03# ./mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 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: FreeBSD 4.0-RELEASE [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. Are these warnings anything I should be worried about? -- Eugene Lee [EMAIL PROTECTED]
Re: Color in telnet sessions to mutt
On Sat, Aug 26, 2000 at 01:54:29PM +0930, Brian Salter-Duke wrote: : : On the Mac I use Microphone to connect to my machine. This does not : support color. Does anyone have any suggestions how I can support color : when connecting from a Mac? Try NCSA Telnet or its successor, MacTelnet: http://home.austin.rr.com/telnet/ I think dataComet and BetterTelnet also support ANSI color sequences. -- Eugene Lee [EMAIL PROTECTED]
Re: conditionals
On Sat, Jul 22, 2000 at 10:58:18AM +0200, Thomas Roessler wrote: : On 2000-07-21 17:25:30 +0200, Johannes Zellner wrote: : : is it possible to have conditionals in ~/.muttrc ? : I want for example slightly different colors in : xterm than in linux console. : : I'm doing it this way: : : source ~/.mutt/colors.`if [ "$TERM" = "linux" ] ; then echo \ : linux ; else echo default ; fi` Can't you do something like: source ~/.mutt/$TERM and then just create a different muttrc file for each terminal? -- Eugene Lee [EMAIL PROTECTED]
a Mutt FAQ? (was Re: those users (was Re: Reply to all???))
On Sat, Jul 01, 2000 at 12:03:29PM +0400, Rino Mardo wrote: : On Fri, Jun 30, 2000 at 11:45:07AM -0400 or thereabouts, David T-G wrote: : : Not particularly; I just want to help out the faq project to get some : quick answers for folks and unclutter the list. : : Unclutter the list? Would a different mailing list addy help? IN : FreeBSD they have a freebsd-newbies and freebsd-hackers mailing list : which I think this list needs. mutt-newbies and mutt-hackers : : What you'd all think about it? Is there enough newbie traffic to warrant the creation of a separate mailing list? If there is, do so. If there isn't, address the real problem at hand. I think the problem is the same that other forums have, which is how one handles the same questions over and over again, without having to write the same answers over and over again. To that end, a FAQ makes more sense. Telling newbies to RTFM is like giving little school kids in English class a college level grammar reference, while pointing out a FAQ is like giving kids the teacher's edition of an English workbook --- because it comes with the answers! Once the kids understand the basics, or enough to solve their immediate problems, they can move onto the official references. I'm also interested in helping out with a Mutt FAQ project. So who's in charge of the beast? :) -- Eugene Lee [EMAIL PROTECTED]
default mbox for cc'd messages
When I am replying to messages, I'd like to have carbon copies stored in my current mailbox. I was hoping the following might work: set record=. Mutt does send the message, but it does not generate a carbon copy in the current mailbox. Is there a way to do this? Or do I just have to manually specify the current mailbox? -- Eugene Lee [EMAIL PROTECTED]
Re: default mbox for cc'd messages
On Fri, Jun 30, 2000 at 04:18:50PM +0530, Suresh Ramasubramanian wrote: : Eugene Lee proclaimed on mutt-users that: : : When I am replying to messages, I'd like to have carbon copies stored : in my current mailbox. I was hoping the following might work: : : set record=. : : Try : : set record="." Both variations failed. After browsing the docs a bit more, I'm curious if the current mailbox path is stored in a variable somewhere that could be expanded somehow. -- Eugene Lee [EMAIL PROTECTED]
Re: feature request: delayed delete
On Wed, Jun 28, 2000 at 02:06:02PM +0200, Marius Gedminas wrote: :On Wed, Jun 28, 2000 at 02:14:28AM -0700, Eugene Lee wrote: : : Besides tagging messages by absolute datetimes, this could be extended : to your specific problem by allowing relative datetime patterns. So you : could do things like tag messages that are 14 days old or older. : :So what's wrong with ~d and ~r? Nothing at all. I just need to RTFM more often. My bad. :) -- Eugene Lee [EMAIL PROTECTED]
Re: feature request: delayed delete
On Wed, Jun 28, 2000 at 12:20:29AM -0500, Carlos Puchol wrote: : :i have a mailbox with 3000 messages and the problem is that :i keep on leaving stuff there that i think i will need later, :but stays there for years. : :the idea is to delay-delete a message. the idea is to :mark a message for deletion, but not delete it for a while. :say i set my 'delay-delete' to 14 days. messages i would :delete today will actually get removed from my inbox the :first time i do an update on my inbox, at or after 14 days :from from today (i.e. from the time i deleted them). Actually, I'd like to have add some kind of search pattern to the message-tagging functions. For example, if I knew that I have a bunch of messages from Januaary and February 2000, I'd like to be to be able to tag them, then do with them as I will. AFAIK, this isn't a feature in Mutt. I know I could tag by searching all the "Date:" fields, but those dates aren't quite standard (the same datetime could come in different formats or in different timezones). Besides tagging messages by absolute datetimes, this could be extended to your specific problem by allowing relative datetime patterns. So you could do things like tag messages that are 14 days old or older. What does everyone else think? -- Eugene Lee [EMAIL PROTECTED]
Re: searching and collapsed threads
On Tue, Jun 27, 2000 at 03:41:05PM -0400, David T-G wrote: :...and then Jeremy Blosser said... :% David T-G [[EMAIL PROTECTED]] wrote: :% I have just discovered that searches do not look inside collapsed :% threads. [...] :% It's considered correct that Mutt treats messages hidden by thread :% collapsing the same way it treats ones hidden by a 'limit' -- as though :% they didn't exist. So if you limit messages, then search, you won't get :% results from messages not in the limit, and the same if you collapse :% threads. [...] :% It's debatable whether this should be -- it makes sense in some ways, since :% you could hurt yourself with a delete-pattern that affects collapsed :% threads when you didn't realize it would, but doesn't make sense in other :% ways, such as your current example. No one has suggested/implemented :% something better, though. : :I suppose a $search_within_collapsed or $match_within_collapsed variable :is in order ;-) I'm used to different behavior from other threaded reader applications on the Mac and PC side. Starting with an index of messages with some threads collapsed, if I do a search, and some of the search results are in messages belonging to collapsed threads, the application uncollapses only those threads to reveal the matched message(s). What do you think of this behavior? Good idea? Bad idea? -- Eugene Lee [EMAIL PROTECTED]
Re: Reply to all???
On Mon, Jun 26, 2000 at 07:07:47PM -0700, Gary Johnson wrote: :On Mon, Jun 26, 2000 at 06:23:04PM -0700, Jason Helfman wrote: : : How would I go about replying to all : :Use 'g': : :group-replyreply to all recipients Mutt's group-reply is not the same thing as "reply to all". Mutt implements the former by putting the sender's address into the "To:" header, then takes all other addresses and puts them into the "Cc:" header. Most other email clients that implements the latter do so by putting all addresses into the "To:" header. Mutt has no built-in function to do the latter. You can fake a "reply to all" function by doing a group-reply, then quit your editor, then hit 'E' to edit your message including headers, then manually move the "Cc:" addresses to the "To:" addresses. -- Eugene Lee [EMAIL PROTECTED]
typos in docs?
There are a few parts of the manual that list a "sort oder"? :) -- Eugene Lee [EMAIL PROTECTED]
Re: Re:
Threads are usually broken because someone's mailer doeesn't generate any useful trackable header like Message-ID, References, or In-Reply-To. I would rather get the person to use a better client, or smack her/his ISP to add this support to their mail system. As for threading by subject, it'd be nice to do what you suggested. But this is an open-source world where code speaks volumes. So writing and submitting a patch would be better. :) On Sat, Jun 17, 2000 at 07:33:16PM -0500, Andrew Eichmann wrote: : :When I thread mailing list messages, often the thread will be broken :up because of differing versions and placement of ``Re:'' in the :subject line, compounded by different mail clients' handling of :the subject line. For example, if the original message's Subject: :line is ``[BOB] What's the frequency, Kenneth?''where ``[BOB]'' is :the mailing list name that gets prepended to the subject, the replies :will :wind up like: : :``Re: [BOB] What's the frequency, Kenneth?'' :``re: [BOB] What's the frequency, Kenneth?'' :``Re: [BOB] re: What's the frequency, Kenneth?'' :``RE: [BOB] What's the frequency, Kenneth?'' :``Re: re: [BOB] What's the frequency, Kenneth?'' :usw. : :I searched on ``Re:'' and ``Subject:'' in the manual and didn't :find anything useful looking. : :Is there a built-in solution to this? Does anybody else have this :problem? I imagine something stripping out all variations of ``Re:'' :before the threads are arranged in the list. This would be child's :play in Perl, the world is not Perl. :-) : :Or should I start putting together a patch, right after I relearn C? -- Eugene Lee [EMAIL PROTECTED]
Re: muttrc.el
On Thu, Jun 15, 2000 at 11:54:47PM +0200, Thomas Roessler wrote: :On 2000-06-15 21:08:02 +0200, Marius Gedminas wrote: : : The Jargon File also mentions " " as the standard inclusion leader. : :Doesn't RFC 1036 have something on this? Nope. :Anyway, regardless of being RFC-documented or not, "" :_is_ the most widely accepted standard for tagging quoted :messages when replying. It is. But it's not an RFC standard. -- Eugene Lee [EMAIL PROTECTED]
request for reply-to-all function?
The feature that I've missed the most from other mailers is some kind of reply-to-all function that, given a email message, composes an normal reply to the sender's email address, but also takes all the email addresses in the "To:" header and adds them to the "To:" header of the reply. Group reply only composes a normal reply but instead puts all the "To:" email addresses into the "Cc" header. Should I forward this request to mutt-dev? -- Eugene Lee [EMAIL PROTECTED]
Re: How add to address for mailing list semi-automatically?
On Fri, May 12, 2000 at 07:59:09AM +0200, Frank Derichsweiler wrote: : :pressing L means: reply to the list. :I would like to start a new thread, i.e. create a mail with no :reference to old ones. This one should have the list address in the to :header field. Just use 'L'. Compose your message, quit your editor, then use 'E' to edit your message with full headers included, and delete any spurious "In-Reply-To:" header. -- Eugene Lee [EMAIL PROTECTED]
Re: Three question items
On Wed, May 10, 2000 at 11:15:12PM +0100, Thomas Ribbrock wrote: : :I found reformatting in vi (vim, to be precise) is very easy when you simply :mark all lines to be reformatted (visual mode) and then press 'gq'. Voilà - :nicely formatted paragraph with lines in ideal length. Unfortunately, it doesn't handle quoted text at all. I like the utility 'par', because it does so. So I can transform the above quote to this: :I found reformatting in vi (vim, to be precise) is very easy when you :simply mark all lines to be reformatted (visual mode) and then press :'gq'. Voilà - nicely formatted paragraph with lines in ideal length. by just piping the lines to an external filter, 'par -gqr 72'. :) -- Eugene Lee [EMAIL PROTECTED]
Re: Priority set to urgent possible?!
On Thu, May 11, 2000 at 06:49:33PM +0100, Lars Hecking wrote: :Mikko Hänninen [EMAIL PROTECTED] mentioned: : : And oh, there's no standard specifying the possible values for this : header. I've mostly seen "urgent" and "high" used, and of course : "bulk", "junk" and "list" for list emails. : : It is well documented in the SENDMAIL INSTALLATION AND OPERATION GUIDE. But there's no RFC for it, is there? -- Eugene Lee [EMAIL PROTECTED]
Re: quoting reply
On Thu, Mar 30, 2000 at 12:54:55PM -0600, Jason Helfman wrote: :I was hunting around for this last night, but where do can you specify :your character set for a "quoting reply" set indent_string=" " -- Eugene Lee [EMAIL PROTECTED]
Re: testing procmail
On Wed, Mar 15, 2000 at 05:32:50PM +, J McKitrick wrote: :I realize this is a mutt list, not a procmail list, :but this is just a quick question not worth subscribing to another :list for: : :Here's my test .procmailrc : :Problem is, nothing sent from me is ending up in chat. it all goes to :the default directory. To your .procmailrc, add this line to enable extended diagnostics: VERBOSE=on Then send another test email, and check your LOGFILE to see what Procmail is doing. The recipe looks fine, so I'm guessing that Procmail isn't even running. In which case you need to fix your $HOME/.forward file, if your local MTA (Sendmail, qmail, etc.) isn't configured to call Procmail automatically. -- Eugene Lee [EMAIL PROTECTED]
problem with ignore
I ran into a problem with the ignore/unignore commands. It appears that the patterns they accept cannot be regex patterns. This works: ignore * and this works: unignore subject: to: from: but this doesn't work: unignore ^(Subject|To|From): So do the ignore/unignore commands deal with shell globbing only? Would it be a good idea to make both commands use regex patterns? -- Eugene Lee [EMAIL PROTECTED]
Re: why is mutt better?
On Fri, Mar 10, 2000 at 02:20:27AM -0600, Jeremy Blosser wrote: :Eugene Lee [[EMAIL PROTECTED]] wrote: : : Having said this, I saw one feature in TheBat that I'd like to see Mutt : have someday: the ability to create and use templates for new messages, : replies, forwarded messages, etc. : :This should be possible now... : :1) create the templates you want, using your editor of choice :2) create macros that change the value of 'editor' to call a script/etc. :that processes the reply+template and calls your editor, then set 'editor' :back to the default, eg: : :macro index r :set editor=replyscriptenterreply:set editor=defaultenter : :With forms of this method the "template" isn't even limited to a text-based :construct, it can really be anything at all. In this aspect, Mutt is far more configurable because of its ability to call external programs to do things. However, it's not possible to insert information --- that Mutt already knows --- into a template without writing another email parser. For example, let's say I have a template for replying to messages from a particular mailing list. My template might look like this: Hullo, %%%FROM%%%! I have a comment about your message about "%%%SUBJECT%%%" on %%%DATE%%%. - begin original message - %%%BODY%%% - end original message - %%%SIGNATURE%%% As you can see, there is information about the email that I'd like to insert in place of the "%%%" strings. Mutt already knows what this stuff is. But there's no mechanism to pass this information onto an external script. Such a script has to figure this information out by itself by parsing the headers, checking for RFC compliancy, fixing special ISO-8859 characters, handling MIME attachments, etc. Maybe Mutt could pass this information along as environment variables to an external script to handle. Or maybe when Mutt creates a temp file, it can read in a template and substitute all the information first, before passing the temp file onto the user's editor. -- Eugene Lee [EMAIL PROTECTED]
Re: why is mutt better?
On Fri, Mar 10, 2000 at 12:04:42PM +0100, Thomas Roessler wrote: :On 2000-03-10 02:57:41 -0800, Eugene Lee wrote: : :set attribution="Hullo, %F!\n\nI have a comment about\ : your message about \"%s\" on %d.\n\n\ : - begin original message -" :set post_indent_string="- end original message " I was wrong saying that there wasn't a way in Mutt to pass this info onto an external script. I stand corrected. Excuse me while I RTFM. Yet again. :) But setting a separate set of attribute/post_indent_string values for each send-hook could get ugly with the escapes needed for extra quotes. -- Eugene Lee [EMAIL PROTECTED]
Re: [Announce] mutt-1.1.8 is out
On Mon, Mar 06, 2000 at 11:13:14AM +0100, Thomas Mueller wrote: : : :Mutt-1.1.8 is out. This is another BETA version. Changes : :against 1.1.7 include fixes for one recent and one : :long-standing, but mostly unnoticed bug. : : Just a quick observation. Mutt is one of the few pieces of software : that gets full version numbers for betas, versus most conventions that : use a next-version-number + "b" + beta-version-number. I just found : this practice to be a bit unusual. :) : :?? Linux Kernel, Gimp, ... they all use even numbers for stable releases :and odd numbers for development version. My history is based from BSD, Apache, BIND, Sendmail, etc. and never held any numerical favoritism. :-) I actually prefer a major.minor.fix versioning format. Besides, when releasing software that is still in beta testing, how do you count versions according to the Linux kernel way? For example, the previous Mutt beta was 1.1.7. Since the current release is still beta, shouldn't it be numbered as 1.1.9 ? Just curious, this is really new information to me. I feel so clueless... -- Eugene Lee [EMAIL PROTECTED]
Re: why is mutt better?
On Thu, Mar 09, 2000 at 06:39:45PM +, J McKitrick wrote: : :I just got in a debate over email clients, and my windows friend :argues anything i can do in mutt, he can do in TheBat! just as easily. :I checked the feature list, and it is extensive. Most of what mutt :offers, thebat offers. Why is the advantage of mutt, or any :text-based email client? - uses any editor you want (like any Unix mail client) - has extensive hook mechanism (although choice of actions isn't) - spawn subshells to do whatever - tags messages without moving them to another folder/mailbox Having said this, I saw one feature in TheBat that I'd like to see Mutt have someday: the ability to create and use templates for new messages, replies, forwarded messages, etc. -- Eugene Lee [EMAIL PROTECTED]
Re: signature send-hook problem
On Thu, Mar 09, 2000 at 05:25:36PM -0500, Jim Toth wrote: :On Thu, Mar 09, 2000 at 03:34:08PM -0500, Josh Kuperman ([EMAIL PROTECTED]) :said: : : The commented out line always gets matched and will force the : default signature. Is is simply changing the order? : :Yep, that's it. From the manual (section 3, Configuration): : : When multiple matches occur, commands are executed in the order : they are specified in the muttrc. I got bit by this too just a little while ago. I guess I'm used to the short circuit logic in C. -- Eugene Lee [EMAIL PROTECTED]
Re: Happy Little Vegemite
On Wed, Mar 01, 2000 at 11:09:22PM +1100, Chuck Dale wrote: : :RandomRant generality="waytoohigh" : :The problem (as I see it) is that .muttrc goes against the principles :which Mutt is following. Particularly in modularisation. The .muttrc :contains absolutely everything configurable in the program - it defines :the interface (keys, column presentation, folder hooks, colours), mail transfer :(sendmail settings, mailboxes which receive mail), personal settings :(real name, personal headers) and a few other random settings as well. : :/RandomRant : :One way to make things clearer would be to have sections like :[colors] :[keybindings] :[mailboxes] :[lists] :[folder_hooks] I don't know if this division of labor will work for all but the most simplest configurations. An example would be a complex set of folder hooks where colors, key bindings, save hooks, and other settings. Now imagine you had different sets of settings for different folders! -- Eugene Lee [EMAIL PROTECTED]
Re: changing tag deleting behavior
On Mon, Feb 28, 2000 at 03:03:19PM -0600, David DeSimone wrote: :Eugene Lee [EMAIL PROTECTED] wrote: : : I know I can do this by setting up a new key, but I'd rather invent no : new keystrokes if possible. Or should I just start practicing the : habit of tag-save to /dev/null? :) : :Is this really what you do? Waste time writing messages to /dev/null :(it isn't lightning-fast!), just to un-tag the messages? My favorite :way to untag all tagged messages is ";t", which means "apply the 'tag' :command to all tagged messages". It's quick and painless. :) I'm on a few dozen mailing lists. Even when parsed out with Procmail, I still end up with mailboxes with hundreds of messages each. Often I will tag lots of messages with certain subjects (usually when the thread has become a flame fest), then do a ";d". But I'd like that action to also untag the messages at the same time, which ";s" does. (Yes, I'm almost too lazy to do ";t" ;-) BTW, I noticed that if I try to ";s" to /dev/null, it fails! Mutt 1.0.1i (2000-01-18) Copyright (C) 1996-2000 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: FreeBSD 3.3-RELEASE [using ncurses 1.8.6/ache] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. fcntl: Invalid argument (errno = 22) Mutt 1.0.1i (2000-01-18) Copyright (C) 1996-2000 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: SunOS 4.1.4 [using slang 10202] Compile options: -DOMAIN +HOMESPOOL -USE_SETGID +USE_DOTLOCK -USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH=".mailbox/inbox" SHAREDIR="/u/u13/wcheung/lib/mutt" SYSCONFDIR="/u/u13/wcheung/etc" ISPELL="/depot/links/bin/ispell" _PGPPATH="/usr/local/nuglops/bin/pgp" _PGPV2PATH="/usr/local/nuglops/bin/pgp" To contact the developers, please mail to [EMAIL PROTECTED]. This flashes the message "Copying to /dev/null..." and does not generate an error message. However, the messages are not marked as deleted. -- Eugene Lee [EMAIL PROTECTED]
Re: applying filter to message being replied
On Thu, Feb 17, 2000 at 02:53:22PM +, [EMAIL PROTECTED] wrote: : :I sometimes need to preprocess a message I 'm about to reply :(eg. to reformat it so that long lines fit at a particular screen width) : :After reading the manual and performing a search in 'comp.mail.mutt', :I am still puzzled, whether and how it could be done. Don't send a mailer to do an editor's job! :) Some editors have a built-in function to wrap text. For example, Vim uses the key sequences 'gq'. If your editor lacks that function, you can always pipe the contents through a Unix filter such as 'par' that does the same job (it actually does a better job, IMHO). -- Eugene Lee [EMAIL PROTECTED]
Re: Changing X-Sender header
On Wed, Feb 09, 2000 at 01:17:50PM -0600, Kent R. Frazier wrote: :On Wed, Feb 09, 2000 at 05:05:30PM +, Lars Hecking wrote: : Claus Assmann writes: : On Wed, Feb 09, 2000, Lars Hecking wrote: : :The Sender: header is written by the MTA (eg. sendmail). : : sendmail does not generate a "Sender:" header. : Which MTA does it? : : Mutt doesn't, either. What does this leave? Mailing list software? Yes. Many do so to help identify messages being sent by some daemon. :Could this possibly be added by my ISP's smtp server? Probably yes, as well as any other header. -- Eugene Lee [EMAIL PROTECTED]
Re: save-hook
On Thu, Feb 10, 2000 at 01:15:01AM +0530, A.V. Jayanthan wrote: : : I subscribe to this mailing list. I receive mails from all :those who send mail to this mailing list. My question here is that, :what do I do in .muttrc so that when I press 's' to save a mail :received from this mailing list, it should automatically show =mutt, :the folder into which I save all these mails. Try this: save-hook '~e [EMAIL PROTECTED]' =mutt -- Eugene Lee [EMAIL PROTECTED]
