On 4/14/06, Ty Morrison <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Editing C code i'm seeing this problem a lot I had to stop using vim 7 for 6
> because of it.
>
> Sometimes it happens just from arrowing up sometimes it happents jumping from
> closing -> open brace.
>
> Sometimes it completely locks u
It's a useful operation to close tab by double
clicking on a tab, since there is a operation to add
new page by double clicking on nontab area on tabline.
___
雅虎1G免费邮箱百分百防垃圾信
http://cn.mail.yahoo.com/3967a3968,3981
> WNDP
On Sat, Apr 15, 2006 at 12:22:06PM +0530, Praveena M wrote:
> Hi,
>
> I am new to vim-dev.
>
> I am looking for some pointers to implement auformatting perl programs
> (similar to perltidy) using vim script.
Vim has features to adjust the indentation automatically, but not
to break up lines
On Fri, Apr 14, 2006 at 09:24:35PM -0400, Benji Fisher wrote:
> On Fri, Apr 14, 2006 at 03:11:13PM +0200, Bram Moolenaar wrote:
> >
> > Check: it doesn't matter how you started the Vim in which you do
> > ":!gvim"?
>
> Good question. This works:
>
> $ vim -u NONE
> :!gvim
>
> But guess wh
Benji Fisher wrote:
> > > The problem is neither python nor plugins. This is the default
> > > version compiled on FC2, with Normal features, -python. When I start
> > > gvim with
> > >
> > > :!gvim -u ~/.vimrc ~/.gvimrc
> > >
> > > there is no segfault and I get the same plugins as if I
C Fang wrote:
> It's a useful operation to close tab by double
> clicking on a tab, since there is a operation to add
> new page by double clicking on nontab area on tabline.
Double clicking on a tab also creates a new tab, in front of where you
clicked. This probably doesn't work for all GUIs
Benji -
> On Fri, Apr 14, 2006 at 09:24:35PM -0400, Benji Fisher wrote:
> > On Fri, Apr 14, 2006 at 03:11:13PM +0200, Bram Moolenaar wrote:
> > >
> > > Check: it doesn't matter how you started the Vim in which you do
> > > ":!gvim"?
> >
> > Good question. This works:
> >
> > $ vim -u NON
On Sat, Apr 15, 2006 at 01:48:34PM -, fangread wrote:
> Bram wrote:
> > Closing a tab cannot be undone, thus I don't think it should be done
> > too easily. It's easy to double click while you meant to click once
> > two times.
> I know the reason now.
>
> How about providing a option? It's d
In vim6, the following completion request generated flat
(nonrecursive) list, and worked quicky:
vim
:set nocp wildmenu
:e /usr/*
In vim7, the same input generates recursive filelist (which
is very slow if directory is deeply populated).
Is this intentional change ?
Yakov
On Sat, Apr 15, 2006 at 03:41:17PM +0200, Bram Moolenaar wrote:
>
> Hmm, I did fix a problem for setting $MYVIMRC: in vimrc_found() the
> "dofree" option wasn't initialized to FALSE. If this is missing in your
> source code is missing that might be the cause of the crash.
>
> The start of the vi
Yakov Lerner wrote:
> In vim6, the following completion request generated flat
> (nonrecursive) list, and worked quicky:
>
> vim
> :set nocp wildmenu
> :e /usr/*
>
> In vim7, the same input generates recursive filelist (which
> is very slow if directory is deeply populat
In the example below, the 'cabbrev ' doesn't work,
while identical cabbrev without works ok (vim70d02)
---
vim -u cab.vim# where cab.vim is below
:GG# this works, produces expected :GG *
:BB# doesn't work, does not produce :BB *
:BB
Yakov Lerner wrote:
> In the example below, the 'cabbrev ' doesn't work,
> while identical cabbrev without works ok (vim70d02)
> ---
> vim -u cab.vim# where cab.vim is below
> :GG# this works, produces expected :GG *
> :BB# doesn't
On 4/15/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> Yakov Lerner wrote:
>
> > In the example below, the 'cabbrev ' doesn't work,
> > while identical cabbrev without works ok (vim70d02)
> > ---
> > vim -u cab.vim# where cab.vim is below
> > :GG
I'm seeing a gVim 7.0d (GTK2) bug in refreshing the GUI tab bar. When
a guitablabel is set by autocmd (VimEnter, BufEnter, etc), the results
aren't actually shown until the Vim window is refreshed, such as with
:set nu or :set list.
--
Steve Hall [ digitect mindspring com ]
I was very pleased to see Taro Muraoka's functionality included for selecting quoted strings! Here's a small patch to correct the fact that these are visual mode commands as opposed to normal mode commands.
-- Adam Monsen
version7.txt.patch
Description: Binary data
Hi!
Vim choses the default colors of the syntax highlighting for gVim
depending of the value of background. If I add the lines
set background=dark
hi Normal guifg=#e0e0e0 guibg=#202020
I get the defaults for dark backgrounds. Unfortunately, the background
colors of cursorline and cursorcolum
17 matches
Mail list logo
