There one inconvenient thing in error messages: they come with line numbers
relative to the function start. This means to see the line that caused the
error you either need to use :fu or find function name in a file (and file
is only seen with :verb fu), be sure you open all folds contained in a
function and use 12j for line 12.
I suggest to add the following information to the error message: file where
function was defined and line number in this file. Proposed format:
Error detected while processing function Error
defined in /tmp/error.vim, line 3: script line 4:
line 1:
E492: Not an editor command: error
. This additional line will not be present if function was not defined in a
script and "script line 4:" part will not be present if function was
defined inside :execute.
:verbose fun should also provide this information
function Error()
Last set at line 3 from /tmp/error.vim
1 error
endfunction
This way to find where error occurred you only need to switch to the file
explicitly listed in the error message and do 4gg.
This and absence of normal names for anonymous functions inconvenience
bugged me for a long time, but while names were already altered in
extended-funcref branch this issue can be discussed here and merged into
default much earlier.
--
--
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/groups/opt_out.
