Win32 vim.exe blows up reading from stdin

2006-10-12 Thread Dave Roberts
Hello all, Somewhere between v7.0.118 and v7.0.131 Vim started blowing up when started with a - to read from stdin. Ex. vim -u NONE - If no one else is having this problem I'll supply more compile/environment info. I use gvim as a less program all the time so I know this wasn't happening

Re: Convert2HTML Again

2006-10-12 Thread Edd Barrett
On 12/10/06, Benji Fisher [EMAIL PROTECTED] wrote: span class=bar (text) /span in the body, while the non-CSS version will have something like font color=#EEE bgcolor=333 (text) /font and now the CSS version is easier to read. Yes I see, If i had written this from scratch i

Patch 7.0.132

2006-10-12 Thread Bram Moolenaar
Patch 7.0.132 (after 7.0.130) Problem:Win32: Crash when Vim reads from stdin. Solution: Only use mch_nodetype() when there is a file name. Files: src/fileio.c *** ../vim-7.0.131/src/fileio.c Tue Oct 10 18:43:50 2006 --- src/fileio.cThu Oct 12 20:50:35 2006 *** ***

Re: Win32 vim.exe blows up reading from stdin

2006-10-12 Thread Bram Moolenaar
Dave Roberts wrote: Somewhere between v7.0.118 and v7.0.131 Vim started blowing up when started with a - to read from stdin. Ex. vim -u NONE - If no one else is having this problem I'll supply more compile/environment info. I use gvim as a less program all the time so I know this

RE: Why not commit runtime files?

2006-10-12 Thread Suresh Govindachar
A.J.Mechelynck wrote: Suresh Govindachar wrote: Hello, I have just found out that while the runtime directory is periodically updated on the ftp site, it is not committed to the cvs repository. What is the reason for not committing runtime files into cvs? I see

Re: Why not commit runtime files?

2006-10-12 Thread David Brown
A.J.Mechelynck wrote: I see some comment about runtime files not having patches; but committing to cvs does not require creating a patch; one can just command cvs to commit a local directory to the repository. I don't know exactly; but I think the various repositories (rsync, FTP, CVS,

Re: Why not commit runtime files?

2006-10-12 Thread Mikolaj Machowski
I don't know exactly; but I think the various repositories (rsync, FTP, CVS, SVN) are not maintained by the same people. I think CVS and SVN use the FTP site as a master with automated updates (but not every day), so that the FTP updates trickle down to the CVS/SVN repositories after a delay

Re: Why not commit runtime files?

2006-10-12 Thread A.J.Mechelynck
David Brown wrote: [...] I had the same kind of problem when maintaining CVS for vim 6. I tried updating the runtime files, and would occasionally get a patch that wouldn't apply, because something did get patched in a runtime file. Dave Yeah. Nowadays I rsync my runtime files from time to

Re: vim and 64bit xp

2006-10-12 Thread A.J.Mechelynck
Brian Krusic wrote: Thanks fo rthe reply. Still no shell extension. I did the regedit approach. Any ideas? Is Gvimext.dll in a directory in your PATH? Check it at the dos-box prompt: echo %PATH% or in Vim: :echo $PATH If it isn't, you can set it in (IIRC) Control Panel -

[Fwd: Re: vimshell feature? [oops]]

2006-10-12 Thread A.J.Mechelynck
Apparently the second try didn't succeed any better than the first one. This way you (David) won't need to try a third time. I'm sending it to vim-dev rather than vim@ because IMHO it's more on-topic for that list. Original Message Subject: Re: vimshell feature? [oops]