[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Starting the final call for features for 1.7

From: Laura Creighton
Subject: Re: [Nmh-workers] Starting the final call for features for 1.7
Date: Sun, 25 Sep 2016 12:19:00 +0200

In a message of Sat, 24 Sep 2016 16:44:38 -0400, David Levine writes:
>Laura wrote:

>I don't think you need that with nmh 1.6, and you shouldn't with 1.7,
>assuming your locale (LANG, LC_ALL, or LC_CTYPE environment variable)
>is set to a utf-7 or utf-8 (preferred by some) locale.

Yes, but I need my .mh_profile to work _everywhere_ including on machines
that are purposely not set to utf-8 so we can test software there.

>> The problem is that you typically get your new nmh one day when you, or
>> maybe the sysadmins at work, do a system-wide update.  Since you never
>> asked for it to get changed, you never noticed that you have a new
>> version (unless things stop working for some reason). I am not sure what
>> the best way to handle this is,
>Build your own nmh?  If you want to give that a quick try:
>    $ git clone git://git.savannah.nongnu.org/nmh.git
>    $ cd nmh
>    $ docs/contrib/build_nmh -div

I can do this, but the problem I am talking about is not 'how do I get
my own nmh, should I need to build one' but 'how to inform users whose
nmh has changed out from under them, because the package just was updated
on their distribiution that this has occurred', with the added proviso
that the person doing the update may not be the person using nmh.

For instance, I was blissfully unaware of this mailing list and that
nmh was ever under active development until a few years ago, and I
suspect that there are quite a few others out there who are still in
this position.  We just didn't give it any thought, like all things that
quietly go on working without needing any effort on our part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]