Bug#430205: vim: chmod foo -x; foo/bar unreadable directory causes [new file] annotation

Justin Pryzby justinpryzby at users.sourceforge.net
Sat Jun 23 11:02:00 UTC 2007


Package: vim
Version: 1:7.0-122+1etch2
Severity: minor

If vim gets a permission denied return value from a syscall trying to
open a file due to a parent directory lacking execute permission, it
should say so, not [new file] (although the file may or may not exist,
it's nicer to warn the user of this eg. in the same way it's nice to
warn when one starts to edit a readonly file).




More information about the pkg-vim-maintainers mailing list