http://blog.gmane.org/gmane.editors.vim.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.editors.vim.devel/34655 <pre>Hi! Here is patch for syntastic, but it uses exact copy of Vim's /usr/share/vim/vim73/tools/efm_perl.pl, so patch will apply: https://github.com/powerman/syntastic/commit/1e99ed56b7cefde536997c037fff44be9fd26fab </pre> Alex Efros 2012-05-26T21:05:47 http://comments.gmane.org/gmane.editors.vim.devel/34653 <pre>The vim docs give me the impression that individual autocommands are executed independently. However... This sequence of autocommands: autocmd BufWritePost * if 0 | echo &lt;afile&gt; | endif autocmd BufWritePost * echo "foo" will not cause "foo" to be echoed when a buffer is written. Reversing the order of the above two autocommands will result in "foo" being echoed. The &lt;afile&gt; reference is the part of the first autocommand that must be present to cause this problem. Replacing the "if 0" with "if 1" in the above results in an error message when the autocommand is created. However, the original autocommand in which I ran accross this problem works fine with its &lt;afile&gt; reference: " Automatically set executable flag for shebang scripts on save. autocmd BufWritePost * if getline(1) =~ '^#!\(/usr\)*/bin/' | \ silent !chmod ugo+x &lt;afile&gt; | endif The executable bit is automatically set as intended for shebang files. However, when a non-shebang file is saved, then subsequently </pre> Britton Kerin 2012-05-26T19:31:23 http://comments.gmane.org/gmane.editors.vim.devel/34652 <pre>The attached patch adds the "j" flag to 'formatoptions' which is described in todo.txt as follows: 7 Add 'j' flag to 'formatoptions': Remove comment leader when joining lines. It makes it possible to perform a join on the following lines: #v+ /* * Comment */ #v- to obtain: #v+ /* Comment */ #v- It detects comments after some code, so: #v+ if (condition) /* Comment * comment. */ #v- will become: #v+ if (condition) /* Comment comment */ #v- and is intelligent enough to convert: #v+ if (condition) // comment // comment { #v- into: #v+ if (condition) // comment comment { #v- but to keep the comment leader in the following situation: #v+ if (condition) /* comment */ // comment { #v- and yield: #v+ if (condition) /* comment */ // comment { #v- I added some tests for the functionality. Cheers, Lech </pre> Lech Lorens 2012-05-26T19:15:47 http://comments.gmane.org/gmane.editors.vim.devel/34631 <pre> Patch 7.3.530 (after 7.3.520) Problem: Gvim does not work when 'guioptions' includes "f". (Davido) Solution: Call gui_mch_init_check() when running GUI in the foreground. (Yasuhiro Matsumoto) Files: src/gui.c *** ../vim-7.3.529/src/gui.c2012-05-18 17:03:13.000000000 +0200 --- src/gui.c2012-05-25 14:01:26.000000000 +0200 *************** *** 102,107 **** --- 102,111 ---- else #endif { + /* If there is 'f' in 'guioptions' and specify -g argument, + * gui_mch_init_check() was not called yet. */ + if (gui_mch_init_check() != OK) + exit(1); gui_attempt_start(); } *** ../vim-7.3.529/src/version.c2012-05-25 13:12:33.000000000 +0200 --- src/version.c2012-05-25 14:05:46.000000000 +0200 *************** *** 716,717 **** --- 716,719 ---- { /* Add new patch number below this line */ + /**/ + 530, /**/ </pre> Bram Moolenaar 2012-05-25T12:06:52 http://comments.gmane.org/gmane.editors.vim.devel/34628 <pre> Patch 7.3.529 Problem: Using a count before "v" and "V" does not work (Kikyous) Solution: Make the count select that many characters or lines. (Christian Brabandt) Files: src/normal.c *** ../vim-7.3.528/src/normal.c2012-05-25 11:04:34.000000000 +0200 --- src/normal.c2012-05-25 13:12:06.000000000 +0200 *************** *** 7660,7672 **** else /* start Visual mode */ { check_visual_highlight(); ! if (cap-&gt;count0) /* use previously selected part */ { ! if (resel_VIsual_mode == NUL) /* there is none */ ! { ! beep_flush(); ! return; ! } VIsual = curwin-&gt;w_cursor; VIsual_active = TRUE; --- 7660,7668 ---- else /* start Visual mode */ { check_visual_highlight(); ! if (cap-&gt;count0 &gt; 0 &amp;&amp; resel_VIsual_mode != NUL) { ! /* use previously selected part */ VIsual = curwin-&gt;w_cursor; VIsual_active = TRUE; *************** *** 7725,7730 **** --- 7721,7736 ---- /* start Select mode when 'selec</pre> Bram Moolenaar 2012-05-25T11:12:51 http://comments.gmane.org/gmane.editors.vim.devel/34626 <pre> Patch 7.3.528 Problem: Crash when closing last window in a tab. (Alex Efros) Solution: Use common code in close_last_window_tabpage(). (Christian Brabandt) Files: src/window.c *** ../vim-7.3.527/src/window.c2012-03-16 19:07:54.000000000 +0100 --- src/window.c2012-05-25 12:25:16.000000000 +0200 *************** *** 23,28 **** --- 23,29 ---- static void win_totop __ARGS((int size, int flags)); static void win_equal_rec __ARGS((win_T *next_curwin, int current, frame_T *topfr, int dir, int col, int row, int width, int height)); static int last_window __ARGS((void)); + static int close_last_window_tabpage __ARGS((win_T *win, int free_buf, tabpage_T *prev_curtab)); static win_T *win_free_mem __ARGS((win_T *win, int *dirp, tabpage_T *tp)); static frame_T *win_altframe __ARGS((win_T *win, tabpage_T *tp)); static tabpage_T *alt_tabpage __ARGS((void)); *************** *** 2105,2110 **** --- 2106,2147 ---- } /* + * Close the possibly last window in a tab page. + * Returns TRUE whe</pre> Bram Moolenaar 2012-05-25T10:39:38 http://comments.gmane.org/gmane.editors.vim.devel/34625 <pre> Patch 7.3.527 Problem: Clang complains about non-ASCII characters in a string. Solution: Change to \x88 form. (Dominique Pelle) Files: src/charset.c *** ../vim-7.3.526/src/charset.c2012-01-26 13:40:04.000000000 +0100 --- src/charset.c2012-05-25 11:49:58.000000000 +0200 *************** *** 1602,1611 **** #define LATIN1LOWER 'l' #define LATIN1UPPER 'U' - /* !"#$%&amp;'()*+,-./0123456789:;&lt;=&gt;?&lt; at &gt;ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]%_'abcdefghijklmnopqrstuvwxyz{|}~ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ */ static char_u latin1flags[257] = " UUUUUUUUUUUUUUUUUUUUUUUUUU llllllllllllllllllllllllll UUUUUUUUUUUUUUUUUUUUUUU UUUUUU</pre> Bram Moolenaar 2012-05-25T09:56:47 http://comments.gmane.org/gmane.editors.vim.devel/34622 <pre> Patch 7.3.526 Problem: Confusing indenting for #ifdef. Solution: Remove and add indent. (Elias Diem) Files: src/normal.c *** ../vim-7.3.525/src/normal.c2012-04-30 18:18:43.000000000 +0200 --- src/normal.c2012-05-23 20:35:13.000000000 +0200 *************** *** 29,37 **** static voidset_vcount_ca __ARGS((cmdarg_T *cap, int *set_prevcount)); #endif static int ! # ifdef __BORLANDC__ ! _RTLENTRYF ! # endif nv_compare __ARGS((const void *s1, const void *s2)); static intfind_command __ARGS((int cmdchar)); static voidop_colon __ARGS((oparg_T *oap)); --- 29,37 ---- static voidset_vcount_ca __ARGS((cmdarg_T *cap, int *set_prevcount)); #endif static int ! #ifdef __BORLANDC__ ! _RTLENTRYF ! #endif nv_compare __ARGS((const void *s1, const void *s2)); static intfind_command __ARGS((int cmdchar)); static voidop_colon __ARGS((oparg_T *oap)); *** ../vim-7.3.525/src/version.c2012-05-25 11:02:34.000000000 +0200 --- src/version.c2012-05-25 11:03:37.000000000 +0200 **********</pre> Bram Moolenaar 2012-05-25T09:04:50 http://comments.gmane.org/gmane.editors.vim.devel/34621 <pre> Patch 7.3.525 Problem: Compiler warning on 64 bit MS-Windows. Solution: Add type cast. (Mike Williams) Files: src/ex_getln.c *** ../vim-7.3.524/src/ex_getln.c2012-04-30 18:48:38.000000000 +0200 --- src/ex_getln.c2012-05-23 20:33:16.000000000 +0200 *************** *** 5263,5269 **** { static char_u compl[2] = { NUL, NUL }; char *short_names = ":=&lt; at &gt;&gt;?/"; ! int short_names_count = STRLEN(short_names); int history_name_count = sizeof(history_names) / sizeof(char *) - 1; if (idx &lt; short_names_count) --- 5263,5269 ---- { static char_u compl[2] = { NUL, NUL }; char *short_names = ":=&lt; at &gt;&gt;?/"; ! int short_names_count = (int)STRLEN(short_names); int history_name_count = sizeof(history_names) / sizeof(char *) - 1; if (idx &lt; short_names_count) *** ../vim-7.3.524/src/version.c2012-05-18 21:53:29.000000000 +0200 --- src/version.c2012-05-25 11:01:51.000000000 +0200 *************** *** 716,717 **** --- 716,719 ---- { /* Add new patch number b</pre> Bram Moolenaar 2012-05-25T09:03:01 http://comments.gmane.org/gmane.editors.vim.devel/34615 <pre>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 </pre> Christian Brabandt 2012-05-24T20:14:23 http://comments.gmane.org/gmane.editors.vim.devel/34614 <pre>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. </pre> Антон Кочков 2012-05-24T18:42:13 http://comments.gmane.org/gmane.editors.vim.devel/34613 <pre>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 </pre> Dominique Pellé 2012-05-24T18:48:24 http://comments.gmane.org/gmane.editors.vim.devel/34610 <pre>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(&amp;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(&amp;bt) | lclose | endif :tabnew :lexpr system('echo :1:some') :lopen :wincmd p :q Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault This happens on 7.3.515. Versions before 7.3.449 behave differently without tabs, but with tabs they all crash. There is probably bug in</pre> Alex Efros 2012-05-24T10:28:55 http://comments.gmane.org/gmane.editors.vim.devel/34599 <pre>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 </pre> Christian Brabandt 2012-05-22T13:54:21 http://comments.gmane.org/gmane.editors.vim.devel/34598 <pre>Hello everybody This is a very small patch. The preprocessor directive is not nested. It distracted me a little. Greetings Elias </pre> Elias Diem 2012-05-22T09:06:05 http://comments.gmane.org/gmane.editors.vim.devel/34569 <pre>Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 64 by dominiqu...&lt; at &gt;gmail.com: Can't paste the &lt;0c&gt; 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 &lt;0c&gt; 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\&lt;C-V&gt;x0c\&lt;C-V&gt;x0c\&lt;Esc&gt;Y/\&lt;C-R&gt;\"") The last line inserts 2 &lt;0c&gt; (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: /&lt;0c&gt;&lt;0c&gt;&lt;0d&gt; Instead, I only see: /&lt;0d&gt; Now if you do the same with 'noincsearch', it works as expected: 1. start Vim with: vim -u NONE 2. :set nocp display=uhex noincsearch 3. :call feedkeys("i\&lt;C-V&gt;x0c\&lt;C-V&gt;x0c\&lt;Esc&gt;Y/\&lt;C-R&gt;\"") And then I see the expected: /&lt;0c&gt;&lt;0c&gt;&lt;0d&gt; W</pre> vim< at >googlecode.com 2012-05-20T20:51:40 http://comments.gmane.org/gmane.editors.vim.devel/34561 <pre>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 &lt; at &gt;&lt; at &gt; -6081,7 +6081,7 &lt; at &gt;&lt; at &gt; #endif } #ifdef FEAT_FOLDING - if (n != cap-&gt;count1 &amp;&amp; (fdo_flags &amp; FDO_HOR) &amp;&amp; KeyTyped + if (n &lt;= cap-&gt;count1 &amp;&amp; (fdo_flags &amp; FDO_HOR) &amp;&amp; KeyTyped &amp;&amp; cap-&gt;oap-&gt;op_type == OP_NOP) foldOpenCursor(); #endif &lt; at &gt;&lt; at &gt; -6151,7 +6151,7 &lt; at &gt;&lt; at &gt; } } #ifdef FEAT_FOLDING - if (n != cap-&gt;count1 &amp;&amp; (fdo_flags &amp; FDO_HOR) &amp;&amp; KeyTyped + if (n &lt;= cap-&gt;count1 &amp;&amp; (fdo_fl</pre> Christian Brabandt 2012-05-20T12:45:08 http://comments.gmane.org/gmane.editors.vim.devel/34558 <pre>Hi Attached patches add &lt; at &gt;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 </pre> Dominique Pellé 2012-05-20T07:15:37 http://comments.gmane.org/gmane.editors.vim.devel/34554 <pre>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 </pre> Lech Lorens 2012-05-20T00:15:37 http://comments.gmane.org/gmane.editors.vim.devel/34549 <pre>hello Bram, this patch adds 'b:undo_indent' to 'runtime/indent/vim.vim'. </pre> Thilo Six 2012-05-19T17:54:40 http://comments.gmane.org/gmane.editors.vim.devel/34548 <pre>Hello Jocelyn, this patch adds 'b:undo_indent' to 'runtime/indent/eiffel.vim'. </pre> Thilo Six 2012-05-19T17:39:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.editors.vim.devel