unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: guile-devel@gnu.org
Cc: wingo@pobox.com, wjm@heenes.com
Subject: Re: enhancement requests ("load-ignoring-cached-go")
Date: Sat, 23 Apr 2011 15:17:43 -0400	[thread overview]
Message-ID: <8CDD00241393292-FC8-55BD@web-mmc-d08.sysops.aol.com> (raw)
In-Reply-To: <m3bozzg0ps.fsf@unquote.localdomain>

>
> On Thu 21 Apr 2011 12:21, Wolfgang J Moeller <wjm@heenes.com> writes:
>
> > In my browser, searching the Guile Reference Manual
> > ( http://www.gnu.org/software/guile/manual) Indices
> > for GUILE_LOAD_COMPILED_PATH ... no hits ...
>
> An open bug, yes; hrm.  Adding Mark Harig to the Cc, who had a plan 
for
> fixing this.
>

In brief, the plan was to reorganize the sections in the chapter
"Programming in Scheme" to add a new section, "Invoking Guile", with
two new subsections, "Command-line Options" and "Environment
Variables."  The subsection "Command-line Options" is a copy of the
former subsection "Invoking Guile", which resided in the section
"Guile Scripting."  The subsection "Environment Variables" is a new
node that contains descriptions of the (as yet undocumented)
environment variables that can be set before Guile is started.

Here is an outline of the change in the chapter structure:

1. Current structure:

  Chapter: Programming in Scheme
    * Guile Scheme
    * Guile Scripting
      * The Top of a Script File
      * Invoking Guile
      * The Meta Switch
      * Command Line Handling
      * Scripting Examples
    * Using Guile Interactively
    * Using Guile in Emacs

2. New structure:

  Chapter: Programming in Scheme
    * Guile Scheme
    * Invoking Guile
      * Command-line Options
      * Environment Variables
    * Guile Scripting
      * The Top of a Script File
      * The Meta Switch
      * Command Line Handling
      * Scripting Examples
    * Using Guile Interactively
    * Using Guile in Emacs

I will send the proposed patches in a separate message.



  parent reply	other threads:[~2011-04-23 19:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 11:50 enhancement requests Andy Wingo
2011-03-21  0:24 ` Wolfgang J Moeller
2011-03-21  8:23   ` Andy Wingo
2011-03-29  9:50   ` Andy Wingo
2011-03-29 14:40     ` Wolfgang J Moeller
2011-04-15  9:29   ` Andy Wingo
2011-04-18  9:53     ` Wolfgang J Moeller
2011-04-21  9:34       ` Andy Wingo
2011-04-21 10:21         ` enhancement requests ("load-ignoring-cached-go") Wolfgang J Moeller
2011-04-21 14:04           ` Andy Wingo
2011-04-21 15:56             ` Wolfgang J Moeller
2011-06-30 11:38               ` Andy Wingo
2011-04-23 19:17             ` Mark Harig [this message]
2011-03-29 10:18 ` enhancement requests Andy Wingo

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=8CDD00241393292-FC8-55BD@web-mmc-d08.sysops.aol.com \
    --to=idirectscm@aim.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    --cc=wjm@heenes.com \
    /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).