From: "Ricardo G. Herdt" <r.herdt@posteo.de>
To: guile-user@gnu.org
Subject: Re: Guile outside of Emacs + Geiser
Date: Wed, 27 Sep 2023 19:47:52 +0000 [thread overview]
Message-ID: <e2f067cb85f449621626097e2151f9b4@posteo.de> (raw)
In-Reply-To: <87jzsbv387.fsf@dustycloud.org>
Hi Christine,
I started writing a Guile LSP server a while ago
(https://codeberg.org/rgherdt/scheme-lsp-server). Like you said it is
incomplete, but I got following features so far:
- show signature
- show documentation
- autocompletion
- jump to definition
- show diagnostics
There is an open issue to integrate it into Guix:
https://issues.guix.gnu.org/60286
I also wrote a simple client for VS Code:
https://codeberg.org/rgherdt/vscode-scheme-lsp
This extension is focused on LSP support though, sort of a proof of
concept. Syntax highlighting, REPL support etc could be integrated with
other extensions. Or someone could implement a more involved extension
to integrate these features, like what Magic Racket seems to do.
Honestly I have mixed feelings towards LSP. It's kind of a different
mindset compared to traditional lisp editors: you get a language server
that typically analyses the project statically, providing information
regardless of the user's interaction with the REPL. My implementation
relies, at least for Guile, on Geiser, so it works by interaction with a
running Guile instance in the background. It might be enough for users
coming from other editors, but I still prefer the way Slime/Swank works,
where the REPL is the same image that provides information to the
editor.
Regards,
Ricardo
Am 27.09.2023 21:07 schrieb Christine Lemmer-Webber:
> There's a long thread on guix-devel which is related and touches on
> many
> things, but I thought I'd narrow in on this one thing.
>
> Has anyone had a "good" experience programming with Guile without using
> Emacs? If so, what was your development experience like?
>
> Furthermore, what's the right direction to making non-Emacs users have
> as nice of an experience as Emacs users do? Racket, for instance, has
> lovely support in vscode with "Magic Racket". What's the right path to
> recommend for the present, and what's the best path to improve the
> future? LSP? There are a few incomplete implementations I think but I
> haven't tried them.
>
> (Let's leave aside whether or not everyone should be using Emacs, or
> other approaches to make Emacs easier for newcomers. This thread is
> specifically about making Guile useful to people who already have a
> tool
> they like and present experiences.)
>
> - Christine
next prev parent reply other threads:[~2023-09-27 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 19:07 Guile outside of Emacs + Geiser Christine Lemmer-Webber
2023-09-27 19:47 ` Ricardo G. Herdt [this message]
2023-09-30 12:42 ` Christine Lemmer-Webber
2023-09-30 17:24 ` defn(life()) via General Guile related discussions
2023-09-27 19:48 ` Luis Felipe
2023-09-28 7:20 ` tomas
2023-09-28 12:01 ` Mike Gran
2023-09-28 12:23 ` Maxime Devos
2023-10-13 13:38 ` Simon Tournier
2023-10-16 19:41 ` Christine Lemmer-Webber
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2f067cb85f449621626097e2151f9b4@posteo.de \
--to=r.herdt@posteo.de \
--cc=guile-user@gnu.org \
/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).