On Wednesday, March 23, 2016 at 6:21:21 PM UTC-5, Manuel Ortega wrote: > > That reminds me of something else. Why isn't 'modified' set when you change > >cryptmethod or the encryption password? > > > > > > Isn't it because the *buffer* hasn't changed? IIUC, in the latter case the > *file* changes, not the buffer. In the former case neither has changed, so > for sure 'modified' should not be set. > >
If you change any of 'fileformat', 'fileencoding', 'bomb', or 'nofixeol' then the buffer doesn't change either, only the file. 'cryptmethod' is the oddball here. I view the 'modified' flag as saying "if you save this buffer then the file will change". I got caught once while I was testing something where I had the wrong password because I had quit Vim after changing the password, but I hadn't saved yet. Vim let me do that without any complaint, because the buffer wasn't modified. This might be a decent use for an OptionSet autocmd event, but that seems like a hack. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
