Opening a vimball in Vim sets 'nomodifiable' not only locally but also
globally: henceforward, all new [No Name] buffers opened in the same session
will be created with 'nomodifiable' set.
Workaround: Use :set modifiable in the first [No Name] buffer created after
opening a vimball.
Fix:
A.J.Mechelynck wrote:
Opening a vimball in Vim sets 'nomodifiable' not only locally but also
globally: henceforward, all new [No Name] buffers opened in the same
session will be created with 'nomodifiable' set.
Workaround: Use :set modifiable in the first [No Name] buffer created
after
Instead of doing a boring holiday job, students can work on Vim this
summer. Google sponsors the work.
Ideas for what could be worked on can be found on the ideas page:
http://www.vim.org/soc/ideas.php
But you can also come up with your own task. Keep in mind that the
number of students that
Quoting A.J.Mechelynck [EMAIL PROTECTED]:
Opening a vimball in Vim sets 'nomodifiable' not only locally but also
globally: henceforward, all new [No Name] buffers opened in the same session
will be created with 'nomodifiable' set.
Workaround: Use :set modifiable in the first [No Name] buffer
