On May 19, 6:28 pm, Tony Mechelynck
wrote:
> Either it's been fixed in one of
> the patches (if any) between what you have and 7.2.436 (but I don't see
> anything obvious in the README of the patches), or else it's been
> corrected between 7.2 and 7.3a.
The bug is still present in 7.2.437 (window
Hi
I ran "make test" with Vim-7.3a BETA (f8222d1f9a73)
and all test passed. However, I then uncommented the
VALGRIND = ... line in src/testdir/Makefile file, and test61 failed:
Test results:
test61 FAILED
TEST FAILURE
$ diff -c test61.ok test61.failed
*** test61.ok 2010-05-24 08:32:37.5418290
Hello,
I just installed vim7.2.437 on linux.
It seems that some modification has been done.
Now when you type (with vimrc_example as .vimrc):
gvim -p file1 file2 file3
file1 is opened with the cursor position on line 100 at the MIDDLE of
the screen (OK)
file2 and file3 are opened with the cursor po
Björn Winckler wrote:
> I have set up a Git clone of the Vim Mercurial repo here [1] (complete
> with instructions on how this was done [2]).
Nice. Do you also have a page for how to use this? I could link that
from the Vim pages. The link you gave with [1] does not say how to pull
from the r
Dominique Pelle wrote:
> I ran "make test" with Vim-7.3a BETA (f8222d1f9a73)
> and all test passed. However, I then uncommented the
> VALGRIND = ... line in src/testdir/Makefile file, and test61 failed:
>
> Test results:
> test61 FAILED
> TEST FAILURE
>
> $ diff -c test61.ok test61.failed
> **
Cesar Romani wrote:
> Compiling the latest vim 7.3a on Win XP with MinGW I get:
>
> ... blowfish.c -o gobjZ/blowfish.o
> In file included from proto.h:153,
> from vim.h:1867,
> from blowfish.c:14:
> proto/sha256.pro:3: error: syntax error b
Bram Moolenaar wrote:
> Hari Kumar wrote:
>
> > Vim uses cindent for JS files which works in general nicely. There are
> > a few cases where this does not work correctly. F.e.
> >
> > var a = {
> > b: 1,
> > c: "hello"
> > }
> >
> > cindent would align b: 1 to col 0 and indent c: "hello" by
Lech Lorens wrote:
> > However, there's no reason to use 'tagfunc' for ^P/^N anyway. All
> > we want there is tag names, and no need to disambiguate tags of the
> > same name, so regardless, ^P/^N shouldn't use 'tagfunc'. Using
> > tagfunc will also slow it down since all tags files are looked a
Bram Moolenaar wrote:
> Dominique Pelle wrote:
>
>> I ran "make test" with Vim-7.3a BETA (f8222d1f9a73)
>> and all test passed. However, I then uncommented the
>> VALGRIND = ... line in src/testdir/Makefile file, and test61 failed:
>>
>> Test results:
>> test61 FAILED
>> TEST FAILURE
>>
>> $ diff
On 24 May 2010 11:52, Bram Moolenaar wrote:
>
> Björn Winckler wrote:
>
>> I have set up a Git clone of the Vim Mercurial repo here [1] (complete
>> with instructions on how this was done [2]).
>
> Nice. Do you also have a page for how to use this? I could link that
> from the Vim pages. The lin
Björn Winckler wrote:
> I have updated the docs [1] to show how to pull (using Git or
> Mercurial) with a note on how to check out the vim73 branch (since I'm
> guessing this is what most people want at the moment). Is there
> anything else worth mentioning on the wiki?
Thanks, I'll add a link
Hi
I see Valgrind errors in Vim-7.3a BETA (f8222d1f9a73) when using the
wundo command in an unnamed buffer:
$ valgrind --track-origins=yes vim -u NONE -c 'wundo! foo' 2> vg.log
==4800== Syscall param stat64(file_name) points to unaddressable byte(s)
==4800==at 0x499BC83: __xstat64@@GLIBC_2.
Dominique Pelle wrote:
> I see Valgrind errors in Vim-7.3a BETA (f8222d1f9a73) when using the
> wundo command in an unnamed buffer:
>
> $ valgrind --track-origins=yes vim -u NONE -c 'wundo! foo' 2> vg.log
>
> ==4800== Syscall param stat64(file_name) points to unaddressable byte(s)
> ==4800==
Dominique Pelle wrote:
> I also notice this additional error which happens sometimes
> when loading the persistent undo file:
>
> =3D=3D14996=3D=3D Invalid write of size 1
> =3D=3D14996=3D=3Dat 0x402753D: memmove (mc_replace_strmem.c:629)
> =3D=3D14996=3D=3Dby 0x81A62C0: u_read_undo (str
As you may have noticed, I have added the persistent undo patch
yesterday. The core of this was done by Jordan Lewis.
This means you can make changes to a file, quit Vim, edit that same file
and undo the previous changes.
I have added a few things, such as computing a hash of the text to
verify
On May 24, 1:06 pm, Bram Moolenaar wrote:
> I have also changed the MS-Windows installer. It should now work in
> Windows 7. I also tried making the "Edit with Vim" context menu work
> for 64 bit systems, but it doesn't appear to work yet.
>
> You can try the self-installing executable:
> ftp:/
On Mon, May 24, 2010 at 3:06 PM, Bram Moolenaar wrote:
>
> As you may have noticed, I have added the persistent undo patch
> yesterday. The core of this was done by Jordan Lewis.
> This means you can make changes to a file, quit Vim, edit that same file
> and undo the previous changes.
>
> I hav
Nico Raffo wrote:
> On May 24, 1:06=A0pm, Bram Moolenaar wrote:
> > I have also changed the MS-Windows installer. =A0It should now work in
> > Windows 7. =A0I also tried making the "Edit with Vim" context menu work
> > for 64 bit systems, but it doesn't appear to work yet.
> >
> > You can try th
Jordan Lewis wrote:
> --0016e68ee46947c7a104875ce992
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Mon, May 24, 2010 at 3:06 PM, Bram Moolenaar wrote:
>
> >
> > As you may have noticed, I have added the persistent undo patch
> > yesterday. The core of this was done by Jordan Lewis.
>
Bram Moolenaar schrob am 24.05.2010 22:56:
I suppose most people will want Python 2.6. I'll see if I manage to
make that work. You can try it yourself, if you like.
It compiles without any problem in my builds. :-)
--
You received this message from th
On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
>
> Jordan Lewis wrote:
> > I suppose the argument could be made that the user who has added undo
> > persistence to her vimrc would have read enough of the documentation to know
> > that she must also set undodir if she doesn't want
On 24/05/10 22:30, Jordan Lewis wrote:
[...]
I am a bit concerned with your decision to write undo files to the
current directory by default, though. I think that it is "impolite" to
users to have Vim store its state (especially at the
1-statefile-per-file rate that undo persistence uses) directl
Hi
I see the following error with Valgrind in Vim-7.3a BETA (c81f0a037059)
when doing :wundo foo and when file foo already exists and has size 0:
==4957== Conditional jump or move depends on uninitialised value(s)
==4957==at 0x81BCB49: u_write_undo (undo.c:1293)
==4957==by 0x80AFBE6: ex
On Mon, May 24, 2010 at 4:39 PM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:
> On 24/05/10 22:30, Jordan Lewis wrote:
> [...]
>
> I am a bit concerned with your decision to write undo files to the
>> current directory by default, though. I think that it is "impolite" to
>> users to hav
On Mon, May 24, 2010 at 4:23 PM, James Vega wrote:
> On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
> >
> > Jordan Lewis wrote:
> > > I suppose the argument could be made that the user who has added undo
> > > persistence to her vimrc would have read enough of the documentation t
On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote:
[..]
I suppose most people will want Python 2.6. I'll see if I manage to
make that work. You can try it yourself, if you like.
I also have a patch to support Python 3. We'll have to see if
dynamically loading both will work. I
On 25 May 2010 06:06, Bram Moolenaar wrote:
>
> As you may have noticed, I have added the persistent undo patch
> yesterday.
There is a minor typo in the doc for 'persistent-undo'. Patch attached.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below t
hi,
i've just got a shiny new corei7 macbookpro with macosx-10.6.3
and i'm trying to compile an x11-motif vim-7.2.436 on it with:
>configure \
> --disable-darwin \
> --with-x \
> --enable-gui=motif \
> --enable-multibyte \
> --with-mac-arch=current \
> --with-f
hi,
i've just got a shiny new corei7 macbookpro with macosx-10.6.3
and i'm trying to compile an x11-motif vim-7.2.436 on it with:
>configure \
> --disable-darwin \
> --with-x \
> --enable-gui=motif \
> --enable-multibyte \
> --with-mac-arch=current \
> --with-f
unsub
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
30 matches
Mail list logo
