Christian Brabandt | 24 May 22:14

[patch] v/V with a count

Bram,
attached patch fixes this issue from the todo list:

,----
| Use a count before "v" and "V" to select that many characters or lines?
| (Kikyous)
`----

regards,
Christian
-- 
Geschichte schreiben ist eine Art, sich das Vergangene vom Halse 
zu schaffen.
		-- Goethe, Maximen und Reflektionen, Nr. 251

--

-- 
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
Attachment (visual_count.diff): text/x-diff, 842 bytes
Picon

Updated fasm vim syntax file

Hello!
I've updated fasm vim syntax file to match fasm-1.70.02 (latest
stable) version syntax and support 64bit, MMX, SSE1-SSE4, AVX-AVX2
instructions.
Hope it can be useful.

Best regards,
Anton Kochkov.

--

-- 
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
Attachment (fasm.vim.gz): application/x-gzip, 4141 bytes
Dominique Pellé | 24 May 20:48
Picon

[patch] fixed clang-3.1 warnings: src/charset.c uses latin1 char in strings

Hi

Compiling Vim-7.3.524 with clang-3.1 gives these warnings:

charset.c:1607:34: warning: illegal character encoding in string
literal [-Winvalid-source-encoding]
charset.c:1608:34: warning: illegal character encoding in string
literal [-Winvalid-source-encoding]

The charset.c source file uses strings in latin1 encoding.

This seems dangerous since compilers often use utf-8 for
input source file or the locale settings according
to man gcc (see -finput-charset=...).  So I wonder how
portable it is to use latin1 strings in source files.

Attached patch fixes the warning by making charset.c
source use ASCII characters only.

Since the fix can be error prone, I verified with
"objdump -s objects/charset.o" that the generated
object files are identical before and after fix (when
stripping debug info which was different).

Regards
-- Dominque

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
(Continue reading)

Alex Efros | 24 May 12:28
Favicon
Gravatar

bug related to patch 7.3.449 (Autocommands caused command to abort)

Hi!

I've discover this bug when trying to ':wq' in file with syntax errors using
syntastic plugin with
    let g:syntastic_auto_loc_list=1
Instead of exiting from vim no matter there are syntax errors I got either
    E855: Autocommands caused command to abort
or vim segfault.

To reproduce this bug it's enough to:

    $ vi -u /dev/null --noplugin
    :autocmd BufWinLeave * if empty(&bt) | lclose | endif
    :lexpr system('echo :1:some')
    :lopen
    :wincmd p
    :q
    (location list closes; got message E855: Autocommands caused command to
    abort; vim doesn't exit)
    :q
    (now vim exit)

Or, with tabs and segfault:

    $ vi -u /dev/null --noplugin
    :autocmd BufWinLeave * if empty(&bt) | lclose | endif
    :tabnew
    :lexpr system('echo :1:some')
    :lopen
    :wincmd p
(Continue reading)

Christian Brabandt | 22 May 15:54

[patch] browsefilter for the gtk gui

Bram,
I noticed the GTK build of gvim does not make use of the browsefilter 
variables. So I threw some code at that problem ;)

Find the patch attached.

regards,
Christian
-- 

--

-- 
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
Attachment (gtk_browsefilter.diff): text/x-diff, 1484 bytes
Elias Diem | 22 May 11:06
Picon

[format patch] Unnested ifdef

Hello everybody

This is a very small patch. The preprocessor directive is 
not nested. It distracted me a little.

Greetings Elias

--

-- 
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
Attachment (vim.patch): text/x-diff, 466 bytes
vim | 20 May 22:51

Issue 64 in vim: Can't paste the <0c> character on Ex or / command line when using 'incsearch'

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 64 by dominiqu...@gmail.com: Can't paste the <0c> character on Ex  
or / command line when using 'incsearch'
http://code.google.com/p/vim/issues/detail?id=64

Description:

Vim can't paste the <0c> character (form feed) on Ex or / command line  
when 'incsearch' variable is set.

What steps will reproduce the problem?

1. start Vim with:  vim -u NONE
2. :set nocp display=uhex incsearch
3. :call feedkeys("i\<C-V>x0c\<C-V>x0c\<Esc>Y/\<C-R>\"")

The last line inserts 2 <0c> (form feed characters), yanks the line and  
appends the line in the search / line.

What is the expected output? What do you see instead?

I would expect to see at the bottom of the screen:

/<0c><0c><0d>

Instead, I only see:

(Continue reading)

Christian Brabandt | 20 May 14:45

[patch] open folds on horizontal movements

Bram,
I find it irritating, that folds open on horizontal movements depending 
on where the cursor is.

For example open fold.c, move the cursor to a closed fold, Move the 
cursor to the end of the line ('$'), now the fold opens. Close the fold 
and press 'l'. The closed fold does not open, because the cursor did not 
move.

This happens sometimes to me and I find this confusing, that 
sometimes the fold does not open and sometimes it does.

So here is a small patch, that fixes it.

diff --git a/src/normal.c b/src/normal.c
--- a/src/normal.c
+++ b/src/normal.c
@@ -6081,7 +6081,7 @@
 #endif
     }
 #ifdef FEAT_FOLDING
-    if (n != cap->count1 && (fdo_flags & FDO_HOR) && KeyTyped
+    if (n <= cap->count1 && (fdo_flags & FDO_HOR) && KeyTyped
                                               && cap->oap->op_type == OP_NOP)
        foldOpenCursor();
 #endif
@@ -6151,7 +6151,7 @@
        }
     }
 #ifdef FEAT_FOLDING
(Continue reading)

Dominique Pellé | 20 May 09:15
Picon

Added support for spell checking in runtime/syntax/{bc,cmake,expect,mmix,spice,vhdl,xpm2}.vim

Hi

Attached patches add @Spell to the the syntax files
runtime/syntax/{bc,cmake,expect,mmix,spice,vhdl,xpm2}.

I tried to contact the maintainers but their emails
bounce for all those 7 syntax files.

Regards
-- Dominique

--

-- 
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
Attachment (fix-spell-spice.vim.patch): application/octet-stream, 526 bytes
Attachment (fix-spell-mmix.vim.patch): application/octet-stream, 1105 bytes
Attachment (fix-spell-expect.vim.patch): application/octet-stream, 1032 bytes
Attachment (fix-spell-vhdl.vim.patch): application/octet-stream, 1342 bytes
Attachment (fix-spell-cmake.vim.patch): application/octet-stream, 569 bytes
Attachment (fix-spell-xpm2.vim.patch): application/octet-stream, 441 bytes
Attachment (fix-spell-bc.vim.patch): application/octet-stream, 680 bytes
Lech Lorens | 20 May 02:15
Picon

[Patch] Handle tabs in pointer lines ('errorformat')

The attached patch causes Vim to handle pointer lines which consist of
a sequence of '-', '.', ' ' or tabs (I added tab handling; the rest was
obviously there).
As a result an error report like this can be handled correctly:
#v+
"foo.c", line 234: undefined identifier "Foo"
	    for (foo = bar; Foo != NULL; ++foo)
	                    ^
#v-

I also added tests for some 'efm' features which were not tested
(virtual column, pointer lines).

Cheers,
Lech

--

-- 
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
Attachment (efm-pointer-line-tab.patch): application/octet-stream, 7899 bytes
Thilo Six | 19 May 19:54
Picon
Picon

[patch] runtime/indent/vim.vim

hello Bram,

this patch adds 'b:undo_indent' to 'runtime/indent/vim.vim'.

-- 
Regards,
Thilo

4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6  7C18 89A4 A2A0 C70B 1A8F

--

-- 
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
Attachment (vim.patch): text/x-diff, 675 bytes
Attachment (vim.vim): application/x-wine-extension-vim, 2636 bytes

Gmane