Re: Mac Command Line and mutt
On Mon, Sep 12, 2011 at 17:07, Leo Vegoda wrote: […] In my experience it works the same on whichever OS you choose as long as you build in all the bits and pieces you need. That’s my experience too. I use it on my Mac, and also on a Linux VPS (which I’m using now), and I haven’t had any issues with either. The .muttrc is the same for both, and it works without problems the way I have it set up (YMMV). For the latter issue, you might want to look at the different package management systems available for Mac OS, including Fink and MacPorts, to find out which versions they have available. I installed it on the Mac using Fink, and had no problems with it. If I recall correctly, the MacPorts copy was an older version. Mike -- __ __ __ / /_ ___ _/ /__ _/ / _ __ / '_/ _ \/ __/ _ `/ / _ `/ __/ _ \ |/ /Raconteur, Mostly /_/\_\\___/_/ \_,_/_/\_,_/\__/\___/___/ http://koralatov.com/
Color difference between 'mutt' and 'screen -t mutt'
Hello, all, I've set most colors in mutt to red on black (for night vision reasons), when I start mutt directly by $ mutt I get http://tx0.org/2qx but when I open it 'in a new tab' in screen via $ screen -t 'mutt' mutt I get the expected http://tx0.org/2qy What on Earth can be going on? Sincerely yours, John B. -- I guess I'm gonna fade into Bolivian. -Mike Tyson ___ http://jbaber.freeshell.org
Re: Mac Command Line and mutt
On Mon, Sep 12, 2011 at 02:56:08PM -0800, Tim Johnson wrote: Not so much a mutt question as a request for a reference. FYI: I have used mutt for years on linux. I am considering getting a mac mini. Some time ago, I queried this list about using mutt on a mac and from the responses, it appears that some of you do just that. What I am most interested in at this time is whether there are any MLs or forums that are designed around using the mac terminal. I just found http://www.mac-forums.com, looks like there is a forum for mac terminal. Any other recommendations? I have a related problem since moving from XP to Mac last May. I save email threads as MBOX files and reference them on the (local) home page of my browser, Firefox. The home page is my to-do list, and it contains references along the lines of: A HREF=file:///Users/tbaker/work/important-email-exchange.mbox Under XP, with some fiddling, I was able configure Firefox to launch a batch file, which launched a script, which launched mutt -f important-email-exchange.mbox. In other words, one mouse click in my to-do list in Firefox put me right into mutt, where I could read and directly respond to an email thread. I have been doing this for years. With the Mac, I have combed the forums, tried Automator and numerous shell script variations to try to get this to work. As I understand it, the problem is how to pass the HREF filename to an Apple application (*.app) that can launch a shell with mutt, taking the passed filename as an argument for mutt. If I could solve this problem, then presumably I could configure the Mac to open mutt when I click on a file such as important-email-exchange.mbox in the Mac Finder. I have tried everything I could think of, even looked into Emacs's Rmail, but I'm not sure I understand the system well enough to know where to look for the answer. Would one need to write an Apple script? Can anyone suggest an approach? Many thanks, Tom -- Tom Baker t...@tombaker.org
next-unread-mailbox and mbox
I use maildir for all my mailboxes, except the system mailbox in /var/spool/mail/user which receives mail from local processes such as cron, and which is in mbox format. Mutt seems to detect new mail in the system mbox fine (at least, the mailbox is marked as having new mail in the sidebar - I'm using the sidebar patch.) However, for this solitary mbox mailbox, the next-unread-mailbox command doesn't work. It works fine for all the other maildir mailboxes. I've tried both with and without the check_mbox_size option enabled, to no effect. I'm running Linux with /var on a separate filesystem, and /var is mounted with the relatime option (which, as I understand it, should mean that check_mbox_size is unnecessary). Does anyone have any idea why next-unread-mailbox doesn't work for this one particular mailbox, even though mutt does seem to be detecting new mail to it, and the command works for all other mailboxes? Thanks, Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
Repeating back addresses
If I use mutt to send an outgoing email message to an address, for example mutt j...@msn.com when I hit RETURN, mutt responds with: To: j...@msn.com I can then hit RETURN and get prompted for a Subject and continue on to enter the text and send the email. I'd like to not have mutt repeat back the email address I entered; I'd like to go immediately to the Subject: prompt. I looked through the options but I couldn't figure out if this behaviour is something I can change. Is there a way to tell mutt not to repeat back the email address I entered? Paul
Re: Mac Command Line and mutt
On Sep 13, 2011 at 10:06 AM -0400, Tom Baker wrote: If I could solve this problem, then presumably I could configure the Mac to open mutt when I click on a file such as important-email-exchange.mbox in the Mac Finder. I have tried everything I could think of, even looked into Emacs's Rmail, but I'm not sure I understand the system well enough to know where to look for the answer. Would one need to write an Apple script? Can anyone suggest an approach? There is probably some way to do with with apple script and/or iTerm. I'm sure you could do it with an applescript and Terminal/iTerm. Have the applescript receive the link, either by associating it with a custom URL scheme (instead of file:///path/to/box, maybe try x-mbox:///path/to/box) or by getting the selection as a file path or something. Then parse the input (URL or file path) for the mbox's file path. Then open up a Terminal/iTerm window and run the command mutt command with the mbox path as an argument. Alternately, you might be able to do it with no applescript if you use iTerm, since iTerm can be associated with specific URL schemes, like mailto:. Then in the profile command box, instead of having it start a login shell, you can enter a command with a placeholder for the URL, like so: /usr/local/bin/mutt $$URL$$ Thus, when I click on a mailto: link, iTerm handles it and runs mutt with the contents of the link. I think you could modify that somehow to run `mutt -f $$URL$$` as long as the URL was a file path. Of course, you wouldn't want to pollute the mailto URL scheme, so you'd have to pick another one. Looking at iTerm's preferences right now, the allowed choices are: https, ftp, gopher, mailto, news, nntp, telnet, wais, whois, x-man-page. No custom options. However, the iTerm developer is pretty responsive and might add in the capability to handle custom x-stuff schemes. Just some thoughts. There's probably a better way to do what you want...
Re: Mac Command Line and mutt
On Sep 12, 2011 at 04:39 PM -0800, Tim Johnson wrote: Ah! Package systems, that is valuable info. I'd definitely recommend homebrew over the others. A lot less messy and easier to install and manage in my mind. As far as installing mutt, even though I have a lot of stuff installed with homebrew, I find it more customizable to compile mutt by hand. I have a shell script that updates my hg repository of mutt, sets my configure options, and compiles it. Though homebrew does have 1.5.21 with tokyo-cabinet. It has the following selectable patches: sidebar, trash, slang, ignore-thread, and PGP verbose mime. Everything else should be more or less like what you have on Linux. If you use vim or emacs for composing, you are set for editors. If you wish to use one of the Mac text editors (which you most likely won't since you are coming from Linux), you can use a wrapper shell script to call them. I used BBEdit for composing mail with mutt for a couple years and had a script that wrapped my text for format flowed and did some other things. Now I use Vim. Check out MacVim if you are a vim user. You can use it from the terminal, but the gvim that comes with MacVim has been modified for OS X in some nice ways. I'd also recommend checking out iTerm. I never really liked it enough to move away from Terminal in the last 10 years until very recently. Terminal has gotten better, but the latest versions of iTerm are very nice. Especially if you use mutt - you can set up iTerm to handel mailto URLs pretty easily.
Re: Mac Command Line and mutt
Wow - this is great. Thanks! Options to work with :-) I installed iTerm, configured it for /sw/bin/mutt -f $$URL$$ and tried clicking on: A HREF=wais://Users/tbaker/mboxmbox - 2 slashes/A A HREF=wais:///Users/tbaker/mboxmbox - 3 slashes/A Firefox prompted me to choose a program, with iTerm as default, and when I chose it, Firefox launched an iTerm window, but nothing appeared in the window. I see this is going to take some more study, e.g., of apple script... Will report back if successful, but it may take a week or two before I can find the time. Many thanks, Tom On Tue, Sep 13, 2011 at 11:01:39AM -0400, Tim Gray wrote: On Sep 13, 2011 at 10:06 AM -0400, Tom Baker wrote: If I could solve this problem, then presumably I could configure the Mac to open mutt when I click on a file such as important-email-exchange.mbox in the Mac Finder. I have tried everything I could think of, even looked into Emacs's Rmail, but I'm not sure I understand the system well enough to know where to look for the answer. Would one need to write an Apple script? Can anyone suggest an approach? There is probably some way to do with with apple script and/or iTerm. I'm sure you could do it with an applescript and Terminal/iTerm. Have the applescript receive the link, either by associating it with a custom URL scheme (instead of file:///path/to/box, maybe try x-mbox:///path/to/box) or by getting the selection as a file path or something. Then parse the input (URL or file path) for the mbox's file path. Then open up a Terminal/iTerm window and run the command mutt command with the mbox path as an argument. Alternately, you might be able to do it with no applescript if you use iTerm, since iTerm can be associated with specific URL schemes, like mailto:. Then in the profile command box, instead of having it start a login shell, you can enter a command with a placeholder for the URL, like so: /usr/local/bin/mutt $$URL$$ Thus, when I click on a mailto: link, iTerm handles it and runs mutt with the contents of the link. I think you could modify that somehow to run `mutt -f $$URL$$` as long as the URL was a file path. Of course, you wouldn't want to pollute the mailto URL scheme, so you'd have to pick another one. Looking at iTerm's preferences right now, the allowed choices are: https, ftp, gopher, mailto, news, nntp, telnet, wais, whois, x-man-page. No custom options. However, the iTerm developer is pretty responsive and might add in the capability to handle custom x-stuff schemes. Just some thoughts. There's probably a better way to do what you want... -- Tom Baker t...@tombaker.org
