Ben Fritz wrote:
On May 20, 9:36 pm, Steven Mueller <diffu...@ugcs.caltech.edu> wrote:
Hi Chip,
I've been enjoying flying around a large source tree using netrw, but
have discovered that when opening read-only files from the local
browse mechanism, setlocal noro is done on the new buffer anyway.
This problem was also encountered in this thread on vim_use:
http://groups.google.com/group/vim_use/browse_thread/thread/82946ab8ac7e1c62/f4f6021bca21127b
Responding there might be nice when the fix is incorporated.
I don't see where netrw use is mentioned; no browsing, "I opened a
directory, and...", etc, in that thread. The problem addressed by SM
essentially meant that no warning was issued by vim when one modified a
read-only file when it should be; its not marking the buffer as "nomod"
(which is what the autocmd mentioned in that thread does, but only when
the file is readonly, so the netrw problem would prevent that autocmd
from firing, too).
Regards,
Chip Campbell
--
You received this message from the "vim_dev" 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
