On Oct 19, 12:25 pm, James Vega <james...@jamessan.com> wrote: > On Wed, Oct 19, 2011 at 07:56:14AM -0700, Ben Fritz wrote: > > > So maybe, certain options should not be settable via setscript? > > 'encoding' certainly. > > I lobbied a while back[0] to not allow setting of 'encoding' at all by > the user. All they should really care about is 'fenc' and 'tenc'. If I > remember right, the problem with always using an encoding of Unicode for > 'encoding' was due to supporting 16-bit platforms. > > [0]:http://article.gmane.org/gmane.editors.vim.devel/22998
Not really related to "problem options" in terms of sourcing scripts, but I noticed a very intriguing idea mentioned only in passing, in the thread above about not allowing user edits of 'encoding'. What if :lockvar also supported options? Or even (probably with a different command) mappings? A user or script could manually unlock and change 'encoding' or other problematic options if desired; Vim could automatically lock problem options as part of init, with the assumption that this manual intermediate step would weed out most of those who just don't know what they're doing, leaving only those who (a) understand the risks or (b) are the type of person who ignore the big safety warning stickers on everything anyway (and therefore don't have much recourse when they shoot themselves in the foot, either figuratively or literally). -- 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
