Re: problems with vim

Nageshwar M wrote: Hello, I compiled the vim 7.1 source for unix and installed it in my fedora core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert mode) , backspace is not working and when I pressed delete continuously the gvim is closing down. Someone please help me. The

Re: problems with vim

On 5/15/07, A.J.Mechelynck [EMAIL PROTECTED] wrote: Nageshwar M wrote: Hello, I compiled the vim 7.1 source for unix and installed it in my fedora core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert mode) , backspace is not working and when I pressed delete continuously the

Re: problems with vim

Hello, I tried in xterm, konsole, and yakuake but got the same problem. I guess the problem is with compilation options... When I used :set esckeys arrow keys working properly but not backspace (in gvim also i faced the same problem). Also the command completion is not working .. i typed :he and

patch 7.1.002

Patch 7.1.002 Problem:Oracle Pro*C/C++ files are not detected. Solution: Add the missing star. (Micah J. Cowan) Files: runtime/filetype.vim *** ../vim-7.1.001/runtime/filetype.vim Thu May 10 20:42:30 2007 --- runtime/filetype.vimTue May 15 09:12:06 2007 *** ***

Re: [Patch] proper detection of ProC files.

Micah Cowan wrote: Fixes an apparent typo in filetype.vim. Per https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916. Must have been there for a while. Thanks for the fix! -- In a world without fences, who needs Gates and Windows? /// Bram Moolenaar -- [EMAIL PROTECTED] --

Re: patch 7.1.002

Bram Moolenaar wrote: Patch 7.1.002 Problem:Oracle Pro*C/C++ files are not detected. Solution: Add the missing star. (Micah J. Cowan) Just to be clear: while I reformatted the solution in patch-form, it was Arturo Olguín Cruz who first found the bug and determined its fix:

Re: Stable Vim version 7.1 has been released

Francois Pinard wrote: [Bram Moolenar] Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. In fact,

Re: problems with vim

Thanks, The problem was sloved by keeping these two lines in .vimrc set backspace=2 set nocompatible Thanks once again.. -- Nageshwar M

Re: Stable Vim version 7.1 has been released

[Bram Moolenar] So how do I tell make that I want to build three targets in sequence then? For generice make, not GNU make. It was once forbidden to depend on GNU make in GNU packages. I guess the first package to blatantly break this rule has been GNU libc. So, most of our habits were

new text object feature request

I often need to replace parameter text and usually try to remember the text object that selects the inner parameter, only to come up short since that type isn't defined. It seems natural to have a parameter text object, where it would act on the text between commas or parentheses, i.e. from (, to

RE: new text object feature request

Hi Peter, It can (see below), but then again, the other text objects could be implemented as vimscript as well. Extending the existing text objects to include parameters seems like a natural fit. David nmap silent cim :call ChangeInnerParam()cr function ChangeInnerParam() call