Bug#796872: vim: E676 saving a buftype=nofile buffer

James McCoy jamessan at debian.org
Sat Dec 5 04:33:22 UTC 2015

On Tue, Aug 25, 2015 at 08:57:27AM +0000, Daniel Shahaf wrote:
>    * What led up to the situation?
> The following sequence of commands:
> rm foobar
> vim -i NONE -u NONE -N
> :set buftype=nofile
> :saveas foobar

Easily reproduced.  Thanks.

>    * What was the outcome of this action?
> "E676: No matching autocommands for acwrite buffer"
>    * What outcome did you expect instead?
> "E382: Cannot write, 'buftype' option is set"

Hmm.  I think :saveas should be successful here, but the 'nofile'
setting should be transfered to the alternate buffer that gets created.
“:saveas foo” should really act like a short-cut for “:w foo” and “:e
>    * Further information:
> There is no cause for an error message concerning an 'acwrite' buffer,
> since no acwrite buffer is involved.  Using ":w" at that point produces
> E382; I assume that's what the ":saveas" should result in, too.
> I am not sure whether it's simply a misphrased error messages, a wrong
> codepath being taken ('acwrite' instead of 'nofile'), or something else.
> Thanks,
> Daniel
> -- Package-specific info:
> [ I've reproduced this in sid but writing the bug report on jessie, so
> snipped the host OS information. ]

GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>

More information about the pkg-vim-maintainers mailing list