On 11/27/2010 09:49 PM, Lech Lorens wrote:
On 27-Nov-2010 H Xu wrote:
On 2010/11/27 4:34, Bram Moolenaar wrote:
Well, if you change the default for 'cinoptions', then it's not unusual
to also need to change 'cinkeys'. I don't think "break" needs to be
re-indented for the default value of 'ci
On 27-Nov-2010 H Xu wrote:
> On 2010/11/27 4:34, Bram Moolenaar wrote:
> >
> >Well, if you change the default for 'cinoptions', then it's not unusual
> >to also need to change 'cinkeys'. I don't think "break" needs to be
> >re-indented for the default value of 'cinoptions'.
>
> Hello Bram Moolen
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
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
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
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
--
You received this message from the "vim_dev"