unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: guile-user@gnu.org,
	"alex sassmannshausen" <alex.sassmannshausen@gmail.com>,
	"Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: r.herdt@posteo.de, guile-user <guile-user@gnu.org>
Subject: Re: LSP Server for Scheme (and more ...)
Date: Sat, 11 Jun 2022 07:58:18 +0200	[thread overview]
Message-ID: <E1D0BC37-7FCB-4371-AFC7-F6ECC62D8D58@korwin-zmijowski.fr> (raw)
In-Reply-To: <CAKdwf2CeNgKUKapSkEBmLFEf4aMAvrMoVWTDz_eV0LgGx57RsA@mail.gmail.com>

+1 haha

Le 11 juin 2022 07:21:11 GMT+02:00, alex sassmannshausen <alex.sassmannshausen@gmail.com> a écrit :
>+1
>
>On Sat, 11 Jun 2022, 04:07 Aleix Conchillo Flaqué, <aconchillo@gmail.com>
>wrote:
>
>> Yes!!! This is amazing and things like this can expose Guile to many more
>> people. Even though I've been using Emacs for many years, I believe it's
>> not great for newcomers to hear "if you want a good Guile environment you
>> can only use Emacs".
>>
>> Congratulations again, this was such an important missing piece!
>>
>> Best,
>>
>> Aleix
>>
>> On Fri, Jun 10, 2022 at 3:05 PM <r.herdt@posteo.de> wrote:
>>
>> > Hi Guilers!
>> >
>> > I want to share a couple of things I have being working on that you may
>> > find useful.
>> >
>> > 1) I developed an LSP Server for Scheme. For those that don't know the
>> > Language Server Protocol (LSP), it is meant for adding programming
>> > language support for IDEs and editors that implement the protocol
>> > (nowadays most of them support it).
>> >
>> > For now I am focusing on Guile 3 and CHICKEN 5. The idea is to write as
>> > much R7RS for common code as possible (like representing documents,
>> > fetching word under cursor etc.) and leave implementation specific code
>> > to dedicated files. So far I managed to implement auto-completion, fetch
>> > signature, fetch documentation and jump to definition.
>> >
>> > Repo: https://codeberg.org/rgherdt/scheme-lsp-server
>> >
>> > 2) An LSP server without a client is quite useless, so I'm also sharing
>> > an emacs-lsp client:
>> >
>> > Repo: https://codeberg.org/rgherdt/emacs-lsp-scheme
>> >
>> > I will create a PR to melpa for this. Until it is merged, you can clone
>> > the repo somewhere, 'load' it and follow the instructions in the README
>> > to activate it.
>> >
>> > Usage is based on interaction with the REPL, which is based on Emacs's
>> > built-in scheme inferior-mode. So you have to load the file (say by
>> > typing C-c C-l on a buffer) in order to get access to symbols imported
>> > from other modules.
>> >
>> > Note: for daily use you probably should stick to Geiser, since its Guile
>> > support is obviously much more mature. It can still become useful for
>> > other Schemes though, and is a good way to develop the LSP server
>> > without leaving Emacs ;)
>> >
>> > 3) The whole idea behind LSP is to improve language support across
>> > multiple IDEs/editors. So I started a proof of concept in VS Code:
>> >
>> > https://codeberg.org/rgherdt/vscode-scheme-lsp
>> >
>> > Since I don't use VS Code, I don't expect spending much time on it. I
>> > also don't know how a lispy LSP client should/could look like in VS
>> > Code. If you have ideas, or want to contribute/take over this, feel free
>> > to contact me. It is not documented nor published yet, but already works
>> > for the functionality mentioned (there are a couple of command to launch
>> > a REPL and load files on it). I will investigate how to automate
>> > installation of the LSP server before publishing it and let you know.
>> >
>> > Everything is on an early stage of development, and APIs may change. I
>> > tested it using following software:
>> > - Guile 3.0.8
>> > - Emacs 27.1 and 28.1
>> > - Debian Bullseye and Ubuntu 18.04
>> >
>> > Any questions, suggestions, critics and contributions are more than
>> > welcome. We can also reach me on @libera's #guile, #chicken, #scheme
>> > channels by the name rgherdt.
>> >
>> > Have a nice weekend you all!
>> >
>> > Ricardo
>> >
>> >
>> >
>>


  reply	other threads:[~2022-06-11  5:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 22:05 LSP Server for Scheme (and more ...) r.herdt
2022-06-11  2:07 ` Aleix Conchillo Flaqué
2022-06-11  5:21   ` alex sassmannshausen
2022-06-11  5:58     ` Jérémy Korwin-Zmijowski [this message]
2022-06-11  7:27   ` Ricardo G. Herdt
2023-09-27 19:27     ` Christine Lemmer-Webber
2022-06-11 13:21   ` Luis Felipe
2022-06-11 16:48     ` Ricardo G. Herdt
2022-06-11  8:37 ` James Crake-Merani
2022-06-12  2:37 ` Nala Ginrut
2022-06-16 20:12 ` (
2022-06-17  6:42   ` r.herdt

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=E1D0BC37-7FCB-4371-AFC7-F6ECC62D8D58@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=aconchillo@gmail.com \
    --cc=alex.sassmannshausen@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=r.herdt@posteo.de \
    /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).