From: "Peter" <craven@gmx.net>
To: Per Bothner <per@bothner.com>, kawa@sourceware.org
Subject: Re: Environment Introspection
Date: Mon, 18 Sep 2017 05:44:00 -0000 [thread overview]
Message-ID: <87efr4a7ft.fsf@nexoid.at> (raw)
In-Reply-To: <1222b13d-969b-d59f-4808-280199b140bc@bothner.com>
Hello Per!
Thanks for the answers ;)
>> (This is for implementing a swank server for multiple Schemes,
>> to make them work with SLIME).
> I think supporting the Language Server Protocol is most promising path for
> IDE support (including on Emacs), but it's great if you can make Swank/Slime useful.
I haven't looked into it closely yet, but is there an Emacs frontend
that supports unified debugging and inspection? That's the reason I'm
interested in SLIME at all, compared to geiser. I don't just want an
interface to the existing repl, I want actual debugging, inspection and
tracing support ;) Things are working ok so far, I'll just see how far I
get ;)
Relatedly, is there any secial support in kawa for stack traces, or
would I just use normal java introspection?
Thanks for the help!
Greetings,
Peter
next prev parent reply other threads:[~2017-09-18 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 20:57 Peter
2017-09-17 23:17 ` Per Bothner
2017-09-18 5:44 ` Peter [this message]
2017-09-18 6:15 ` Per Bothner
2017-09-20 7:05 ` Helmut Eller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efr4a7ft.fsf@nexoid.at \
--to=craven@gmx.net \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).