Re: the release (Re: Solaris 'vim' configure bug)

2003-06-13 Thread Bill Wohler
[EMAIL PROTECTED] wrote: At least one patch (kre's) fixed a security bug (from memory). It'd be a shame to release without fixing those. Not to mention Mark's patch to fix broken scan lines. Since MH-E is already in an editor, it doesn't *call* an editor; so it is agnostic here. -- Bill

the release (Re: Solaris 'vim' configure bug)

2003-06-08 Thread mlh
On Thu, 5 Jun 2003 18:52:17 -0400 Glenn Burkhardt [EMAIL PROTECTED] wrote: A heretic. But I have no problem with declaring nmh 1.1rc1 a release, and let it go. There's a few bugs and/or patches listed or referenced from the nmh page at http://savannah.gnu.org/ I'd give you a better link

Re: Solaris 'vim' configure bug

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

Re: Solaris 'vim' configure bug

2003-06-06 Thread Jerry Peek
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 nag us again! There are a few problems, like the Mandrake ndbm.h file location, that don't sound too

Re: Solaris 'vim' configure bug

2003-06-06 Thread Glenn Burkhardt
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 nag us again! There are a few problems, like

Re: Solaris 'vim' configure bug

2003-06-06 Thread Simon Burge
On Thu, Jun 05, 2003 at 06:52:17PM -0400, Glenn Burkhardt wrote: After thinking about this on my drive home, it seems simpliest to eliminate the 21 at the end of the line. It looks like almost all 'vi' versions write messages to stdout, not stdin. And if they don't, the downside is that

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: