Dear vim_dev,
I think I have found a bug in BufDelete autocommand. When I delete
a buffer, load it (with the :buffer command) and then delete it again
(with :bdelete) the BufDelete autocommand group is not triggered.
I tested this with vim -u NONE --noplugin
:au BufDelete * :echom 'BufDelete'
Hi, Bram
I also confirmed. I got Hayaki's behavior.
Best, regards
--
Hirohito Higashi
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
John Little wrote:
I've just spent a few hours trying to track this down. It was very frustrating
as vim's behaviour became unpredictable, though I think I know the cause.
Using :Decho went bananas until I found the comment that explained that
DechoTabOn was necessary, but even that was
Hi Bram,
It works correctly for me, setting 'ttymouse' to sgr automatically.
Hmm, I checked this problem in Debian squeeze and OSX 10.7 environment.
My $HOME/.vimrc is here:
--
set nocompatible
set mouse=a
--
There are no statements any more.
The environment variable $TERM is xterm.
I
Am 03.12.2012 11:25, schrieb Marcin Szamotulski:
Dear vim_dev,
I think I have found a bug in BufDelete autocommand. When I delete
a buffer, load it (with the :buffer command) and then delete it again
(with :bdelete) the BufDelete autocommand group is not triggered.
I tested this with vim -u
On 19:20 Mon 03 Dec , Andy Wokula wrote:
Am 03.12.2012 11:25, schrieb Marcin Szamotulski:
Dear vim_dev,
I think I have found a bug in BufDelete autocommand. When I delete
a buffer, load it (with the :buffer command) and then delete it again
(with :bdelete) the BufDelete autocommand
Motivation:
http://stackoverflow.com/questions/13640538/vim-syntax-files-add-to-cterm
Example:
syntax region Italic start='_' end='_' modifier contains=Bold
syntax region Bold start='\*' end='\*' modifier contains=Italic
highlight Italic cterm=italic
highlight Bold
Hayaki Saito wrote:
It works correctly for me, setting 'ttymouse' to sgr automatically.
Hmm, I checked this problem in Debian squeeze and OSX 10.7 environment.
My $HOME/.vimrc is here:
--
set nocompatible
set mouse=a
--
There are no statements any more.
The environment variable
Hmm, I think combine would express better what this is doing:
combining the existing attributes with those in the current
syntax/highlight item. One can also combine a fg and bg color, but a
new fg color would overrule an existing fg color (we don't mix colors).
SGTM
We don't need the
Hi!
Is there any reason why \(\\\n\\\n\)\@=U fail to match this text:
\
\
U
while \(\\\n\\\n\)U will match it and \(\\\n\)\@=U will match it too
(without first line)?
Vim 7.3.646, Gentoo Linux amd64
--
WBR, Alex.
--
You received this message from the vim_dev
On Tue, 4 Dec 2012, Alex Efros wrote:
Hi!
Is there any reason why \(\\\n\\\n\)\@=U fail to match this text:
\
\
U
while \(\\\n\\\n\)U will match it and \(\\\n\)\@=U will match it
too (without first line)?
I suspect you're running into (from: :help /\@= ):
\@= and \@! check for matches
Hi!
On Mon, Dec 03, 2012 at 05:53:58PM -0500, Benjamin R. Haskell wrote:
Probably, as it suggests there, you could just use \zs instead:
\\\n\\\n\zsU
You right, but \zs doesn't work for me. I'm writing syntax highlight rules
for mkfile (OS Inferno/Plan9 variant of Makefile). It allow any
Updated modifier - combine
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
combine.runtime.diff
Description: Binary data
combine.src.diff
Description:
...
Rebuild Vim. Then you can run Vim with gdb with a breakpoint
when Vim gives E341:
$ cd vim/src
$ grep -n E341 *c
misc2.c:902:EMSGN(_(E341: Internal error: lalloc(%ld, )), size);
$ gdb --args ./vim -f -g
(gdb) br misc2.c:902
Breakpoint 1 at 0x4eb006: file misc2.c, line 902.
On Sunday, December 2, 2012 4:31:43 AM UTC+13, DrChip wrote:
Unfortunately, I haven't been able to duplicate this loss of buffer with
a simpler example as yet.
I can reproduce it with
vim -u NONE -N -c 'so $VIMRUNTIME/plugin/netrwPlugin.vim'
:e .
iii
Maybe your .vim/.netrwhist needs to
Just tried to apply these clean and realized that the doc patch had caught some
changes to tags. My mistake, a cleaned one is below.
Bram, do you have any preference on the name of this argument?
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the
16 matches
Mail list logo