From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org, Fabian Schuetz <info@fms-edv.de>
Subject: Re: Segmentation Fault in guile-1.8.7 on recent Macbook Pro
Date: Thu, 18 Nov 2010 16:10:23 +0100 [thread overview]
Message-ID: <m3pqu21xcw.fsf@unquote.localdomain> (raw)
In-Reply-To: <87ocaboacn.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 30 Oct 2010 16:58:45 +0100")
On Sat 30 Oct 2010 17:58, Neil Jerram <neil@ossau.uklinux.net> writes:
> Fabian Schuetz <info@fms-edv.de> writes:
>
>> (undefine list)
>
> Unless there's a compelling need, I'm afraid it's unlikely anyone will
> work on this, because most developer focus is now on 1.9/2.0.
Indeed, `undefine' doesn't exist in 1.9/2.0.
If you still have questions, Fabian, let us know how we can help you do
what you need to do without using undefine.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-11-18 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 11:40 Segmentation Fault in guile-1.8.7 on recent Macbook Pro Fabian Schuetz
2010-10-30 15:58 ` Neil Jerram
2010-11-18 15:10 ` Andy Wingo [this message]
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=m3pqu21xcw.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=info@fms-edv.de \
--cc=neil@ossau.uklinux.net \
/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).