Re: strange behavior: ":w" only writes new buffers to disk, not open them.

On 2013-08-21 12:06, Christian Brabandt wrote:
> On Wed, August 21, 2013 11:26, Leonardo Barbosa wrote:
> > set cpo=n
>
> This is you error. You probably want to add the 'n' flag
> to the 'cpo' settings and not have 'cpo' only contain the 'n'.
>
> The difference is, in the former, the default flag 'F' will still
> be available, which is responsible for setting the filename of
> the current buffer to the one supplied by the :w command.
> If it isn't there (e.g. by setting cpo=n), Vim won't set the
> buffername and this is what you are currently experiencing.
>
> See also the help:
> :h cpo-F


Christian nailed the issue (including digging up which option, 'F',
was the culprit that got wiped out), however he omitted the most
important detail: how to fix it. If you got caught by this, it might
have been helpful to include the remedy, to change

set cpo=n

to

set cpo+=n

as mentioned at

:help :set+=

-tim



--
--
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 message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.