From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: Unclear documentation: "Options and Config", set! and enable/disable
Date: Fri, 24 Jun 2005 09:48:27 +1000 [thread overview]
Message-ID: <87y890ocs4.fsf@zip.com.au> (raw)
In-Reply-To: <42B8387C.4040903@mail.msen.com> (Alan Grover's message of "Tue, 21 Jun 2005 11:55:40 -0400")
Alan Grover <awgrover@mail.msen.com> writes:
>
> It isn't clear from the documentation how to use the "User Level Options
> Interfaces" (chapter "Configuration, Features and Runtime Options").
Alas, yes.
> Apparently, all of the <group>-set! are macros, and interpret the first
> argument as a symbol. Perhaps this was an attempt to make this interface
> appear analogous to set!, despite the option-symbols not being
> defined/bound.
An example of a macro only serving to obscure :(.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2005-06-23 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 15:55 Unclear documentation: "Options and Config", set! and enable/disable Alan Grover
2005-06-23 23:48 ` Kevin Ryde [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=87y890ocs4.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).