Re: Making vim more native-win32 friendly

2007-09-16 Fir de Conversatie Bill McCarthy
On Sun 16-Sep-07 12:48am -0600, Ed S. Peschko wrote: As for the options in question, there is a precedent - sort is implemented in vim already. I can count on one hand the programs that I regularly use inside of the buffer, and 'uniq' is one.. 'sort' ing, and then 'uniq' ing to get a count

7.1.112: warning not seen before

2007-09-16 Fir de Conversatie Tony Mechelynck
I haven't noticed the announcement on the list, but patches 7.1.111 and 7.1.112 have appeared on the FTP server. Trying to apply them and compile: [...] eval.c: In function 'eval7': eval.c:6709: warning: 'key' may be used uninitialized in this function [...] Considering all the recent patches

Re: Making vim more native-win32 friendly

2007-09-16 Fir de Conversatie Bram Moolenaar
Ed Peschko wrote: I know it's been discussed before, but how easy would it be to make: 1. uniq (and other commonly used %! commands to sort input) native to vim. Use the built-in :sort command with the u flag. 2. vim take a list of files as an input (ie: vim -l

patch 7.1.111

2007-09-16 Fir de Conversatie Bram Moolenaar
Patch 7.1.111 Problem:When using :vimgrep with the j flag folds from another buffer may be displayed. (A.Politz) Solution: When not jumping to another buffer update the folds. Files: src/quickfix.c *** ../vim-7.1.110/src/quickfix.c Thu Jun 28 21:23:52 2007 ---

patch 7.1.112

2007-09-16 Fir de Conversatie Bram Moolenaar
Patch 7.1.112 Problem:Using input() with a wrong argument may crash Vim. (A.Politz) Solution: Init the input() return value to NULL. Files: src/eval.c *** ../vim-7.1.111/src/eval.c Thu Sep 13 20:39:58 2007 --- src/eval.c Sat Sep 15 19:04:51 2007 *** *** 11565,11578

Bug in autoload handling?

2007-09-16 Fir de Conversatie Nikolai Weibull
Create autoload/bug.vim: let s:cpo_save = cpo set cpovim function bug#reproduce() echo bug#number endfunction let bug#number = 1 let s:cpo_save = cpo set cpovim Start vim and run :call bug#reproduce() which will give you the following output (instead of 1): Error detected while

Re: Bug in autoload handling?

2007-09-16 Fir de Conversatie Nikolai Weibull
On 9/16/07, Nikolai Weibull [EMAIL PROTECTED] wrote: function bug#reproduce() echo bug#number endfunction let bug#number = 1 :call bug#reproduce() which will give you the following output (instead of 1): Error detected while processing function bug#new: line1: E121: Undefined

Re: Making vim more native-win32 friendly

2007-09-16 Fir de Conversatie Bill McCarthy
On Sun 16-Sep-07 7:39am -0600, Bram Moolenaar wrote: 2. vim take a list of files as an input (ie: vim -l filelist) It's a bit more typing, but you can do it: vim '+n `=readfile(/tmp/filelist)`' Wow! I didn't know lists could be used that way. BTW, that format won't work in

[BUG] autocmd effect cancelled by :bdelete

2007-09-16 Fir de Conversatie Nikolai Weibull
% vim :new :autocmd BufWinLeave buffer=1 :2wincmd w | quit :wincmd p :q Guess what, buffer 1 is still loaded and displayed. Like, WTF? The reason I want to do this is that I have opened a window that I want to be dependent on the first window being visible. This is for doing diffs.I've

Re: Bug in autoload handling?

2007-09-16 Fir de Conversatie Bram Moolenaar
Nikolai Weibull wrote: On 9/16/07, Nikolai Weibull [EMAIL PROTECTED] wrote: function bug#reproduce() echo bug#number endfunction let bug#number = 1 :call bug#reproduce() which will give you the following output (instead of 1): Error detected while processing function

Re: Making vim more native-win32 friendly

2007-09-16 Fir de Conversatie Ed S. Peschko
On Sun, Sep 16, 2007 at 02:39:10PM +0200, Bram Moolenaar wrote: Ed Peschko wrote: I know it's been discussed before, but how easy would it be to make: 1. uniq (and other commonly used %! commands to sort input) native to vim. Use the built-in :sort command with