From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: guile-user@gnu.org,Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: Geiser vs. guile-mode?
Date: Tue, 04 Feb 2020 17:16:30 +0100 [thread overview]
Message-ID: <897B58B1-A727-4224-938E-5F7D826DA963@korwin-zmijowski.fr> (raw)
In-Reply-To: <87eevamlds.fsf@ambrevar.xyz>
Hi Pierre !
In my position I am actually writing an emacs-guile.el to address some of your points. With the knowledge I have as a beginner with emacs and guile haha.
I want it to be guile-dev-centric, easy to share and to extend. With an attention not to overtool the user.
Jérémy
Le 4 février 2020 16:18:23 GMT+01:00, Pierre Neidhardt <mail@ambrevar.xyz> a écrit :
>Hi!
>
>At the Guix days a little while back we had a session about the tooling
>to hack
>Guile code.
>
>In particular, Geiser seemed to unanimously cause issues:
>
>- How do we insert breakpoints?
>- How do we inspect compound objects? (e.g. SLIME / CIDER style)
>- How do we use the stepper (for debugging)?
>- Documentation lookup does not work.
>
>The last issue has been reported a long time ago and still hasn't been
>fixed upstream:
>
> https://gitlab.com/jaor/geiser/issues/252
>
>I find the situation a hindrance to Guile development.
>I suppose the Guile Studio is also concerned by this.
>
>What do you people suggest?
>
>I know that the Racket community decided to follow its own route with
>racket-mode. So what about a Guile-mode that's well tailored to Guile
>development?
>
>--
>Pierre Neidhardt
>https://ambrevar.xyz/
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
next prev parent reply other threads:[~2020-02-04 16:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:18 Geiser vs. guile-mode? Pierre Neidhardt
2020-02-04 16:16 ` Jérémy Korwin-Zmijowski [this message]
2020-02-04 16:40 ` Pierre Neidhardt
2020-02-07 13:50 ` Pierre Neidhardt
2020-02-07 16:19 ` Jérémy Korwin-Zmijowski
2020-02-07 16:30 ` Matt Wette
2020-02-07 17:50 ` sirgazil
2020-02-07 22:24 ` Matt Wette
2020-02-08 18:14 ` Ricardo Wurmus
2020-02-08 18:59 ` Matt Wette
[not found] ` <F5513F8F-F6A8-4AAC-8AF3-C91991CE8E40@korwin-zmijowski.fr>
2020-02-13 9:38 ` Jérémy Korwin-Zmijowski
2020-02-18 23:53 ` sirgazil
2020-02-19 14:16 ` Ricardo Wurmus
2020-02-20 14:24 ` sirgazil
2020-02-20 22:50 ` Jose A. Ortega Ruiz
2020-02-21 0:01 ` sirgazil
2020-02-21 1:44 ` Jose A. Ortega Ruiz
2020-02-21 8:41 ` Arne Babenhauserheide
2020-02-21 22:57 ` Jose A. Ortega Ruiz
2020-02-08 16:30 ` Pierre Neidhardt
2020-02-07 23:44 ` Jose A. Ortega Ruiz
2020-02-14 8:38 ` Pierre Neidhardt
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=897B58B1-A727-4224-938E-5F7D826DA963@korwin-zmijowski.fr \
--to=jeremy@korwin-zmijowski.fr \
--cc=guile-user@gnu.org \
--cc=mail@ambrevar.xyz \
/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).