David Barnett wrote:
I discovered a bug in try..catch. E117 bypasses the catch and always
bubbles up to the user if it comes from a :return command in code like the
following:
function E_117_Bad() abort
try
return foo#Bar()
catch /.*/
endtry
endfunction
but not if the
I discovered a bug in try..catch. E117 bypasses the catch and always
bubbles up to the user if it comes from a :return command in code like the
following:
function E_117_Bad() abort
try
return foo#Bar()
catch /.*/
endtry
endfunction
but not if the exception comes from any other command
On Nov 19, 2013, at 9:59 PM, David Barnett daviebd...@gmail.com wrote:
I discovered a bug in try..catch. E117 bypasses the catch and always bubbles
up to the user if it comes from a :return command in code like the following:
function E_117_Bad() abort
try
return foo#Bar()
catch
On Tue, Nov 19, 2013 at 8:13 PM, Benjamin Klein b...@silver-chalice.comwrote:
This may be irrelevant but as it isn’t defined here: What is foo#Bar()?
Heh, that's exactly the point. E117 is Unknown function (sorry, should
have mentioned that). foo#Bar() was my dummy undefined function.
David
On Nov 19, 2013, at 10:17 PM, David Barnett daviebd...@gmail.com wrote:
Heh, that's exactly the point. E117 is Unknown function (sorry, should have
mentioned that). foo#Bar() was my dummy undefined function.
Oops -- sorry. That was dumb of me to not notice, but then again I’m on my
phone and
On Nov 20, 2013 8:17 AM, David Barnett daviebd...@gmail.com wrote:
On Tue, Nov 19, 2013 at 8:13 PM, Benjamin Klein b...@silver-chalice.com
wrote:
This may be irrelevant but as it isn’t defined here: What is foo#Bar()?
Heh, that's exactly the point. E117 is Unknown function (sorry, should
Yep, sorry, I should have used
return xxx_unknown_function_xxx()
in my example for clarity, but I didn't think of that until after the fact.
Anyway, I think this is a bug in vim. Also forgot to mention I checked the
latest version of vim available, 7.4.94, and the bug still hasn't been
fixed.
