Re: A semi-annual poke about progress

2003-06-03 Thread Glenn Burkhardt
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?

Re: A semi-annual poke about progress

2003-06-03 Thread Ken Hornstein
Are you still sheparding this project? I remembered to look at Rather poorly, but yes (well, I just got back from a two week vacation in Europe). 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

Re: A semi-annual poke about progress

2003-06-03 Thread Ken Hornstein
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 (including me) makes sure what's on the 1.1 branch compiles on

Re: A semi-annual poke about progress

2003-06-03 Thread Jon Steinhart
I have it working on Solaris (albeit an old 2.6) and Linux RH9. 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

Re: A semi-annual poke about progress

2003-06-03 Thread Neil W Rickert
Glenn Burkhardt [EMAIL PROTECTED] wrote: Clues on what the test for 'broken vi' does are solicited. The vi on some systems (including solaris) returns a non-zero exit status if any command at all failed during the vi session. Presumably this makes sense if vi is running in the background from a

Solaris 8 build

2003-06-03 Thread Glenn Burkhardt
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?

Solaris 'vim' configure bug

2003-06-03 Thread Glenn Burkhardt
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 21 It seems wrong to me to include a newline in the string this way. It could be

Re: Solaris 'vim' configure bug

2003-06-03 Thread Glenn Burkhardt
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 21 hangs. Redirecting just standard output cause no problem. But there doesn't seem any output to redirect anyway...

Re: Solaris 'vim' configure bug

2003-06-03 Thread Jerry Peek
On 2 June 2003 at 22:13, Glenn Burkhardt [EMAIL PROTECTED] wrote: if echo 'r /nonexist-file q' | ex /dev/null 21 It seems wrong to me to include a newline in the string this way. It could be re-written as: echo 'r /nonexist-file\nq' | ex /dev/null 21 Unless I'm missing something,

Re: Solaris 'vim' configure bug

2003-06-03 Thread Ralph Corderoy
Hi, if echo 'r /nonexist-file q' | ex works but if echo 'r /nonexist-file q' | ex /dev/null 21 hangs. Redirecting just standard output cause no problem. But there doesn't seem any output to redirect anyway... Can you use strace on Solaris to see what ex is actually doing?

Re: Solaris 'vim' configure bug

2003-06-03 Thread Robert Elz
Date:Mon, 2 Jun 2003 22:23:17 -0400 From:Glenn Burkhardt [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] | Redirecting just standard output cause no problem. But there doesn't | seem any output to redirect anyway... On NetBSD Error: script, 1: