[ANN] Clewn and vimGdb 1.7

2006-04-09 Thread Xavier de Gaye
Hi all Clewn and vimGdb 1.7 have been released. The clewn project implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. You can get clewn and vimGdb from . New features: Clewn: an expression va

Missing reference to version7.txt in help.txt

2006-04-09 Thread Xavier de Gaye
I think a reference to version7.txt in the main help file is missing in the Versions section (in vim-7.0c12.zip). Versions |vi_diff.txt| Main differences between Vim and Vi |version4.txt| Differences between Vim version 3.0 and 4.x |version5.txt| Differences between Vim version 4.6 and 5.x |v

[vim 7.0d bug] Gtk asserts errors when hitting

2006-04-11 Thread Xavier de Gaye
I am running Vim 7.0d on FC3. 1 - the file 'no_m.vim' contains only the following line where 'm' has been removed from the default guioptions option: set guioptions=agirLtT 2 - run gvim with the following invocation: $ gvim -u no_m.vim -U NONE 3 - hit : The following messages are displayed

console menus priority

2006-04-12 Thread Xavier de Gaye
When running Vim 7.0d on FC3 as: $ gvim -u cfg.vim with cgf.vim as: "= " some sample menus with priorities an 01.100 To.up R an 01.200 To.down r an 02.100 Session.getsession:source ~/.vim/wk/ an 02.200 Ses

Re: console menus priority

2006-04-13 Thread Xavier de Gaye
--- Bram Moolenaar wrote: > > Xavier de Gaye wrote: > > > When running Vim 7.0d on FC3 as: > > > > $ gvim -u cfg.vim > > > > with cgf.vim as: > > > > "= > > " some

Re: Netbeans Interface

2006-06-01 Thread Xavier de Gaye
--- Sebastian Menge <[EMAIL PROTECTED]> wrote: > Under *netbeans-configure* it is said, that "only gvim is supported". > > Does that mean i never can use the netbeans-interface in a terminal > (since the dependency on gvim is hardcoded in netbeans.c)? > > Or does it mean that i have to compile m

Re: Netbeans Interface

2006-06-01 Thread Xavier de Gaye
--- Sebastian Menge <[EMAIL PROTECTED]> wrote: > Am Donnerstag, den 01.06.2006, 12:49 -0700 schrieb Xavier de Gaye: > > Netbeans can only be used with gvim compiled either with GTK, Motif, or > > with the Windows version of gvim. It cannot be used with plain vim > > ru

[ANN] Clewn and vimGdb 1.8

2006-06-18 Thread Xavier de Gaye
Hi all Clewn and vimGdb 1.8 have been released. The clewn project implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. You can get clewn and vimGdb from . New features: vimGdb is ported to Vi

[ANN] Clewn and vimGdb 1.8.1

2006-07-23 Thread Xavier de Gaye
Hi all, Clewn and vimGdb 1.8.1 have been released. The clewn project implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. You can get clewn and vimGdb from . Bug fixes: Fixed jumping back to l

Forget the buf_T reference when processing a 'close' netbeans command

2006-08-03 Thread Xavier de Gaye
Bug description: === Vim version 7.0 When receiving a netbeans 'close' command, vim does delete the specified buffer, but the buffer's reference (buf_list[bufno].bufp called here 'this_memory_address') is still kept in buf_list[]. It may happen that this_memory_address is once again re

Re: Forget the buf_T reference when processing a 'close' netbeans command

2006-08-05 Thread Xavier de Gaye
--- Bram Moolenaar wrote: > > Xavier de Gaye wrote: > > > Bug description: > > === > > Vim version 7.0 > > > > When receiving a netbeans 'close' command, vim does delete the > > specified buffer, but the buffer's referenc

[ANN] Clewn and vimGdb 1.9

2006-08-27 Thread Xavier de Gaye
Hi all Clewn and vimGdb 1.9 have been released. The clewn project implements full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. You can get clewn and vimGdb from . New features: The 'restart' command

Current buffer name after :python os.chdir()

2006-11-07 Thread Xavier de Gaye
Assuming the current buffer is the file 'foobar' in the current directory. After running the following Vim commands: :python import os :python os.chdir("subdir") the current buffer name is not changed as it is when you run the Vim command ':cd subdir' (but the output of ':pwd' is Ok), an

[RFC] Add a new getAnno function to the netbeans protocol

2006-11-07 Thread Xavier de Gaye
During the "compile-debug-edit" development cycle, the signs placed in the Vim buffers by the IDE with the netbeans protocol can have their line numbers changed when the buffers are edited (a Vim sign sticks with the line it has been set upon, and moves with it). It would be nice to allow the IDE

Re: Current buffer name after :python os.chdir()

2006-11-07 Thread Xavier de Gaye
--- Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Xavier de Gaye wrote: > > > Assuming the current buffer is the file 'foobar' in the current > > directory. After running the following Vim commands: > > > > :python import os > > :py

Re: [RFC] Add a new getAnno function to the netbeans protocol

2006-11-11 Thread Xavier de Gaye
--- Bram Moolenaar <[EMAIL PROTECTED]> wrote: > Xavier de Gaye wrote: > > > During the "compile-debug-edit" development cycle, the signs placed in > > the Vim buffers by the IDE with the netbeans protocol can have their > > line numbers changed when the bu

Gvim blinking on processing netbeans commands

2007-04-20 Thread Xavier de Gaye
The gvim screen is blinking when receiving netbeans command. This happens even when the signs that are being moved around are not visible in the displayed windows. The following patch fixes this problem. Patch based on stable vim 7.0 Problem:gvim blinking on processing the addAnno command Sol

Re: Gvim blinking on processing netbeans commands

2007-04-21 Thread Xavier de Gaye
--- Bram Moolenaar wrote: > > Xavier de Gaye wrote: > > > The gvim screen is blinking when receiving netbeans command. This > > happens even when the signs that are being moved around are not visible > > in the displayed windows. The following patch fixes

[ANN] vimgdb 1.11

2007-05-30 Thread Xavier de Gaye
Hi all Vimgdb 1.11 is a port of vimgb to Vim 7.1. Vimgdb is a vim patch implemented as a vim optional feature that provides full gdb support in the vim editor: breakpoints, watch variables, gdb command completion, assembly windows, etc. You can get vimgdb from . Xa