Accessing SKILL runtime error locations outside the IDE (Vim workflow)

Hi,

If you want to enter the dark side of SKILL, you can actually redefine the errorHandler function to whatever you like.

Be careful

Aurélien 

No idea why I could not format my code properly this time...

The following defines an error handler that tries to look for the first errorful function in the stack and open its definition if you loaded your files with debugMode enabled (and keepSrcInfo is probably required as well) 

(inScheme (let ()

(defglobalfun errorHandler ( @rest errset_values
 @aux ( errport (symeval 'errport) ) ( stack_trace (get_stack_trace) )
 )
 "Custom error handler to call editor on errorful file."
 ;; This function is minimalist on purpose as we don't want to raise errors inside the error handler
 (fprintf errport "%N\n" errset_values)
 (fprintf errport "%s\n" stack_trace)
 (errset (try_to_open_editor errset_values stack_trace) t)
 );fun

(defun get_stack_trace ()
 "Return the current stack trace string."
 (let ( ( port (outstring) )
 )
 (unwindProtect
 ;; 9999 is meant to be bigger than the maximum stack size
 ;; 8 is exactly the number of levels so that the stack trace do not report the functions we are currently defining
 ;; (When modifying this code, make sure to adapt this number accordingly)
 (progn (stacktrace t 9999 8 port) (getOutstring port))
 (close port)
 );unwind
 ));let ;fun

(defun try_to_open_editor ( errset_values stack_trace )
 "Try to parse ERRSET_VALUES or STACK_TRACE to raise editor at the proper location."
 (let ( file line )
 (cond
 ;; Try to parse errset values
 ( (setq file (pcre_get_match "error while loading file - \"(.+)\"" (car (nth 4 errset_values))))
 (setq line (pcre_get_match "at line ([0-9]+)$" (car (nth 4 errset_values))))
 (open_editor file (if line (atoi line) 0))
 )
 ;; Try to find the first function whose location is stored 
 ;; Skip the first <<< Stack Trace >>> line
 ( (exists sexp_str (cdr (parseString stack_trace "\n"))
 (let ( ( sexp (linereadstring sexp_str))
 )
 (when (and (listp sexp) (listp (car sexp)))
 (destructuringBind ( _file _line ) (get_function_source (caar sexp))
 (setq line _line)
 (setq file _file)
 ));dbind ;when
 ));let ;exists
 (open_editor file (cond ( (integerp line) line ) ( (stringp line) (atoi line) ) ( t 0 )))
 )
 );cond
 ));let ;fun

(defun get_function_source ( name "s" )
 "Try to get source information of function named NAME.
This works only if function was loaded in debug mode and using `(sstatus keepSrcInfo t)`."
 (if (stringp (get name '_loadFile))
 ;; Function source is defined, use it
 (list (get name '_loadFile) (get name '_loadLine))
 ;; Try with `whereIs`, no idea if this is useful
 (letseq ( ( po_port (symeval 'poport) )
 ( tmp_port (outstring) )
 ( msg (unwindProtect
 (progn (set 'poport tmp_port) (funcall 'whereIs name) (getOutstring tmp_port))
 (progn (set 'poport po_port ) (close tmp_port))
 ) )
 )
 (list
 (pcre_get_match "is defined in file \"(.+)\"" msg)
 (pcre_get_match "at line ([0-9]+).$" msg)
 ));list ;letseq
 ));if ;defun

(defun pcre_get_match ( pattern string "tt" )
 "Safely return the first PCRE group if PATTERN matches STRING, return nil otherwise"
 (let ( ( magic (rexMagic) )
 )
 (unwindProtect
 (progn (rexMagic t) (when (pcreMatchp pattern string) (pcreSubstitute "\\1")))
 (rexMagic magic)
 )
 ));let ;def

(defun open_editor ( file line "tx" )
 "Open editor on FILE at LINE."
 ;; I do not despise `vi` users but I'm used to a better editor (which is also coded in Lisp!)
 ;; Feel free to replace it with whatever commands that will raise `vi` on the proper FILE+LINE
 (sh (lsprintf "emacsclient -n +%d '%s' &" line file))
 )

));Scheme ;closure

;*/

I was this close to sending a huge thank you, and then I saw the last comment...
In all seriousness this is wonderful, I am 100% incorporating this masterpiece into my workflow. I very much appreciate this!
Thanks, Trevor

I was this close to sending a huge thank you, and then I saw the last comment...
In all seriousness this is wonderful, I am 100% incorporating this masterpiece into my workflow. I very much appreciate this!
Thanks, Trevor