Re: Nmh on MacOs

[Ralph Corderoy]

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’ short discussion.

There is a text file which tracks your ‘current’ version and when nmh
realises it's more new then it says ‘Welcome’.  To locate that file,
replicate my commands but with the output you get.

$ mhparam path context
path: mail
context: context
$
$ cat ~/mail/context
Current-Folder: inbox
Version: nmh-1.7+dev
$

> I know one mistake I made was running inc while in root, but I don’t
> know how to fix it. 

Can you write to that context file?  Perhaps nmh is having trouble
storing the new version after it has said welcome.  I'd expect ~/mail
downwards to be owned by you, not root.  Or whatever your ‘path’ is
shown to be with the above mhparam(1) command.

$ cd
$ find `mhparam path` ! -user $LOGNAME
$


You'll see in the above thread that Ken gives a way of disabling the
welcome message but I wouldn't rush to do that in case your problem is
a symptom of a mess left by running inc as root.  You'd just be
disguising the underlying cause and hit a new problem instead.

-- 
Cheers, Ralph.

Re: Nmh on MacOs

[Jude DaShiell]

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 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 also have a 
> gui (emacs 30) and a cli emacs 29.3. Every time I press inc, I get this 
> message ,” 
> 
> Welcome to nmh version 1.8
>
> See the release notes in /opt/homebrew/Cellar/nmh/1.8_1/share/doc/nmh/NEWS
>
> Send bug reports, questions, suggestions, and patches to
> nmh-workers@nongnu.org.  That mailing list is relatively quiet, so user
> questions are encouraged.  Users are also encouraged to subscribe, and
> view the archives, at https://lists.gnu.org/mailman/listinfo/nmh-workers
>
> This message will not be repeated until nmh is next updated. “
>
>
> But the message is repeated. I can send mail, but not receive it.
> I used the simplest setting, where the mail gets handed off to gmail, I 
> haven’t set up any back end beyond installing mu, and nmh.
>
>  I know one mistake I made was running inc while in root, but I don’t know 
> how to fix it.
>
> Any help would be greatly appreciated,
> Eric A.
>

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

[Lyndon Nerenberg]

> 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 what the 3rd-party commercial software folks are doing.  
This sounds to me like a lot of application-private openssl libraries shipping 
with all sorts of software.  That can't end well.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Ken Hornstein]

>> 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
>> ancient:
>
>Dare I ask how anyone compiles TLS-enabled code on a Mac these days?!?

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.

(My understanding of the core issue is basically that the OpenSSL people
refused to commit to a stable ABI and that's really important to Apple).

--Ken

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Lyndon Nerenberg]

> 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 if you can't compile new source against it, and it also looks
> ancient:

Dare I ask how anyone compiles TLS-enabled code on a Mac these days?!?

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

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

[Tom Lane]

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 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10xxx).

> Once upon a time (<= 10.9?) there was a program you could run to switch the 
> default SDK for the command-line compilation tools.  I can't find it any more.

> I abandoned MacOS as a development platform a while ago, so I'm woefully 
> behind on the latest Xcode fu.  Are there any MacOS C developers out there 
> who can catch me up?

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
ancient:

$ ls -l /usr/lib/*ssl*
-rwxr-xr-x  1 root  wheel  400608 Sep  9  2014 /usr/lib/libssl.0.9.7.dylib*
-rwxr-xr-x  1 root  wheel  616560 Aug  5  2015 /usr/lib/libssl.0.9.8.dylib*
lrwxr-xr-x  1 root  wheel  18 Oct 18  2014 /usr/lib/libssl.dylib@ -> 
libssl.0.9.8.dylib

Personally I just install openssl from source into /usr/local and then
build/link against that.

regards, tom lane

___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers