Sorry - the last one didn't include printing of the prompt - I was mostly
concerned with getting exmh to work
*** ruserpass.c.origFri Apr 30 14:08:34 1999
--- ruserpass.c Mon Nov 29 14:45:04 1999
***
*** 178,183
--- 178,210
return(-1);
}
+ #include
+ char
I tried posting this to [EMAIL PROTECTED], but it didn't get posted.
I recently tried to configure nmh 1.0.2 to work as a POP client on a
Mandrake Linux 6.1 system, which uses glibc 2.1.1, and it didn't work.
The problem is the glibc edition of 'ruserpass.c', which is called by 'inc'
to get the
I recently tried to configure nmh 1.0.2 to work as a POP client on a
Mandrake Linux 6.1 system, which uses glibc 2.1.1, and it didn't work.
The problem is the glibc edition of 'ruserpass.c', which is called by 'inc'
to get the user password. The glibc edition of ruserpass won't prompt the user
Is this list dead?
I'd appreciate feedback on my recent submission (will it be accepted, etc?).
I'd also like to discuss a better solution to the ruserpass() issue, and
I'm willing to do the work to expunge it from nmh entirely.
TIA
Last November, I submitted a bug report with patches for nmh - it didn't work
as a POP client properly on Linux systems. But unfortunately, the patches
didn't get into the 1.0.4 release, so here goes again:
The Symptom: Unless .netrc is used, on systems using glibc 2.1.1, 'inc' fails
to work wh
> My solution was to completely take out any dependency on system ruserpass,
> and use the version packaged with nmh. If you want to take advantage of
> this, I recommend you get the latext CVS version.
I think that this is the best solution - it gets my vote!
There are quite a few bug fixes in the CVS repository that could help
folks out - isn't it time for a new release? In particular, I'm still
seeing reports of problems with POP access that I know were fixed about
a year ago...
Thanks..
This note generated a bit of positive response. So can there be a new
release now? I've just seen another note about POP access problems on
the exmh mailing list. Thanks!
There are quite a few bug fixes in the CVS repository that could help
folks out - isn't it time for a new release? In
Please!
Thanks.
A lot, but there's a refusal to kick the ball into the goal. There have been
many significant bug fixes over the last couple of years, but the maintainers
don't seem willing to issue a new release to the outside world
(UNFORTUNATELY!).
A bunch of stuff relating to accessing POP servers was fix
I can help get a next release out. At the very least, I can help with
testing, since I use nmh with my mail client.
On Thursday 09 May 2002 06:48 am, Anders Eriksson wrote:
> I have to agree with Ken and Earl. It's high time we get the sourcres
> under a more stable control. I'd say go for Savannah of sourceforge.
> I don't really care which, as log as I can get access to it!
>
> Is it time for a community poll
> I just compiled and installed without errors, but 'inc' is not working
> correctly.
For what it's worth, POP access in the most recent release 1.1-RC1 of nmh works
for me, with these two commands:
/usr/local/nmh/bin/inc -snoop +inbox -truncate -nochangecur -width 100 -host priam
-user asdf
Pa
Ken Hornstein <[EMAIL PROTECTED]> wrote:
> Everyone,
>
> I've created a nmh 1.1 release canidate. You can get it from:
>
> http://savannah.gnu.org/download/nmh/nmh-1.1-RC1.tar.gz
What's the difference between this release and the one I picked (and have
been using since then) in July?
I found this note in the 'vim' release notes:
When using "cmd | vim -", stdin is not a terminal. This gave problems with
GPM (Linux console mouse) and when executing external commands. Now close
stdin and re-open it as a copy of stderr.
The source for version 6 does this:
if (read_stdin)
The makefile in the man directory uses GNU "simply expanded variables" with
these lines:
MAN1 := $(MAN1SRC:.=.$(manext1))
MAN5 := $(MAN5SRC:.=.$(manext5))
MAN8 := $(MAN8SRC:.=.$(manext8))
However, Solaris 8 uses a System V make that uses ':=' for conditional
macro assignment.
My reading of the
On Thursday 05 June 2003 04:52 pm, Jerry Peek wrote:
> On 5 June 2003 at 15:40, Glenn Burkhardt <[EMAIL PROTECTED]> wrote:
> > Advice?
>
> I feel our momentum slowing here; thanks for waking us up, Glenn.
> Let's avoid waiting six more months until Jon has to na
Are you still sheparding this project? I remembered to look at
http://savannah.nongnu.org/projects/nmh
I noticed that there are outstanding bugs - I haven't had a chance to look
at the reports. Do you need help with them?
Please let's do it!!
I've been using nmh-1.1-RC1.tar.gz since Nov 18, 2002. It works. I give
it my blessing (for whatever that's worth!).
I've forgotten who had put it together and where it's hosted - does
anyone remember??
On Monday 02 June 2003 04:40 pm, you wrote:
> >Hi. Seems like we've had a 1.1 release candidate sitting for a long
> >time. Can we make it a release yet? It would be nice to have something
> >newer than 1.0.4 going into things like Linux distributions.
>
> Hm, well ... how about everyone (includ
The makefile in the 'man' directory works with GNU make, but not Sun
make (/usr/ccs/bin/make).
What's the preferred solution here? Require GNU make? If so, shouldn't the
configure script check for its presence, and set execution paths accordingly?
If vim 6.0 is installed on a Solaris system, the 'ex' program included with
vim 6.0 goes into an infinite loop when this statement in 'configure' is
executed:
if echo 'r /nonexist-file
q' | ex > /dev/null 2>&1
It seems wrong to me to include a newline in the string this way. It could be
re-
Sorry, spoke too soon. The real problem has to do with output redirection.
if echo 'r /nonexist-file
q' | ex
works but
if echo 'r /nonexist-file
q' | ex > /dev/null 2>&1
hangs.
Redirecting just standard output cause no problem. But there doesn't
seem any output to redirect anyway...
Attached is a patch for the problems I found with Solaris 8 and Mandrake 9.1
I've been trying to get a GNU Savannah login, but it looks like they are down
tonight.
It turns out that there are two database packages available with the Mandrake
distribution that support 'ndbm' calls: db1 (derived
Does anyone know the status of mailing lists? This request from 8/02
was for a user's mailing list.
Bart Massey submitted an update to the mh-format man page as part of
bug report 2031. I'm not an expert on the content, but it looks like
he's done a good job at improving this page.
Please review it, and if there are no corrections, I plan to commit it.
Thanks.
Name
mh-format - format f
Apparently the powers that be don't want informational messages to be part
of the 'In-Reply-To:" fields anymore (http://www.faqs.org/rfcs/rfc2822.html).
The obsolete fields could look like:
In-reply-to: Your message of "Fri, 27 Jun 2003 13:35:24 EDT."
<[EMAIL PROTECTED]>
which is w
Jeffery Honig has been unable to subscribe to the mailing list. He'd like any
comments any one has about his proposed patch. You should mail the comments
directly to him:
Jeffrey C Honig <[EMAIL PROTECTED]>
Index: h/fmt_scan.h
==
I've incorporated suggestions from Jerry Peek, and the new edition is
attached.
I've eliminated the obtuse reference to 'argument mode', and tried to explain
what the syntax is instead. I believe it was to distinguish between
functions/components used as escapes from functions/components used
I'd like to change the default components file to include a folder copy:
To:
cc:
Fcc: +sent-mail
Subject:
Most mail clients I've dealt with make a copy of sent mail by default, and
it's easier for new users to delete a line than to figure out how to
correctly add one.
I'll change the 'c
While trolling for patches, I was pointed to a problem reported by
Robert Elz last October. The order of the arguments "-list" and "-seq"
matters, as mentioned in the man page. In other words,
pick -list -seq x
and
pick -seq x -list
do not do the same thing. -seq implicitly me
> Bill Wohler wrote:
> I think a Fcc out of the box is entirely appropriate for new users. The
> Dcc usage that Earl suggests is a little more advanced, and is typically
> used with procmail which is even more advanced (although it is
> absolutely necessary these days). And remember that Dcc is sti
> Bill Wohler wrote:
> Note that in replcomps, the Fcc only appears if you specify "repl -fcc
> +outbox". But then it does appear in the header.
>
> Whatever we do should be consistent.
Jerry Peek had (privately) suggested this solution:
Fcc: %<{fcc}%{fcc}%|+outbox%>
as part of replcomps. This
Ok, I've committed changes to components, forwcomps, distcomps, replcomps,
replgroupcomps, based on the discussion. Only repl.man needed to be changed;
the other man pages dynamically pull in the current default template file
when the man page is built by 'make'.
34 matches
Mail list logo
