unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jannneke Nieuwenhuizen <janneke@gnu.org>
To: guile-devel@gnu.org
Cc: Olivier Dion <olivier.dion@polymtl.ca>
Subject: Re: A Guile debugger workgroup?
Date: Thu, 02 Mar 2023 07:18:31 +0100	[thread overview]
Message-ID: <878rgf4qx4.fsf@gnu.org> (raw)
In-Reply-To: <87edtlptgv.fsf@laura> (Olivier Dion via's message of "Tue, 29 Nov 2022 12:21:20 -0500")

Olivier Dion via Developers list for Guile, the GNU extensibility library writes:

Hi,

> There's been a discussion on the state of debugging with Guile on the
> guix-devel mailing list.  Here's the relevant link if you want the full
> discussion:
> <https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00283.html>
> which is a reply to <https://issues.guix.gnu.org/issue/58812#id=33>.

In 2014, I wrote patches for Guile to use a debug prompt that GUD can
work with.  The Guile debug patches didn't make it into Guile, but the
Emacs GUD integration is part of Emacs.

   https://lists.gnu.org/archive/html/guile-devel/2014-08/msg00004.html

   https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00343.html

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com



  parent reply	other threads:[~2023-03-02  6:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:21 A Guile debugger workgroup? Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-11-29 17:58 ` Neil Jerram
2023-03-01 15:59   ` Maxim Cournoyer
2022-11-29 20:18 ` Damien Mattei
2023-03-02  6:18 ` Jannneke Nieuwenhuizen [this message]
2023-03-02  7:54   ` Dr. Arne Babenhauserheide
2023-03-03 10:28     ` Janneke Nieuwenhuizen
2023-03-03 10:30       ` Jan Nieuwenhuizen

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=878rgf4qx4.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).