RE: How to make Ctrl-X Ctrl-F expand file names using slashes even under Windows?

Vadim Zeitlin wrote: > When a file name is completed in insert mode using Ctrl-X > Ctrl-F Win32 version of gvim helpfully "corrects" the path > separator characters to fit those used by the current > platform. So under Windows pressing Ctrl-X Ctrl-F after > typing "include/foo/" results in "includ

How to make Ctrl-X Ctrl-F expand file names using slashes even under Windows?

Hello, When a file name is completed in insert mode using Ctrl-X Ctrl-F Win32 version of gvim helpfully "corrects" the path separator characters to fit those used by the current platform. So under Windows pressing Ctrl-X Ctrl-F after typing "include/foo/" results in "include\foo\bar" which, whil

Re: Upgraded Ubuntu and perl-support.vim no longer works.

On Mon, May 4, 2009 at 3:45 PM, Bill Moseley wrote: > > Ok, perhaps getting closer.  Doesn't seem like any ftplugin/*.vim are > getting loaded. > > > When I edit a .pl file (filetype=perl) ftplugin/perl.vim doesn't seem > to be loaded.  A look at strace seems to confirm that. > > But, if I run thi

Re: Upgraded Ubuntu and perl-support.vim no longer works.

Ok, perhaps getting closer. Doesn't seem like any ftplugin/*.vim are getting loaded. When I edit a .pl file (filetype=perl) ftplugin/perl.vim doesn't seem to be loaded. A look at strace seems to confirm that. But, if I run this command: :runtime! ftplugin/**/*.vim I see this error brief

Can't :imap

Why can I do :imap   and it works fine, while :imap   seems to ignore the mapping and just inserts one space? Is a valid mapping at all? -- gvim 7.1.314 --~--~-~--~~~---~--~~ You received this message from the "vim_use" maillist. For more infor

Re: Plugin in .vimrc not available->where to set settings?

Matt Wozniski schrieb: > On Mon, May 4, 2009 at 12:51 PM, Ben Fritz wrote: > >> On May 4, 11:47 am, "Torsten A." wrote: >> >>> I checked the vim help and found the ~/.vim/after directory, which is >>> supposed to be scanned __after__ the plugins are loaded. I tried to add >>> my script se

Re: Plugin in .vimrc not available->where to set settings?

Matt Wozniski wrote: > On Mon, May 4, 2009 at 12:51 PM, Ben Fritz wrote: > >> On May 4, 11:47 am, "Torsten A." wrote: >> >>> I checked the vim help and found the ~/.vim/after directory, which is >>> supposed to be scanned __after__ the plugins are loaded. I tried to add >>> my script sett

Re: Plugin in .vimrc not available->where to set settings?

On Mon, May 4, 2009 at 12:51 PM, Ben Fritz wrote: > > On May 4, 11:47 am, "Torsten A." wrote: >> I checked the vim help and found the ~/.vim/after directory, which is >> supposed to be scanned __after__ the plugins are loaded. I tried to add >> my script setting the plugin path in the "after" dir

Re: Plugin in .vimrc not available->where to set settings?

On May 4, 11:47 am, "Torsten A." wrote: > I checked the vim help and found the ~/.vim/after directory, which is > supposed to be scanned __after__ the plugins are loaded. I tried to add > my script setting the plugin path in the "after" directory, but the > script is never executed. Currently I

Plugin in .vimrc not available->where to set settings?

Hello, I like to automatically load the project settings using the vim project plugin. As far as I know the ~/.vimrc is executed before the plugins are loaded. Therefore, I cannot set the path for the plugin using >:Project path/to/project.vim because the plugin isn't available yet. I checked

Re: Upgraded Ubuntu and perl-support.vim no longer works.

On Mon, May 04, 2009 at 05:51:00PM +1000, John Beckett wrote: > > I think your problem is using \rs which used to do one thing, > and now does another. This command may be enlightening: The plugin only works when editing Perl files -- so I opened foo.pl and made sure ":set filetype" returned "fi

Re: Toggle plugins when creating a tab

On May 3, 7:37 am, Jan Larres wrote: > and > >  :h TabEnter > If you use this event to call commands or set up options just once on creation of a tab, you will probably need to use a technique similar to this one to limit it to tab creation: http://vim.wikia.com/wiki/Detect_window_creation_wi

RE: bring two buff into diff mode

Andy Wokula wrote: >> After making some changes, you might want: >> :windo diffupdate > > Small correction: the latter :windo should be omitted: > :diffu Oooh. I have been under a misapprehension for quite some time! Thanks. John --~--~-~--~~~---~--~~ You

Re: bring two buff into diff mode

John Beckett schrieb: > Steven Woody wrote: >> Supposing I have two files opened in two separated buffers b1 >> and b2, and now I decide to compare b1 and b2 as if I open >> these file by 'vim -d f1 f2', how can vim help me accomplish >> this? Thanks. > > Usually I have exactly two windows open

Re: bring two buff into diff mode

On Mon, May 4, 2009 at 9:57 AM, John Beckett wrote: > > Steven Woody wrote: >> Supposing I have two files opened in two separated buffers b1 >> and b2, and now I decide to compare b1 and b2 as if I open >> these file by 'vim -d f1 f2', how can vim help me accomplish >> this?  Thanks. > > Usually

RE: bring two buff into diff mode

Steven Woody wrote: > Supposing I have two files opened in two separated buffers b1 > and b2, and now I decide to compare b1 and b2 as if I open > these file by 'vim -d f1 f2', how can vim help me accomplish > this? Thanks. Usually I have exactly two windows open when I want to do this, and the

RE: Upgraded Ubuntu and perl-support.vim no longer works.

Bill Moseley wrote: >> :echo g:mapleader > > That command doesn't work on any of my vim installs, even one > a machine where the perl-support is still working. That just means there is no variable called mapleader, so you have the default backslash as your key. I think your problem is using

bring two buff into diff mode

Hi, Supposing I have two files opened in two separated buffers b1 and b2, and now I decide to compare b1 and b2 as if I open these file by 'vim -d f1 f2', how can vim help me accomplish this? Thanks. -- narke ID: narkewo...@gmail.com You can send me encrypted messages using my public key: --