From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org
Subject: Re: [GUILE/SCWM] Why the hook is 0x0
Date: 12 Sep 2002 23:35:35 +0200 [thread overview]
Message-ID: <87admmc2mw.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200209112255.06333.pieter.pareit@planetinternet.be>
P Pareit <pieter.pareit@planetinternet.be> writes:
> Should error_hook show up in the .x file?
Yes.
> There is mention of SCM__I in the ChangLog-2000 file, where it states that
> it's name is replaced from SCM__I to SCM_SNARF_INIT_START (same for SCM__D,
> SCM__S and SCM__E), if that is true, it would explane my problems in running
> scwm. So this could mean I best replace SCM__I, but it might even be better
> to change the macro's to guile-snarf macro's special made for the purpose
> (SCM_VARIABLE maybe?). Someone knows what I best do?
Yes, SCM_VARIABLE looks like it is the thing you need:
SCM_VARIABLE_INIT (error_hook, "error-hook", scm_make_hook (1));
You loose the docstring, unfortunately.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-09-12 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 20:55 [GUILE/SCWM] Why the hook is 0x0 P Pareit
2002-09-12 21:35 ` Marius Vollmer [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=87admmc2mw.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).