Bug#796872: vim: E676 saving a buftype=nofile buffer
Daniel Shahaf
danielsh at apache.org
Tue Aug 25 08:57:27 UTC 2015
Package: vim-nox
Version: 2:7.4.826-1
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
The following sequence of commands:
rm foobar
vim -i NONE -u NONE -N
:set buftype=nofile
:saveas foobar
* 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"
* 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. ]
More information about the pkg-vim-maintainers
mailing list