[ANN] vimgdb 1.11

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 http://clewn.sourceforge.net.

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

--- 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 buffers are edited (a Vim sign sticks with the line

Current buffer name after :python os.chdir()

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), and

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

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()

--- 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 :python os.chdir(subdir) the current buffer name is not changed

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

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

[ANN] Clewn and vimGdb 1.8.1

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 http://clewn.sourceforge.net. Bug fixes: Fixed jumping back to

[ANN] Clewn and vimGdb 1.8

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 http://clewn.sourceforge.net. New features: vimGdb is ported to Vim

Re: Netbeans Interface

--- 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 my own vim

Re: Netbeans Interface

--- 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 running in a terminal. No workaround

console menus priority

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 C-WRC-L an 01.200 To.down C-WrC-L an 02.100 Session.getsession:source ~/.vim/wk/ an

[vim 7.0d bug] Gtk asserts errors when hitting F10

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 F10: The following messages are