Re: [BUG] vimball changes global 'modifiable' setting

2007-03-17 Thread drchip
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 Na

Re: [BUG] vimball changes global 'modifiable' setting

2007-03-17 Thread A.J.Mechelynck
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 open

[BUG] vimball changes global 'modifiable' setting

2007-03-17 Thread A.J.Mechelynck
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: S