Printing error spans

[jmikedupont2]

Here is a patch to get better error message on the bane of lisp
https://github.com/shsms/tulisp/compare/main...meta-introspector:tulisp:enhanced-error-reporting?expand=1

4 changes: 3 additions & 1 deletion4  
[src/parse.rs](https://github.com/shsms/tulisp/compare/main...meta-introspector:tulisp:enhanced-error-reporting?expand=1#diff-5583e398a8deec11b274d9965eff8b5ade5226c7a020ca214a27d7d07dcc8a29)
Original file line number	Diff line number	Diff line change
@@ -315,7 +315,9 @@ impl Parser<'_, '_> {
        let mut got_dot = false;
        loop {
            let Some(token) = self.tokenizer.peek() else {
                return Err(Error::parsing_error("Unclosed list".to_string())
                return Err(Error::parsing_error(format!(
                    "Unclosed list - missing ')' for opening '(' at line {}, col {}"
                , start_span.start.0, start_span.start.1))
                    .with_trace(TulispObject::nil().with_span(Some(start_span))));
            };
            match token {

[shsms]

Thanks for the report! Tulisp already prints a backtrace, so it is easier for the editor to parse. The compilation mode of Emacs, for example, can recognize this and take you to the open parenthesis automatically.

The text can be improved instead of printing "nil", and I will get to that.

If you're embedding tulisp, you can print formatted error messages by calling Error::fomat, like it is done here, for example.

The project is unfortunately very poorly documented, and I'm still stabilizing the interfaces. I didn't realize there was any interest in the project, so I never prioritized it. Maybe that should change.

[jmikedupont2]

Well I'm porting Emacs to it

…

On Sat, Apr 4, 2026, 09:30 Sahas Subramanian ***@***.***> wrote: *shsms* left a comment (shsms/tulisp#104) <#104 (comment)> Thanks for the report! Tulisp already prints a backtrace, so it is easier for the editor to parse. The compilation mode of Emacs, for example, can recognize this and take you to the open parenthesis automatically. The text can be improved instead of printing "nil", and I will get to that. If you're embedding tulisp, you can print formatted error messages by calling Error::fomat <https://github.com/shsms/tulisp/blob/e5f62a6484183165f3d22873db8ef575fd36c599/src/error.rs#L112>, like it is done here <https://github.com/shsms/tulisp/blob/e5f62a6484183165f3d22873db8ef575fd36c599/src/bin/tulisp.rs#L18-L21>, for example. The project is unfortunately very poorly documented, and I'm still stabilizing the interfaces. I didn't realize there was any interest in the project, so I never prioritized it. Maybe that should change. 20260404_15h07m40s_grim.png (view on web) <https://github.com/user-attachments/assets/e7ffbb8a-dba6-4194-b619-2046d27d474f> — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5KQ2PYG2FB5FE5B34OJQ34UEFABAVCNFSM6AAAAACXMIJ5V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOBXGEZDAOJZGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[shsms]

Wow, that sounds like a big project! Tulisp was not made with that in mind, but