Suresh Govindachar wrote:
> The following response to
>
> :verbose set foo?
>
> "was set in error handler"
>
> is not informative. To be informative, the message
> should mention something to indicate who/what/when/where
> was trying to set the illegal value.
>
> For example, I have been using a valid statusline
> set in my vimrc for a long time. A short time ago,
> it suddenly got set to nothing. While I now know that
> the error handler set it to nothing, I have no clue
> as to who/what/when/where was trying to set it to
> a bad value!
Sorry, we only have one number per option to indicate where it was last
set. In this case there was an error while evaluating the option value,
so it got reset to avoid further errors (this may cause infinite loops:
error messages cause a scroll, screen needs to be redrawn, causes errror
messages, etc.)
You should have the error messages from when the option was reset. You
may need to set 'verbose' for that.
--
Some of the well know MS-Windows errors:
ESLEEP Operator fell asleep
ENOERR No error yet
EDOLLAR OS too expensive
EWINDOWS MS-Windows loaded, system in danger
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
