Hi,
When I was upgrading the OpenBSD nmh package from 1.4 to 1.5rc1, the build
errored out, because OpenBSD does not have utmpx.h. Speaking with other
devs implies that this is unlikely to ever be supported on OpenBSD.
Reverting 7ba29497ff3f164e2a507eda35e81f1cb0658c74 lets nmh build again
on
Ken Hornstein k...@pobox.com writes:
There are a large number of changes in this release; the release notes
(see the NEWS file in the distribution)
I got tired just reading the NEW FEATURES section.
Norman Shapiro
___
Nmh-workers mailing list
When I was upgrading the OpenBSD nmh package from 1.4 to 1.5rc1, the build
errored out, because OpenBSD does not have utmpx.h. Speaking with other
devs implies that this is unlikely to ever be supported on OpenBSD.
Seriously? What the hell?
utmpx is part of POSIX; utmp is not. There was a
Ken Hornstein k...@pobox.com writes:
Greetings all,
I am pleased to announce the first release candidate (RC1) of nmh 1.5 is now
available. You can find it for download here:
INSTLLL says:
For routine installation on popular platforms, the shell script in
docs/contrib/build_nmh can be used
For routine installation on popular platforms, the shell script in
docs/contrib/build_nmh can be used to guide you through configuration.
It will then build and optionally (with -i) install in the configured
location.
I can't find a file named build_nmh anywhwere in the distribution.
I am pleased to announce the first release candidate (RC1) of nmh 1.5 is now
available.
Are requests for new feature, sans code. in order yet?
Sure, go for it. Obviously no new features will be in 1.5, but I can't
think of a reason to not talk about what comes next.
--Ken
Oliver wrote:
I tried compiling and installing on Solaris. It all builds fine but I
get the following message repeated a number of times:
./man/mh-chart-gen.sh: !: not found
! is not available in pure Bourne shell and should be avoided.
There are several options, we could use:
echo $i |
! is not available in pure Bourne shell and should be avoided.
Minor nit: ! is in POSIX; the problem here is Solaris has an ancient sh
implementation (isn't there a POSIX one in something like /usr/xpg4/bin ?).
Same with -E for grep.
I'm fine with workarounds for Solaris, but I'm wondering if we
Ken wrote:
Minor nit: ! is in POSIX; the problem here is Solaris has an ancient
sh implementation (isn't there a POSIX one in something like
/usr/xpg4/bin?). Same with -E for grep.
I'm fine with workarounds for Solaris, but I'm wondering if we want
to tackle this in a different way.
On 4/24/2012 2:13 PM, Ken Hornstein wrote:
... Googling utmpx OpenBSD ... yeah, okay, I guess I don't need to
say anything more.
Reverting 7ba29497ff3f164e2a507eda35e81f1cb0658c74 lets nmh build again
on OpenBSD. Can this change be applied?
I am reluctant to bring this code back, as it was
I and at least one other user -- and probably many others, have .mh_profile
entries that we added years ago, for reasons now obscure and not remembered.
There ought to be an easy way to incorporate comments in that file. As I read
the man page, there is none provided.
Yeah let me speak on
My long standing work around for this, is to use the profile entry #
As in
#:#
#: System wide variables
Aliasfile: aliases
Draft-Folder: drafts
editor: emacs
#:#
#: Program defaults
...
Works like a charm
___
Nmh-workers mailing list
On 2012-04-24, at 9:21 AM, Ken Hornstein wrote:
Minor nit: ! is in POSIX; the problem here is Solaris has an ancient sh
implementation (isn't there a POSIX one in something like /usr/xpg4/bin ?).
Same with -E for grep.
You cannot sanely use a Solaris system without putting /usr/xpg4/bin at
You cannot sanely use a Solaris system without putting /usr/xpg4/bin at
the front of your $PATH. If the auto* tools can arrange for this to
happen in the appropriate places, they should.
There is some stuff to do that already in Autotools. I know it
will search /usr/xpg4/bin for the right grep
Thanks, Jerry!
My FAQ posts are on auto-pilot. I actually don't read Usenet any more
either, but I do use Gnus to read gmane mailing lists (including
gmane.mail.nmh.devel).
JerryHeyman heym...@bellsouth.net writes:
On Sun, 22 Apr 2012 14:56:22 -0500, Ken Hornstein k...@pobox.com wrote:
I've
Me too:
#: Variable Settings
...
Maybe we should simply reserve # as a profile component and document
#: as the .mh_profile comment character(s) rather than leave it as a
puzzle.
Earl Hood e...@earlhood.com writes:
On Tue, Apr 24, 2012 at 11:23 AM, norm wrote:
I and at least one other
Maybe we should simply reserve # as a profile component and document #:
as the .mh_profile comment character(s) rather than leave it as a puzzle.
Makes sense to me. If documenting, point out that you cannot have blank lines,
hence my use of #:# To separate blocks, although if someone were so
Is there a way that scripts can use locking compatibly with the locking
used by the local nmh installation. If not there should be. If so, is
it documented, if not it should be.
Norman Shapiro
798 Barron Avenue
Palo Alto CA 94306-3109
(650) 565-8215
n...@dad.org
Hi Ken,
Ken Hornstein writes:
I am reluctant to bring this code back, as it was messy. But ... let me
offer a compromise. The code is only needed by rcvtty (will output a message
to your terminal) and slocal (actually, looking at slocal ... that usage
seems to be undocumented; anyone know what
19 matches
Mail list logo
