unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <sirgazil@zoho.com>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>, guile-user@gnu.org
Subject: Re: Guile outside of Emacs + Geiser
Date: Wed, 27 Sep 2023 19:48:19 +0000	[thread overview]
Message-ID: <050cd74e-8945-7d16-7ccd-7c083ec70b26@zoho.com> (raw)
In-Reply-To: <87jzsbv387.fsf@dustycloud.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1439 bytes --]

Hi,

El 27/09/23 a las 19:07, Christine Lemmer-Webber escribió:
> 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?

I have tried several editors and IDEs, and you're pretty much left on 
your own, typing characters. The only assistance I've found is syntax 
highlighting and closing parenthesis automatically. Besides those, the 
minimum features I'd expect to feel comfortable editing scheme are 
structural editing (like Emacs paredit) and something like rainbow 
delimiters. These tools alone make any worries about parenthesis go away 
(at least in my case).

But I've always wanted the same level of assistance I find for Python.


> 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.
Personally, I'm hoping projects like 
https://codeberg.org/rgherdt/scheme-lsp-server will make it easier to 
improve the experience outside Emacs (and maybe inside too).

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  parent reply	other threads:[~2023-09-27 19:48 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
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 [this message]
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=050cd74e-8945-7d16-7ccd-7c083ec70b26@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=cwebber@dustycloud.org \
    --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).