Ben Schmidt wrote:
> Tony Mechelynck wrote:
>> Ben Schmidt wrote:
>>> editing.txt is inaccurate on line 892 (a paragraph below *:w_c*):
>>>
>>> The default [range] for the ":w" command is the whole buffer (1,$). If you
>>> write the whole buffer, it is no longer considered changed. Also when you
>>> write it to a different file with ":w somefile"!
>>>
>>> The last sentence is only true if '+' is in 'cpoptions', which isn't the
>>> Vim default.
>>>
>>> Ben.
>> I think this is due to an accidental lack of update at that location in
>> that helpfile: it still describes the old behaviour from version 6. See
>> the following help snippet:
>
> Aaah. Thanks, Tony. That was vaguely what I thought, too, but I searched and
> couldn't find that snippet--was looking in the wrong places (patches mostly).
>
> Ben.
I found it by means of :helpgrep 'modified'
>
>
>
>>> INCOMPATIBLE CHANGES *incompatible-7*
>>>
>>> These changes are incompatible with previous releases. Check this list if
>>> you
>>> run into a problem when upgrading from Vim 6.x to 7.0.
>>>
>>> A ":write file" command no longer resets the 'modified' flag of the buffer,
>>> unless the '+' flag is in 'cpoptions' |cpo-+|. This was illogical, since
>>> the
>>> buffer is still modified compared to the original file. And when undoing
>>> all changes the file would actually be marked modified. It does mean that
>>> ":quit" fails now.
>> Best regards,
>> Tony.
--
The Consultant's Curse:
When the customer has beaten upon you long enough, give him
what he asks for, instead of what he needs. This is very strong
medicine, and is normally only required once.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
