Re: Running mutt on Mac OS X
On 02Jan2009 13:35, Kyle Wheeler kyle-m...@memoryhole.net wrote: | On Friday, January 2 at 02:22 PM, quoth Trey Sizemore: | Well, OSX is built on FreeBSD, so it's going to be similar to that. | What sort of tweaking did you have to do? Certainly paths to | external programs are going to be somewhat different, so that's to | be expected... | | Yeah, it was mostly paths to programs, I believe. | | shrug That's why I typically try to avoid using full paths to | programs, and instead use my ~/.bashrc to carefully craft my $PATH | variable. Another thing I've found helpful is to make a ~/bin-local which contains symlinks to specific versions of a few programs. Having ~/bin-local near the front of $PATH can give you per-program tuning of what you run. (For me, it's bin-local because ~/bin is an exact copy of ~/bin from my main machine, wherever I work. So the per-machine custom stuff goes in ~/bin-local.) Cheers, -- Cameron Simpson c...@zip.com.au DoD#743 http://www.cskk.ezoshosting.com/cs/ This signature was originally recorded on analog equipment. While we have attempted to preserve the meaning of the original, the high resolution of this media may reveal limitations of the source. - paul-michael agapow aga...@latcs1.oz.au
Running mutt on Mac OS X
I'm contemplating getting a MacBook Pro laptop. As a long-time Linux user, I'm concerned about getting mutt running the way that I've got it setup on my Linux machines. For those running mutt on Mac OS X, how easy/hard was it to get your .muttrc 'adapted' to run? Does urlview work as expected, are you using vim for the editor and did you get your vim configurations ported over ok? Thanks for any feedback. -- Cheers, Trey Thieves respect property; they merely wish the property to become their property that they may more perfectly respect it. --G.K. Chesterton, The Man Who Was Thursday Linux lizard 2.6.27.7-9-pae i686 GNU/Linux 12:11pm up 13:08, 5 users, load average: 0.02, 0.09, 0.10
Re: Running mutt on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 12:13 PM, quoth Trey Sizemore: I'm contemplating getting a MacBook Pro laptop. As a long-time Linux user, I'm concerned about getting mutt running the way that I've got it setup on my Linux machines. For what it's worth, I share my muttrc (and related files) between all of my machines, which includes both Linux and Mac boxes, without any trouble. For those running mutt on Mac OS X, how easy/hard was it to get your .muttrc 'adapted' to run? I didn't have to do anything to the muttrc. The only thing that needed some extra entries was, obviously, the ~/.mailcap file and the ~/.urlview file. I say obviously because the commands needed to open various file types are different on OS X. For example, to open a URL in your web browser, you can just use the `open` command. But that's got nothing to do with your muttrc. Here's how I've set my mailcap up - there are simpler ways of doing it, but I add all the test segments so that the correct command is chosen by mutt. # this uses xv only if there's an X server, and only if I have xv image/*; xv %s; test=test -n $DISPLAY type xv /dev/null # this uses open only on OSX and only if I'm not using ssh image/*; open %s; copiousoutput; test=test `uname -s` = Darwin -a -z $SSH_CLIENT Though I recently discovered there's a cooler way to view images on OSX: image/*; qlmanage -p %s 2/dev/null; test type qlmanage -a -z $SSH_CLIENT Does urlview work as expected, Yes, generally (you have to configure it), but I prefer extract_url.pl, because it's better at handling unusual and more modern email encodings that allow URLs to be broken into multiple lines. are you using vim for the editor and did you get your vim configurations ported over ok? ...ported? I use the same vimrc for all of my machines as well. Seriously, I think you're building this up in your mind as some kind of gargantuan task, and it's really quite simple. As long as you don't rely on /usr/bin/sendmail (which is usually asking for trouble *anyway*), and as long as you know the right commands for all your viewers (on OSX, the right command is almost always `open`), you'll be just fine. The only way you could possibly have much trouble is if you have a lot of extremely machine-specific stuff in your muttrc. ~Kyle - -- If man was meant to be nude, he would have been born that way. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkleUX8ACgkQBkIOoMqOI14BgACg6GpqnfdOvgi4M2TgJkddcKpo VUwAoPNj/zcz18lB9+69UF+XLcNOcp8L =IcoI -END PGP SIGNATURE-
Re: Running mutt on Mac OS X
On Fri, 2 Jan 2009 11:40:15 -0600, Kyle Wheeler kyle-m...@memoryhole.net said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 12:13 PM, quoth Trey Sizemore: I'm contemplating getting a MacBook Pro laptop. As a long-time Linux user, I'm concerned about getting mutt running the way that I've got it setup on my Linux machines. For what it's worth, I share my muttrc (and related files) between all of my machines, which includes both Linux and Mac boxes, without any trouble. For those running mutt on Mac OS X, how easy/hard was it to get your .muttrc 'adapted' to run? I didn't have to do anything to the muttrc. The only thing that needed some extra entries was, obviously, the ~/.mailcap file and the ~/.urlview file. I say obviously because the commands needed to open various file types are different on OS X. For example, to open a URL in your web browser, you can just use the `open` command. But that's got nothing to do with your muttrc. Here's how I've set my mailcap up - there are simpler ways of doing it, but I add all the test segments so that the correct command is chosen by mutt. # this uses xv only if there's an X server, and only if I have xv image/*; xv %s; test=test -n $DISPLAY type xv /dev/null # this uses open only on OSX and only if I'm not using ssh image/*; open %s; copiousoutput; test=test `uname -s` = Darwin -a -z $SSH_CLIENT Though I recently discovered there's a cooler way to view images on OSX: image/*; qlmanage -p %s 2/dev/null; test type qlmanage -a -z $SSH_CLIENT Does urlview work as expected, Yes, generally (you have to configure it), but I prefer extract_url.pl, because it's better at handling unusual and more modern email encodings that allow URLs to be broken into multiple lines. are you using vim for the editor and did you get your vim configurations ported over ok? ...ported? I use the same vimrc for all of my machines as well. Seriously, I think you're building this up in your mind as some kind of gargantuan task, and it's really quite simple. As long as you don't rely on /usr/bin/sendmail (which is usually asking for trouble *anyway*), and as long as you know the right commands for all your viewers (on OSX, the right command is almost always `open`), you'll be just fine. The only way you could possibly have much trouble is if you have a lot of extremely machine-specific stuff in your muttrc. ~Kyle Thanks Kyle. Hopefully it *is* just a case of building this up to be more than it is. ;-) I remember having to do a lot of 'tweaking' a while back when I was trying to get things setup on a FreeBSD install, so I assumed (perhaps wrongly) that the situation might be similar with OS X. By chance, are you using the default Mac terminal program, iTerm, or something else entirely for the terminal? Thanks! -- Trey Sizemore t...@fastmail.fm
Re: Running mutt on Mac OS X
On 01/02/09, Trey Sizemore wrote: On Fri, 2 Jan 2009 11:40:15 -0600, Kyle Wheeler snipped... By chance, are you using the default Mac terminal program, iTerm, or something else entirely for the terminal? Having just add a macbook, I find it very interesting getting things to work on a macbook versus normal linux. I ended up using the iTerm because the screen seems to work better. Maybe someone can tell me what was wrong with the terminal app, but it would leave text all over the screen. Parts of previous emails would display etc as you moved around. It was very confusing. The power management, and other bits on the macbook are great. The Home/End key is another issue that iTerm seemed fixed able. I could never get it right in Terminal app. -- respectfully, Joseph
Re: Running mutt on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 01:08 PM, quoth Trey Sizemore: I remember having to do a lot of 'tweaking' a while back when I was trying to get things setup on a FreeBSD install, so I assumed (perhaps wrongly) that the situation might be similar with OS X. Well, OSX is built on FreeBSD, so it's going to be similar to that. What sort of tweaking did you have to do? Certainly paths to external programs are going to be somewhat different, so that's to be expected... By chance, are you using the default Mac terminal program, iTerm, or something else entirely for the terminal? I used to use xterm, but these days I use the default Terminal.app. But that's a battle in and of itself. (more in a moment) ~Kyle - -- Suppose ye that I am come to give peace on earth? I tell you, Nay; but rather division: For henceforth there shall be five in one house divided, three against two, and two against three. The father shall be divided against the son, and the son against the father; the mother against the daughter, and the daughter against the mother; the mother in law against her daughter in law, and the daughter in law against her mother in law. -- Prince of Peace, Jesus Christ (Luke 12:51-53) -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkleW/UACgkQBkIOoMqOI151oACgwyjjZ5y2bAgPFVPXlcms+2s1 CB4AmwevLvnVrTVqOW27am7UdZ+RZGXD =yPOG -END PGP SIGNATURE-
Re: Running mutt on Mac OS X
I'm a long time Linux user (RedHad, Slackware), and last year when the new iMac with OSX 10.5 came out, I couldn't resist -- but with a lot of trepidation. My worries were completely unfounded. True, some things work differently than what you may be used to. You'll have to find those yourself. The following goes beyond your question, but maybe you'll find it useful. In my case, after doing a lot of googling, I immediately installed both Fink and MacPorts in order to get some things I was used to. Turned out to be unnecessary (at least for me), and eventually, I got rid of them both, completely. The console things I wanted that weren't included, I compiled using the built in tools with no problem. The GUI things I wanted, I was able to find Mac versions of. Except Ghostscript. Haven't found a postscript reader (free) for OS X. But I just got used to the builtin ps to pdf converter. I had trouble finding a decent (free) newsreader, but finally settled on OSXnews 2.081. It has some issues, but generally works pretty well (http://OSXnews.sf.net). I would advise holding off on Fink and MacPorts unless you find they are absolutely necessary. Another thing -- I thought I'd be using the built-in X-windows a lot. Eventually decided it was a pain in the neck (although it works pretty well, except for not using some of the native mac capabilities and look -- and cluttering up the toolbar). The things I really wanted a gui for were available in a mac-cocoa or carbon version. Things to get: First thing: get MacVim. Uses the core vim but with a Mac cocoa gui wrapper. It's great. http://code.google.com/p/macvim/. I'm using MacVim to write this email as the editor used by Mutt. I compiled mutt from source with no problem. Another thing you might want to look into: NeoOffice as the OpenOffice version for OS X, (I don't have the url handy, but it's easy to find). There are a lot of choices for a web browser (and for text only browsers to use with mutt.) I used Firefox for quite a while, and while I like it's plugins, it started starting an X which it seemed to not be using, and I had to terminate by hand. Strange. I submitted a bug report, but got no response. I finally switched over to Camino (http://caminobrowser.org/). And the final thing I'll mention: The XCode IDE, the Cocoa platform for programming Mac applications, and Objective-C, the language used by Cocoa. But that's another story. Best, John Velman On Fri, Jan 02, 2009 at 01:08:39PM -0500, Trey Sizemore wrote: On Fri, 2 Jan 2009 11:40:15 -0600, Kyle Wheeler kyle-m...@memoryhole.net said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 12:13 PM, quoth Trey Sizemore: I'm contemplating getting a MacBook Pro laptop. As a long-time Linux user, I'm concerned about getting mutt running the way that I've got it setup on my Linux machines. For what it's worth, I share my muttrc (and related files) between all of my machines, which includes both Linux and Mac boxes, without any trouble. For those running mutt on Mac OS X, how easy/hard was it to get your .muttrc 'adapted' to run? I didn't have to do anything to the muttrc. The only thing that needed some extra entries was, obviously, the ~/.mailcap file and the ~/.urlview file. I say obviously because the commands needed to open various file types are different on OS X. For example, to open a URL in your web browser, you can just use the `open` command. But that's got nothing to do with your muttrc. Here's how I've set my mailcap up - there are simpler ways of doing it, but I add all the test segments so that the correct command is chosen by mutt. # this uses xv only if there's an X server, and only if I have xv image/*; xv %s; test=test -n $DISPLAY type xv /dev/null # this uses open only on OSX and only if I'm not using ssh image/*; open %s; copiousoutput; test=test `uname -s` = Darwin -a -z $SSH_CLIENT Though I recently discovered there's a cooler way to view images on OSX: image/*; qlmanage -p %s 2/dev/null; test type qlmanage -a -z $SSH_CLIENT Does urlview work as expected, Yes, generally (you have to configure it), but I prefer extract_url.pl, because it's better at handling unusual and more modern email encodings that allow URLs to be broken into multiple lines. are you using vim for the editor and did you get your vim configurations ported over ok? ...ported? I use the same vimrc for all of my machines as well. Seriously, I think you're building this up in your mind as some kind of gargantuan task, and it's really quite simple. As long as you don't rely on /usr/bin/sendmail (which is usually asking for trouble *anyway*), and as long as you know the right commands for all your viewers (on OSX, the right command is almost always `open`), you'll be just fine. The only way you could possibly have
Re: Running mutt on Mac OS X
On Fri, Jan 02, 2009 at 12:24:53PM -0600, Kyle Wheeler wrote: [snip] I used to use xterm, but these days I use the default Terminal.app. But that's a battle in and of itself. (more in a moment) I don't have any trouble with Terminal.app. What am I doing wrong? :-) John Velman ~Kyle -- Suppose ye that I am come to give peace on earth? I tell you, Nay; but rather division: For henceforth there shall be five in one house divided, three against two, and two against three. The father shall be divided against the son, and the son against the father; the mother against the daughter, and the daughter against the mother; the mother in law against her daughter in law, and the daughter in law against her mother in law. -- Prince of Peace, Jesus Christ (Luke 12:51-53)
Re: Running mutt on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 01:17 PM, quoth Joseph: I ended up using the iTerm because the screen seems to work better. Ugh, seriously? I tried using iTerm but just found it to be way too slow and finicky. My alternative to Apple's Terminal would be xterm (because it works *exactly* the same as it does on every other Unix, and it's blazing fast). Maybe someone can tell me what was wrong with the terminal app, but it would leave text all over the screen. Parts of previous emails would display etc as you moved around. It was very confusing. There's nothing wrong with the *Terminal.app* program, per se, but there's plenty wrong with your TERM setting. Terminal.app is NOT an xterm, it is NOT an xterm-color, it is NOT an rxvt terminal, it is NOT a dtterm terminal, even though it gives you all those options (and more) in the Advanced tab of the terminal preferences. Most of those options are close-enough that it works for MOST things, but mutt, more than any other program I've ever played with, uses every single ounce of a terminal's capabilities, and so is much more sensitive to slightly-incorrect TERM settings. The correct value for the TERM environment variable, for Apple's Terminal.app program, is nsterm (from NeXTStep Terminal, which is where the Terminal.app's ancestry lies). Now, depending on your termcap database, even that is probably slightly incorrect. For one thing, you probably won't get all the right colors. Personally, the most accurate value I've found is nsterm-16color. But you'll run into additional trouble with that. Get this: the nsterm-16color termcap file that comes with OSX (and that came with ncurses up until very recently) has a bug in it. Not a big one, but some of the commands in it are wrong. This is in the mutt archives - I describe how to modify nsterm-16color so that the Apple Terminal works perfectly: http://marc.info/?l=mutt-usersm=118897291908291w=2 The Home/End key is another issue that iTerm seemed fixed able. I could never get it right in Terminal app. That's easy to fix as well. In Terminal.app, open up the Preferences (under the Terminal menu, or press command-comma). Click on the Settings icon on the top of the window that shows up. Pick your favorite terminal style in the column on the left, and click on the Keyboard tab on the right. In that list you can scroll to find all the keys you want to modify (end, home, etc.). For each one, select it and edit it to change what it does. By default, they're set to affect the scroll bar. If you'd rather they emitted a character sequence (i.e. the way they do on Linux), just tell it what character sequence to use. Here are the correct ones: end: \033[F home: \033[H page down: \033[6~ page up: \033[5~ The \033 part is generated by pressing the escape key when typing in a character sequence. ~Kyle - -- Faith... must be enforced by reason. [...] When faith becomes blind it dies. -- Ghandi -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkleYmwACgkQBkIOoMqOI15cxwCcDFDpy/YMTzi9ah7UnQy6E52e nm0AoOdSUclxou9EJ5I+23H03/yQ0bI3 =vOgX -END PGP SIGNATURE-
Re: Running mutt on Mac OS X
On Fri, 2 Jan 2009 12:24:53 -0600, Kyle Wheeler kyle-m...@memoryhole.net said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 01:08 PM, quoth Trey Sizemore: I remember having to do a lot of 'tweaking' a while back when I was trying to get things setup on a FreeBSD install, so I assumed (perhaps wrongly) that the situation might be similar with OS X. Well, OSX is built on FreeBSD, so it's going to be similar to that. What sort of tweaking did you have to do? Certainly paths to external programs are going to be somewhat different, so that's to be expected... Yeah, it was mostly paths to programs, I believe. Also, there may have been different versions of programs that didn't support some features. By chance, are you using the default Mac terminal program, iTerm, or something else entirely for the terminal? I used to use xterm, but these days I use the default Terminal.app. But that's a battle in and of itself. (more in a moment) ~Kyle -- Trey Sizemore t...@fastmail.fm
Re: Running mutt on Mac OS X
On Fri, 2 Jan 2009 10:41:00 -0800, John Velman vel...@cox.net said: I'm a long time Linux user (RedHad, Slackware), and last year when the new iMac with OSX 10.5 came out, I couldn't resist -- but with a lot of trepidation. My worries were completely unfounded. True, some things work differently than what you may be used to. You'll have to find those yourself. The following goes beyond your question, but maybe you'll find it useful. In my case, after doing a lot of googling, I immediately installed both Fink and MacPorts in order to get some things I was used to. Turned out to be unnecessary (at least for me), and eventually, I got rid of them both, completely. The console things I wanted that weren't included, I compiled using the built in tools with no problem. The GUI things I wanted, I was able to find Mac versions of. Except Ghostscript. Haven't found a postscript reader (free) for OS X. But I just got used to the builtin ps to pdf converter. I had trouble finding a decent (free) newsreader, but finally settled on OSXnews 2.081. It has some issues, but generally works pretty well (http://OSXnews.sf.net). I would advise holding off on Fink and MacPorts unless you find they are absolutely necessary. Another thing -- I thought I'd be using the built-in X-windows a lot. Eventually decided it was a pain in the neck (although it works pretty well, except for not using some of the native mac capabilities and look -- and cluttering up the toolbar). The things I really wanted a gui for were available in a mac-cocoa or carbon version. Things to get: First thing: get MacVim. Uses the core vim but with a Mac cocoa gui wrapper. It's great. http://code.google.com/p/macvim/. I'm using MacVim to write this email as the editor used by Mutt. I compiled mutt from source with no problem. Another thing you might want to look into: NeoOffice as the OpenOffice version for OS X, (I don't have the url handy, but it's easy to find). There are a lot of choices for a web browser (and for text only browsers to use with mutt.) I used Firefox for quite a while, and while I like it's plugins, it started starting an X which it seemed to not be using, and I had to terminate by hand. Strange. I submitted a bug report, but got no response. I finally switched over to Camino (http://caminobrowser.org/). And the final thing I'll mention: The XCode IDE, the Cocoa platform for programming Mac applications, and Objective-C, the language used by Cocoa. But that's another story. Best, John Velman Thanks John. That was some great info. I have a lot of the same questions around things you've already been through. I'll give MacVim a try. Plus it looks like there's a way to access the Mac addressbook so that I don't need to use abook anymore. Much appreciated info. -- Trey Sizemore t...@fastmail.fm
Re: Running mutt on Mac OS X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, January 2 at 02:22 PM, quoth Trey Sizemore: Well, OSX is built on FreeBSD, so it's going to be similar to that. What sort of tweaking did you have to do? Certainly paths to external programs are going to be somewhat different, so that's to be expected... Yeah, it was mostly paths to programs, I believe. shrug That's why I typically try to avoid using full paths to programs, and instead use my ~/.bashrc to carefully craft my $PATH variable. Also, there may have been different versions of programs that didn't support some features. Yeah... again, I handle most of that kind of thing in my ~/.bashrc, rather than in my muttrc or vimrc. If it helps: http://www.memoryhole.net/~kyle/bashrc.html ~Kyle - -- The most wasted of all days is one without laughter. -- e e cummings -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAklebJEACgkQBkIOoMqOI150MgCg9iDXU1rNGlDAdTxiMPBuPrMN 05wAnjqcT+rLn1nJJlS712IJcIZ888GR =mVMZ -END PGP SIGNATURE-
Re: Running mutt on Mac OS X
On Fri Jan 02, 2009 01:35PM, Kyle Wheeler wrote: On Friday, January 2 at 02:22 PM, quoth Trey Sizemore: Well, OSX is built on FreeBSD, so it's going to be similar to that. What sort of tweaking did you have to do? Certainly paths to external programs are going to be somewhat different, so that's to be expected... Yeah, it was mostly paths to programs, I believe. shrug That's why I typically try to avoid using full paths to programs, and instead use my ~/.bashrc to carefully craft my $PATH variable. Also, there may have been different versions of programs that didn't support some features. Yeah... again, I handle most of that kind of thing in my ~/.bashrc, rather than in my muttrc or vimrc. If it helps: http://www.memoryhole.net/~kyle/bashrc.html ~Kyle Thanks Kyle. -- Cheers, Trey Adversity is the trial of principle. Without it, a man hardly knows whether he is honest or not. --Henry Fielding Linux lizard 2.6.27.7-9-pae i686 GNU/Linux 2:47pm up 15:44, 5 users, load average: 0.32, 0.57, 0.40
Mutt on Mac OS X?
On Thu, 21 Feb 2002, Ken Weingold wrote: I have happily used (and still use) Pine under Unix. Since I work with project partners that use MS-Office and other WIN2000 programs, however, I now have to move primarily to a Windows environment. I work alot from home or on the road, live out of range of high-speed Internet, and so need to work offline in store-and-forward mode. Ten years ago I had MKS UUCP with Mailx under DOS 3.3, and this actually worked reasonably well. I am lost without vi/vim. Not what you want to hear, but any chance you could use a Mac? With OS X, you'd be set. And Office v.X is supposed to be great. Some very satisfied colleagues have confirmed this. Looking into it further, I find precompiled ports of vim, pine, lynx, ncftp, and (in theory) procmail -- only in theory, because its ftp directory is empty -- under http://www.osxgnu.org/software/index.html. But no mutt! Does anyone here know more? Tom -- Dr. Thomas Baker[EMAIL PROTECTED] Birlinghoven Library, Fraunhofer-Gesellschaft mobile +49-171-408-5784 Institutszentrum Schloss Birlinghovenwork +49-30-8109-9027 53754 Sankt Augustin, Germany fax +49-2241-14-2619
Re: Mutt on Mac OS X?
On Mon, Mar 11, 2002 at 11:15:28AM +0100, Thomas Baker wrote: On Thu, 21 Feb 2002, Ken Weingold wrote: Ten years ago I had MKS UUCP with Mailx under DOS 3.3, and this actually worked reasonably well. I am lost without vi/vim. Not what you want to hear, but any chance you could use a Mac? With OS X, you'd be set. And Office v.X is supposed to be great. Some very satisfied colleagues have confirmed this. Looking into it further, I find precompiled ports of vim, pine, lynx, ncftp, and (in theory) procmail -- only in theory, because its ftp directory is empty -- under http://www.osxgnu.org/software/index.html. But no mutt! Does anyone here know more? Mac OS X folks like myself are fortunate to have Fink (http://fink.sourceforge.net) -- which is a port of the Debian package management tools. I've installed precompiled ports of the apps you listed as well as mutt (oh and procmail /does/ work - it's preinsatlled) and haven't had any problems that weren't directly caused by my newbieness. -- Ryan Singer :: http://feltpresence.com The reason conservatives cohere and radicals fight: everyone agrees about fears, no one about visons.
Re: Mutt on Mac OS X?
I have been using Mutt on OS X. I installed it with Fink package manager. If you use the sendmail that comes with OS X, then procmail is the local mail delivery agent by default. It is already precompiled into it. With any luck you'll see that this is being sent out from a Darwin machine in the headers. So far my only problems with Mutt on Mac OS X have been: (1) Misreading the documentation and failing to add source ~/.mailaliases to the end of my .muttrc to source my aliases files. (2) The failure of the package to automatically compile the urlview binary, thus depriving me of the ability to hit ctrl-B and get a list of urls from a mail message. (3) No idea what I need to do to get the F1..F12 keys working on an iMac Keyboard. On Mon, Mar 11, 2002 at 11:15:28AM +0100, Thomas Baker wrote: On Thu, 21 Feb 2002, Ken Weingold wrote: I have happily used (and still use) Pine under Unix. Since I work with project partners that use MS-Office and other WIN2000 programs, however, I now have to move primarily to a Windows environment. I work alot from home or on the road, live out of range of high-speed Internet, and so need to work offline in store-and-forward mode. Ten years ago I had MKS UUCP with Mailx under DOS 3.3, and this actually worked reasonably well. I am lost without vi/vim. Not what you want to hear, but any chance you could use a Mac? With OS X, you'd be set. And Office v.X is supposed to be great. Some very satisfied colleagues have confirmed this. Looking into it further, I find precompiled ports of vim, pine, lynx, ncftp, and (in theory) procmail -- only in theory, because its ftp directory is empty -- under http://www.osxgnu.org/software/index.html. But no mutt! Does anyone here know more? Tom -- Dr. Thomas Baker[EMAIL PROTECTED] Birlinghoven Library, Fraunhofer-Gesellschaft mobile +49-171-408-5784 Institutszentrum Schloss Birlinghovenwork +49-30-8109-9027 53754 Sankt Augustin, Germany fax +49-2241-14-2619 -- Josh Kuperman [EMAIL PROTECTED]
Re: Mutt on Mac OS X?
On Mon, Mar 11, 2002, Thomas Baker wrote: Looking into it further, I find precompiled ports of vim, pine, lynx, ncftp, and (in theory) procmail -- only in theory, because its ftp directory is empty -- under http://www.osxgnu.org/software/index.html. But no mutt! Does anyone here know more? Why not just build your own versions of what you want? Go to the Apple web site and download the developer kit. It's a huge file, and includes, amongst other stuff, gcc (called 'cc'). I have built vim, ncftp, and lots of other stuff from source. -Ken
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: compiling Mutt on Mac OS X
At 16:09 -0800 22 Feb 2001, Eugene Lee [EMAIL PROTECTED] wrote: I'm trying to compile Mutt 1.2.5i on Mac OS X and I'm getting a bunch of warnings in the compilation: I'm not so worried about the overlapping function names, but I'm a bit I didn't see any of those in the messages you included. concerned with messasges like "ANSI C does not support `long long'". Those were all in system include files, so there's nothing the mutt developers can do about them. But it's not really anything to worry about. GCC supports "long long" even though it's not part of the ANSI C standard. The warning is there only as a reminder that it isn't portable. Portability isn't really a concern for system includes, where any language extensions used basically become required features for compilers on that system. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Vir: Ahh, he has become one with his inner self. Garibaldi: He's passed out. Vir: That too.
Re: Mutt on Mac OS X ?
On Tue, Oct 17, 2000 at 08:58:39AM -0400, Thomas E. Dickey wrote: On Tue, 17 Oct 2000, John Wright wrote: On Thu, Oct 12, 2000 at 02:14:36PM -0700, Eugene Lee wrote: Just wondering if anyone has gotten Mutt to work under the Mac OS X Public Beta. 1.2.4i didn't compile because it couldn't find things like A_NORMAL. I did find a curses library in some odd place, I might try again with slang or something like that. I'm told that ncurses (post-5.1) builds/works on OS X. No matter what you use you'll have trouble with the config.guess and config.sub scripts, since those cases were only added this year. Ah, post-5.1. yes the latest one didn't get past running the c++ compiler. slang compiled but as soon as I was asked a question but mutt you could see there was a program -- my reply wasn't noticed. I'll keep trying.
Re: Mutt on Mac OS X ?
On Fri, Oct 27, 2000 at 09:44:46AM +0100, John Wright wrote: On Tue, Oct 17, 2000 at 08:58:39AM -0400, Thomas E. Dickey wrote: On Tue, 17 Oct 2000, John Wright wrote: On Thu, Oct 12, 2000 at 02:14:36PM -0700, Eugene Lee wrote: Just wondering if anyone has gotten Mutt to work under the Mac OS X Public Beta. 1.2.4i didn't compile because it couldn't find things like A_NORMAL. I did find a curses library in some odd place, I might try again with slang or something like that. I'm told that ncurses (post-5.1) builds/works on OS X. No matter what you use you'll have trouble with the config.guess and config.sub scripts, since those cases were only added this year. Ah, post-5.1. yes the latest one didn't get past running the c++ compiler. what was the error message? (most of the g++ problems currently are due to things like missing or conflicting libraries - a year or two ago it was more along the lines of g++ bugs). slang compiled but as soon as I was asked a question but mutt you could see there was a program -- my reply wasn't noticed. I'll keep trying. no problem (report bugs) -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Mutt on Mac OS X ?
On Fri, Oct 27, 2000 at 11:43:10AM +0100, John Wright wrote: Ah, post-5.1. yes the latest one didn't get past running the c++ compiler. what was the error message? (most of the g++ problems currently are due to things like missing or conflicting libraries - a year or two ago it was more along the lines of g++ bugs). It looked like g++ bugs as malloc/free were moaning about things and the compiler didn't actually quit but stopped moaning. well, if you have a build-log I can take a look see if there's something that I can fix (library mismatches and compiler bugs aren't, but there's always the possibility of a conflicting #define). -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Mutt on Mac OS X ?
You may wish to try ncurses instead of the system-supplied curses library. May be a good idea anyways. On 2000-10-17 11:30:45 +0100, John Wright wrote: Date: Tue, 17 Oct 2000 11:30:45 +0100 From: John Wright [EMAIL PROTECTED] To: Mutt Users ML [EMAIL PROTECTED] Subject: Re: Mutt on Mac OS X ? Mail-Followup-To: Mutt Users ML [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i On Thu, Oct 12, 2000 at 02:14:36PM -0700, Eugene Lee wrote: Just wondering if anyone has gotten Mutt to work under the Mac OS X Public Beta. 1.2.4i didn't compile because it couldn't find things like A_NORMAL. I did find a curses library in some odd place, I might try again with slang or something like that. -- Thomas Roessler [EMAIL PROTECTED]
Re: Mutt on Mac OS X ?
On Tue, 17 Oct 2000, John Wright wrote: On Thu, Oct 12, 2000 at 02:14:36PM -0700, Eugene Lee wrote: Just wondering if anyone has gotten Mutt to work under the Mac OS X Public Beta. 1.2.4i didn't compile because it couldn't find things like A_NORMAL. I did find a curses library in some odd place, I might try again with slang or something like that. I'm told that ncurses (post-5.1) builds/works on OS X. No matter what you use you'll have trouble with the config.guess and config.sub scripts, since those cases were only added this year. -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
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]
