Re: [patch] fixed signed int overflow (in move.c)

Christ van Willegen wrote: Hello Dominique, On Mon, Nov 5, 2012 at 8:40 PM, Dominique Pellé dominique.pe...@gmail.com wrote: Attached patch fixes it but please review it. This part of the diff looks off to me: -if (h4 + h3 + h2 min_height || h3 + h2 + h1 min_height) +if (h4

feature request: read svgz files

Hi, This is a feature request to be able to read and write .svgz files. It is already possible to read/write *.txt.gz files. It is already possible to read/write .svg files. It is already possible to read/write .svg.gz files, but .svg files that are compressed with gzip don't have .svg.gz file

Re: [patch] fixed undefined behavior found with IOC tool

Dominique Pelle wrote: I ran make test with vim-7.3.712 compiled with IOC (http://embed.cs.utah.edu/ioc/), a tool that detects integer overflows, which behave in undefined way according to the C standard. Only unsigned integer is guaranteed to behave in a predictable way. IOC found a few

[patch] problem with backslash escaped strings in expand(), glob(), etc...

Bram, there seems to be a problem with backslash escaped strings when using expand(), glob() or globpath(): #v+ cb@host: mkdir -p /tmp/test ch@host: touch /tmp/test/bar /tmp/teest/foo\\1 cb@host: vim -u NONE -U NONE -N -c ':e /tmp/test/bar|echo expand(@#)|echo expand(#)' /tmp/test/foo\\1 #v-

cpo re-visited

Hello Bram, hello folks, (cc'ing vim dev) if this already has been discussed excuse me. Some time ago we had a discussion about how to handle specific settings in Vim the correct way. Now some time later i think i have a approach that could be of some use in this regard. example code follows: