Hi,
2013/04/13 Sat 9:09:51 UTC+9 Ken Takata:
>
> Hi,
>
> Library name for +lua/dyn can't be retrieved properly on Ubuntu and Fedora
> (64 bit). The actual name is 'liblua5.1.so.0' on Ubuntu 12.04 and
> 'liblua-5.1.so.0' on Fedora 17, but Vim tries to use 'liblua.so.5.1'.
> There were three prob
Hi,
Library name for +lua/dyn can't be retrieved properly on Ubuntu and Fedora
(64 bit). The actual name is 'liblua5.1.so.0' on Ubuntu 12.04 and
'liblua-5.1.so.0' on Fedora 17, but Vim tries to use 'liblua.so.5.1'.
There were three problems:
1. The configure script tried to search /usr/lib/, but
Hi,
I hear that the config directory of Python3 will be changed on
Ubuntu 13.04 because of multiarch support. E.g. it becomes
/usr/lib/python3.3/config-3.3m-i386-linux-gnu/ on Ubuntu 13.04 32bit.
Currently the configure script can't find this directory.
The config directory of Python2/3 can be re
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 128 by dominiqu...@gmail.com: valgrind error "Invalid read of
size 1" in find_var_in_ht (eval.c:20062) in test91
http://code.google.com/p/vim/issues/detail?id=128
Valgrind memory checker reports the following error when
run
Hi Yegappan!
On Do, 11 Apr 2013, Yegappan Lakshmanan wrote:
> Hi all,
>
> I am running Vim 7.3.831 on a Linux system built with GTK 2.0.
> When I execute the following steps, Vim crashes:
>
> 1. Open an empty buffer
> 2. Enter insert mode using 'i'
> 3. Insert 262040 characters using =repeat('a
On 2013-04-12, Lech Lorens wrote:
>
> On 12 April 2013 13:45, Bram Moolenaar wrote:
>
>
> The updated docs say:
> Unix$HOME/.gvimrc or $HOME/.vim/gvimrc
> Unix$HOME/.vimrc or $HOME/.vim/vimrc
>
> What does that "or" mean? What if
quidame wrote:
> > Please don't forget to email me a new version if you make improvements.
>
> That's the case (see attachment).
> This new version adds keywords for Aptitude keybinding options.
Thanks. Looks like I didn't include the files from last year yet, I'll
move it up in the todo list.
Yukihiro Nakadaira wrote:
> > I have a note in the todo list that test 85, when run with valgrind,
> > finds memory leaks in Lua. Did you every run with Lua under valgrind?
> >
>
> I found a few memory leaks in if_lua.c.
> Please check the attached patch.
Great, thanks.
--
hundred-and-one sy
Hi,
On Fri, Apr 12, 2013 at 8:35 AM, Yegappan Lakshmanan
wrote:
> Hi Dominique,
>
> On Fri, Apr 12, 2013 at 3:23 AM, Dominique Pellé
> wrote:
>> Yegappan Lakshmanan wrote:
>>
>>> Hi all,
>>>
>>> I am running Vim 7.3.831 on a Linux system built with GTK 2.0.
>>> When I execute the following steps
On Thu, Apr 11, 2013 at 6:07 AM, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
> > lua is managing vim objects in cache table to release with finalizer.
> > So it doesn't need to call something in luaV_dict_gc/luaV_list_gc to
> > undef vim objects. it makes double free.
>
> Thanks for the
Hi Dominique,
On Fri, Apr 12, 2013 at 3:23 AM, Dominique Pellé
wrote:
> Yegappan Lakshmanan wrote:
>
>> Hi all,
>>
>> I am running Vim 7.3.831 on a Linux system built with GTK 2.0.
>> When I execute the following steps, Vim crashes:
>>
>> 1. Open an empty buffer
>> 2. Enter insert mode using 'i'
Lech Lorens wrote:
> On 12 April 2013 13:45, Bram Moolenaar wrote:
>
> >
> > The updated docs say:
> > Unix$HOME/.gvimrc or $HOME/.vim/gvimrc
> > Unix$HOME/.vimrc or $HOME/.vim/vimrc
> >
> > What does that "or" mean? What if both files exist?
> >
Yukihiro Nakadaira wrote:
> b:, w: and t: become invalid after closing buffer/window/tabpage.
>
> Steps to reproduce:
> $ vim -u NONE
> :let x = [b:, w:, t:]
> :tabnew
> :1bwipeout
> :echo x
> SEGV
> (or [{}, {}, {}] is shown. "vim -g" seems rather easy to reproduce crash)
>
> I
Hi,
message d'origine
De: Bram Moolenaar
A: "bilibop project"
Cc: vim_dev@googlegroups.com
Sujet: Re: [PATCH] add syntax file for apt.conf
Date: Fri, 05 Oct 2012 22:16:19 +0200
> Please don't forget to email me a new version if you make improvements.
That's the case (see attac
Hi Tony,
On Fri, Apr 12, 2013 at 2:50 AM, Tony Mechelynck
wrote:
>
> On 12/04/13 09:48, Nazri Ramliy wrote:
>>
>> On Fri, Apr 12, 2013 at 9:48 AM, Yegappan Lakshmanan
>> mailto:yegapp...@gmail.com>> wrote:
>>
>> 1. Open an empty buffer
>> 2. Enter insert mode using 'i'
>> 3. Insert 2
On 12 April 2013 13:45, Bram Moolenaar wrote:
>
> The updated docs say:
> Unix$HOME/.gvimrc or $HOME/.vim/gvimrc
> Unix$HOME/.vimrc or $HOME/.vim/vimrc
>
> What does that "or" mean? What if both files exist?
>
> This is an important thing, where yo
b:, w: and t: become invalid after closing buffer/window/tabpage.
Steps to reproduce:
$ vim -u NONE
:let x = [b:, w:, t:]
:tabnew
:1bwipeout
:echo x
SEGV
(or [{}, {}, {}] is shown. "vim -g" seems rather easy to reproduce crash)
I wrote patch for this problem.
Please check the attac
Patch 7.3.888
Problem:Filename completion with 'fileignorecase' does not work for
multi-byte characters.
Solution: Make 'fileignorecase' work properly. (Hirohito Higashi)
Files: src/misc2.c
*** ../vim-7.3.887/src/misc2.c 2013-03-19 18:31:45.0 +0100
--- src/misc2.c
Lech Lorens wrote:
> :help :read! does not mention that it's possible to specify options with
> this form of the :read command.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
151. You find yourself engaged to someone you've never actually met,
except through e-mail.
Patch 7.3.887
Problem:No tests for Visual mode operators, what 7.3.879 fixes.
Solution: Add a new test file. (David Bürgin)
Files: src/testdir/test94.in, src/testdir/test94.ok,
src/testdir/Make_amiga.mak, src/testdir/Make_dos.mak,
src/testdir/Make_ming.mak, src/t
Lech Lorens wrote:
> The attached patch makes it possible to move the vimrc and gvimrc files
> to your vim settings directory:
> ~/.vim/ (UNIX)
> ~\vimfiles\ (Windows)
True.
> etc. This makes it easier to move Vim settings from machine to machine:
> you just copy one directory to the right pl
Patch 7.3.886
Problem:Can't build with multi-byte on Solaris 10.
Solution: Add #ifdef X_HAVE_UTF8_STRING. (Laurent Blume)
Files: src/ui.c
*** ../vim-7.3.885/src/ui.c 2013-03-13 17:50:20.0 +0100
--- src/ui.c2013-04-12 12:24:10.0 +0200
***
*** 1458,14
Yegappan Lakshmanan wrote:
> Hi all,
>
> I am running Vim 7.3.831 on a Linux system built with GTK 2.0.
> When I execute the following steps, Vim crashes:
>
> 1. Open an empty buffer
> 2. Enter insert mode using 'i'
> 3. Insert 262040 characters using =repeat('a', 262040)
> 4. Press
> 5. Select a
Patch 7.3.885
Problem:Double free for list and dict in Lua. (Shougo Matsu)
Solution: Do not unref list and dict. (Yasuhiro Matsumoto)
Files: src/if_lua.c
*** ../vim-7.3.884/src/if_lua.c 2013-02-14 22:19:47.0 +0100
--- src/if_lua.c2013-04-12 11:42:56.0 +0200
***
Yasuhiro Matsumoto wrote:
> > Did you every run with Lua under valgrind?
>
> Not yet. Lua works with incremental GC. Some objects which is set
> undef but not freed remains on memory, i guess.
Is there a call to the Lua library to have it clean up and free all
memory? It should be called in l
On 12/04/13 09:48, Nazri Ramliy wrote:
On Fri, Apr 12, 2013 at 9:48 AM, Yegappan Lakshmanan
mailto:yegapp...@gmail.com>> wrote:
1. Open an empty buffer
2. Enter insert mode using 'i'
3. Insert 262040 characters using =repeat('a', 262040)
4. Press
5. Select and yank all the c
:help :read! does not mention that it's possible to specify options with
this form of the :read command.
diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt
index 4db4341..0048c75 100644
--- a/runtime/doc/insert.txt
+++ b/runtime/doc/insert.txt
@@ -1869,7 +1869,8 @@ NOTE: These commands
The attached patch makes it possible to move the vimrc and gvimrc files
to your vim settings directory:
~/.vim/ (UNIX)
~\vimfiles\ (Windows)
etc. This makes it easier to move Vim settings from machine to machine:
you just copy one directory to the right place and it works.
Please, check and app
On Fri, Apr 12, 2013 at 9:48 AM, Yegappan Lakshmanan wrote:
> 1. Open an empty buffer
> 2. Enter insert mode using 'i'
> 3. Insert 262040 characters using =repeat('a', 262040)
> 4. Press
> 5. Select and yank all the characters using 'V' and 'y'
> 6. Wait for a few seconds and move the cursor
>
>
29 matches
Mail list logo