[PATCH] Make 'lispwords' a global-local option

2014-02-16 Fir de Conversatie guns
Hello, Currently the 'lispwords' setting is global, yet three filetypes attempt to change it on filetype/indent load: scheme, clojure, and art. Scheme and Clojure, in particular, are two very different Lisp variants, but both modify 'lispwords' to influence their indenting. Both filetypes also

Re: [Patch] Add option to disable insert completion message in shortmess

2014-02-16 Fir de Conversatie Holger Rapp
+1 - this would be really useful to have. On Wednesday, February 12, 2014 10:43:22 PM UTC+1, Tyler Brock wrote: BUMP! This would be great to have for you complete me. On Saturday, January 11, 2014 11:00:55 AM UTC-5, Shougo wrote: 2014年1月12日日曜日 0時25分42秒 UTC+9 mattn: Thank

Re: [PATCH] Make 'lispwords' a global-local option

2014-02-16 Fir de Conversatie Bram Moolenaar
Sung Pae wrote: Currently the 'lispwords' setting is global, yet three filetypes attempt to change it on filetype/indent load: scheme, clojure, and art. Scheme and Clojure, in particular, are two very different Lisp variants, but both modify 'lispwords' to influence their indenting. Both

Re: [patch] fixed compilation warnings with clang in vim tiny

2014-02-16 Fir de Conversatie Bram Moolenaar
Dominique wrote: Attached patch fixes the following compilation warnings with clang-3.5 (trunk in svn) when compiling vim tiny 7.4.183: ex_cmds.c:4102:14: warning: variable 'bigness' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] else if

Re: website / wikis - important links / proposal

2014-02-16 Fir de Conversatie Marc Weber
To sum up: - some content is outdated - the community is changing (eg people look more and more on github or somewhere eles) - community is providing content (eg regular tips) which is not yet visible on vim.sf.net which will make it more likely that the project dies again (sooner). That's

BufWinEnter triggered too early with -q

2014-02-16 Fir de Conversatie Gary Johnson
I have a plugin that needs to track the line number of the cursor in order to display some information in the status line. The CursorHold event works fine for this except when a buffer is first opened, as when opening a quickfix error file with -q. I thought that I could use the BufWinEnter

-q option generates error message twice

2014-02-16 Fir de Conversatie Gary Johnson
I created a quickfix error file containing one error and opened it like this: $ vim -N -u NONE -i NONE -q make.out At the bottom of the screen I see the message: (3 of 3): warning: incompatible imlicit declaration of built-in function 'exit' So far, so good. But if I look at all