unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Dave Pawson <davep@dpawson.co.uk>
Cc: Guile User List <guile-user@gnu.org>
Subject: Re: ice-9 and $GUILE_LOAD_PATH
Date: Wed, 30 Jan 2008 21:46:21 +0000	[thread overview]
Message-ID: <87odb3uguq.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <47A031C6.2030106@dpawson.co.uk> (Dave Pawson's message of "Wed,  30 Jan 2008 08:13:58 +0000")

Dave Pawson <davep@dpawson.co.uk> writes:

> Thanks for the reply Mike.
>
> Mike Gran wrote:
>> If I recall correctly, the breakpoint library was split off into a
>> separate package.  The manual is incorrect.  This is a known bug,
>> and should be fixed in the next release.

Yes, indeed, sorry about that.  The incorrect doc was in 1.8.1 through
1.8.3, but has been removed now from 1.8.x CVS, so will no longer be
misleading people in 1.8.4.

>
>> The separate package lives here, I think.
>>
>> https://gna.org/projects/guile-debugging
>
> from which
> ; ** GDS setup
>
> ;; The first thing to do, if you haven't already, is to load the GDS
> ;; library into Emacs.  The Emacs Lisp expression for this is:
> (require 'gds)
>
> elisp?

Yes.  guile-debugging is a slight misnomer, because it actually
provides (or tries to) two overlapping things:

- Scheme-accessible breakpoints (and traps, and other bits of Scheme
  infrastructure)

- modes, keystrokes etc. for using Guile conveniently from within
  Emacs.

The two things overlap, because one of the nicest bits (IMHO :-)) is
how Emacs displays the Scheme stack when stopped at a breakpoint, and
allows easy navigation of it.

> And the documentation link http://www.ossau.uklinux.net/guile-debugging
> is 404.

I'm sorry, I've put something up now at
http://www.ossau.uklinux.net/guile-debugging that hopefully makes
sense, and links to the correct doc.

> Bug reported, but one from 2005 is still not assigned.

Thanks for raising your bug.  The others aren't assigned because I'm
(so far) the only developer, so there isn't much point.

> http://download.gna.org/guile-debugging/guile-debugging.html
> seems good though.

It has most of the right memes, but a lot of the details have moved
on.

> I'm assuming it needs to be dropped within the same 'ice-9' area
> to be picked up by the environmental variable.

guile-debugging could be installed anywhere, so long as you add the
install location to your GUILE_LOAD_PATH.  In practice, it's most
convenient to install it somewhere that's already in the standard
GUILE_LOAD_PATH, i.e. /usr/local/share/guile/site or
/usr/share/guile/site (depending on the prefix that Guile was
built).

> regards
>
> -- 
> Dave Pawson
> XSLT XSL-FO FAQ.
> http://www.dpawson.co.uk

Thanks for your interest.  Please do let me know how you find it, once
you get past these initial troubles.

Regards,
        Neil





  reply	other threads:[~2008-01-30 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 21:23 ice-9 and $GUILE_LOAD_PATH Mike Gran
2008-01-30  8:13 ` Dave Pawson
2008-01-30 21:46   ` Neil Jerram [this message]
2008-01-31  8:05     ` Dave Pawson
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 10:40 Dave Pawson
2008-01-29 11:32 ` Dave Pawson

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=87odb3uguq.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=davep@dpawson.co.uk \
    --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).