Re: Is it better to add "0break" to cinkeys by default?

2010-11-26 Thread H Xu
On 11/26/2010 03:37 PM, H Xu wrote: Hello, When I add "b1" to cinoptions, vim doesn't indent current line when I type "break" by default. This is inappropriate, I think. So I recommend to change the default value of cinkeys by adding "0break". What do you think? Hong Xu 2010/11/26 Hello, S

Re: Is it better to add "0break" to cinkeys by default?

2010-11-26 Thread Bram Moolenaar
Hong Xu wrote: > On 11/26/2010 03:37 PM, H Xu wrote: > > Hello, > > > > When I add "b1" to cinoptions, vim doesn't indent current line when I > > type "break" by default. This is inappropriate, I think. So I > > recommend to change the default value of cinkeys by adding "0break". > > What do you

Re: Where do I send patches? (Mac OS X 10.6 gtk2 fork error)

2010-11-26 Thread Bram Moolenaar
Hisashi T Fujinaka wrote: > I think this worked for me, because there's something odd in 10.6 where > gvim crashes. The crash log says > > Application Specific Information: > abort() called > USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER > > Anything that uses CoreFoundation isn't su

Re: Where do I send patches? (Mac OS X 10.6 gtk2 fork error)

2010-11-26 Thread Hisashi T Fujinaka
On Fri, 26 Nov 2010, Bram Moolenaar wrote: Hisashi T Fujinaka wrote: I think this worked for me, because there's something odd in 10.6 where gvim crashes. The crash log says Application Specific Information: abort() called USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER Anything th

Re: Is it better to add "0break" to cinkeys by default?

2010-11-26 Thread H Xu
On 2010/11/27 4:34, Bram Moolenaar wrote: Hong Xu wrote: On 11/26/2010 03:37 PM, H Xu wrote: Hello, When I add "b1" to cinoptions, vim doesn't indent current line when I type "break" by default. This is inappropriate, I think. So I recommend to change the default value of cinkeys by adding