Re: [code] [textadept] Debugging init.lua issues

From: Mitchell <m.att.foicica.com>
Date: Wed, 2 Oct 2013 10:30:10 -0400 (Eastern Daylight Time)

Hi everyone,

On Wed, 2 Oct 2013, Ryan Pusztai wrote:

> Hi All,
>
> On Wed, Oct 2, 2013 at 8:10 AM, Chris Emerson <c-ta.att.mail.nosreme.org> wrote:
>
>> Hi,
>>
>> In case it helps anyone, I debugged issues from updating to beta 4 by
>> wrapping the following around my init.lua:
>>
>> -- start of init.lua
>> local res, msg = xpcall(function()
>> --[[ rest of init.lua here ]]--
>> end, function(msg)
>> return debug.traceback(msg)
>> end)
>> if not res then
>> f = io.open("ta_error.txt", "w")
>> f:write(msg)
>> f:close()
>> end
>> -- end of init.lua
>>
>> And then if there's a problem a Lua traceback gets written to ta_error.txt
>>
>
> That is great to know.
>
> Mitchell,
>
> I think there is a serious issue with the event eating up all the source of
> the errors. Any thoughts?

In Textadept's init.lua on line 14, change

   ... ui.print(err) ...

to

   ... error(err) ...

You should get a nice message box now telling you what failed. I will
commit this later today.

Cheers,
Mitchell

-- 
You are subscribed to code.att.foicica.com.
To change subscription settings, send an e-mail to code+help.att.foicica.com.
To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
Received on Wed 02 Oct 2013 - 10:30:10 EDT

This archive was generated by hypermail 2.2.0 : Thu 03 Oct 2013 - 06:49:35 EDT