Re: Nmh on MacOs

Hi Eric, > I have mu, nmh, dape, and slime on my emacs I think Emacs users like the MH-E interface to nmh: https://mh-e.sourceforge.io. > Every time I press inc, I get this message This is quite common. https://lists.nongnu.org/archive/html/nmh-workers/2023-03/msg3.html was one ‘recent’

Re: Nmh on MacOs

You don't press inc. You run inc from your user account in the terminal. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Wed, 17 Apr 2024, Eric Arillo wrote: > Hi All, I’m Eric. Here is my

Nmh on MacOs

Hi All, I’m Eric. Here is my dilemma: New to emacs and nmh. I have nm-h version 1.8 installed. I’ve read and re-read the mail documentation in emacs, and tried to read the nm-h man, but lost my way a little. I am on a macOS 14.4.1 , Sonoma. I have mu, nmh, dape, and slime on my emacs, I

Re: [Nmh-workers] macos x 11 :-P

> On Feb 24, 2016, at 6:10 AM, Ken Hornstein wrote: > > I (and I assume everyone else) install OpenSSL via MacPorts (or fink, if > you prefer) and use that. I can say that on my end there is ZERO interest > in porting nmh to use the native TLS library. I was thinking more of

Re: [Nmh-workers] macos x 11 :-P

>> Apple stopped shipping the openssl headers a year or two back. (The >> copies you see must be from back-rev SDKs; there are none on my laptop.) >> It looks like they still provide the shared library, but it's pretty >> useless if you can't compile new source against it, and it also looks >>

Re: [Nmh-workers] macos x 11 :-P

> On Feb 23, 2016, at 9:08 PM, Tom Lane wrote: > > Apple stopped shipping the openssl headers a year or two back. (The > copies you see must be from back-rev SDKs; there are none on my laptop.) > It looks like they still provide the shared library, but it's pretty > useless

Re: [Nmh-workers] macos x 11 :-P

Lyndon Nerenberg writes: > So I tried building on El Torrito Burrito whatever-the-fsck-name current > version of MacOS, tonight. (10.11.3, Xcode 7.2.1 (7C1002).) > Epic fail. cpp doesn't know the location of openssl/ssl.h (which does exist, > in several locations under >