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)

Solaris 8 make error building man pages

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

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