> It doesn't say why though, and the reason IIUC is that vi did it that way,
> and it's such a basic command that millions are used to it. IMO we'd be
> better off with consistency, c{motion} is like d{motion} then enter insert
> mode, without this special case, but after 40 years...
>
>
On Friday, February 12, 2016 at 1:53:00 AM UTC+13, Erik Christiansen wrote:
> But ":h cw" opens with a defence of this "Special case: ...change-word".
It doesn't say why though, and the reason IIUC is that vi did it that way, and
it's such a basic command that millions are used to it. IMO we'd
> As pointed out once or twice upthread, please read ":h cw", in particular
> the last paragraph. For those who can see, it is there.
>
> Erik
Shouldn't an editor startup with the most consistent settings by default?
Elmar
--
--
You received this message from the "vim_use" maillist.
Do not
On 12.02.16 03:02, Elmar Hinz wrote:
>
> > It doesn't say why though, and the reason IIUC is that vi did it
> > that way, and it's such a basic command that millions are used to
> > it. IMO we'd be better off with consistency, c{motion} is like
> > d{motion} then enter insert mode, without this
On 11.02.16 03:43, 'Elmar Hinz' via vim_use wrote:
> the normal behaviour of the w motion is to move n words forward and to act
> exclusively.
Yes, the motion is (mostly) to the start of the next/nth word. (exclusive)
> Different from this the normal behaviour of cw is to change to the end
> of
> The w motion is then perfectly as specified, and as expected.
> It is particularly handy when correcting indentation of a few
> lines to align with a leading line of arbitrary indentation:
>
> 1) Move to start of leading line, with ^.
> 2) j
> 3) dw
> 4) Loop to 2 until done, using '.'
>
> (I start vim as "vim -u NONE" to exclude influences of personal settings.
> Right?)
>
I just detected that "vim -u NONE" brought mit into vi "compatible" setting. So
all I observed here is rather vi behaviour.
It's already improved with "nocompatible". It doesn't exactly work as I
Hi,
'Elmar Hinz' via vim_use schrieb am 11.02.2016 um 15:00:
> On Thursday, February 11, 2016 at 2:41:42 PM UTC+1, Elmar Hinz wrote:
>
>> How do I get my personal settings out of the way, without falling into vi
>> compatible?
>>
>>
>
> vim -u NONE -C
>
I think you meant
vim -u NONE -N
> I think you meant
>
> vim -u NONE -N
>
You think right again. :)
Elmar
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this
On 11.02.16 05:06, Elmar Hinz wrote:
> > The w motion is then perfectly as specified, and as expected.
> > It is particularly handy when correcting indentation of a few
> > lines to align with a leading line of arbitrary indentation:
> >
> > 1) Move to start of leading line, with ^.
> > 2) j
On Thursday, February 11, 2016 at 2:41:42 PM UTC+1, Elmar Hinz wrote:
> >
> > (I start vim as "vim -u NONE" to exclude influences of personal settings.
> > Right?)
> >
> How do I get my personal settings out of the way, without falling into vi
> compatible?
>
>
vim -u NONE -C
--
--
You
Hello,
the normal behaviour of the w motion is to move n words forward and to act
exclusively.
Different from this the normal behaviour of cw is to change to the end of the
current word, much like ce.
But what happens when hitting cw on whitespace between words?
(I start vim as "vim -u NONE"
12 matches
Mail list logo
