stack trace issues

4 views
Skip to first unread message

Ernie Rael

unread,
Feb 27, 2023, 9:10:54 PM2/27/23
to vim...@googlegroups.com
Hi all,

I've got logging stuff, vim9script, that creates a stacktrace:

    splicelib/init.vim::Process_result[1]
    splice9Dev#splicelib#init#Init[1]
    splice9Dev/splice.vim::SpliceInit9[10]
    function splice9Dev/splice.vim::Trampoline[6]

I've discovered another twist, after <SNR>, that some frames use "#" as
separator.

If I see a name with a "#", split on "#", use last component as function
and append ".vim" to the second to the last. May not be perfect (e.g. no
requirement for ".vim" extension) but should be good enough.

Comments? or any other gotchas I should be aware of?

BTW, what's the significance of the "#"?

-ernie

Reply all
Reply to author
Forward
0 new messages