I'd also like this same feature when it comes to debugging:
e.g.
function Rename..SNR1_DoArea..S_Rename..SNR1_AnalyzeLine
line 17: ...
is less easy to read than (e.g.)
function Rename..SNR1_DoArea..S_Rename..SNR1_AnalyzeLine
line 173 (AnalyzeLine 17): ...
--
--
You received this
On Friday, September 27, 2013 12:21:49 PM UTC+4, Axel Bender wrote:
I'd also like this same feature when it comes to debugging:
e.g.
function Rename..SNR1_DoArea..S_Rename..SNR1_AnalyzeLine
line 17: ...
is less easy to read than (e.g.)
function
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
On 26 September 2013, Nikolay Pavlov zyx@gmail.com wrote:
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
On Sep 27, 2013 12:29 AM, LCD 47 lcd...@gmail.com wrote:
On 26 September 2013, Nikolay Pavlov zyx@gmail.com wrote:
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
