unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: `guile-debugging' feature requests
Date: Mon, 19 Jun 2006 09:58:15 +0200	[thread overview]
Message-ID: <873be1o9uw.fsf@laas.fr> (raw)

Hi,

I only started using Neil's `guile-debugging' very recently, and so far
mostly for incremental development from Emacs rather than debugging.
BTW, I find `gds-tutorial.txt' a very nice way to get started and also
to get impressed by the new features.  I think this will have to be
integrated too.

So, below are a couple of feature requests wrt. incremental development
from within Emacs.


* Completion

Currently, `gds-complete-symbol' only completes symbols based on those
defined in the current module of the attached Guile process.  This is
fine, but it would be nice if a completion function compatible with
`hippie-expand' was provided, so that one can plug it in the middle of
other completion functions.


* Module Unloading/Reloading

When one is writing code and periodically testing it via GDS, it may
sometimes be useful to tell GDS to entirely unload/reload a given
module.  This would be particularly helpful when testing features that
span several modules.  I don't know exactly what would be feasible in
this area, and this would certainly require support from Guile itself.

Also, I don't know what other Scheme/Lisp development environments allow
for in this respect.  Does that sound like a useful usage pattern?


Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2006-06-19  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:58 Ludovic Courtès [this message]
2006-06-23 13:31 ` `guile-debugging' feature requests Neil Jerram
2006-06-26 12:19   ` Ludovic Courtès
2006-09-04  7:01     ` Neil Jerram

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=873be1o9uw.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    /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).