unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: bug-guile@gnu.org
Subject: Re: Missing and out-of-date information in guile.1, the Guile man page
Date: Sun, 16 Jan 2011 18:23:01 -0500	[thread overview]
Message-ID: <8CD83EB73A55053-1624-1C633@webmail-m056.sysops.aol.com> (raw)
In-Reply-To: <87d3nxgaf9.fsf@ossau.uklinux.net>

On Sat, Jan 15, 2011 at 08:48:58PM +0000, Neil Jerram wrote:
>
> > 3) Should the manual page include some information about the
> >      environment variable 'LD_LIBRARY_PATH' in the ENVIRONMENT
> >      section, or is this considered to be an O/S-dependent variable?
>
> I'd say too OS-dependent; or more to do with how guile should be
> properly installed, than how to use it once it is installed.
>
> But on the other hand, I might be misunderstanding what you had in 
mind;
> if you'd like to propose some specific text...
>

Related:

  - There is no description in the Guile manual page,
    guile.1, or the Guile Reference Manual, guile.info*, of
    the environment variable GUILE_AUTO_COMPILE.

  - The reference manual also briefly mentions the
    environment variable GUILE_HISTORY (it describes the
    default value as `.guile_history', but does not mention
    its default location, presumably $HOME, correct?), but
    the manual page does not mention it.

  - Is there an environment variable that can specify the
    name of the Guile initialization file (default: .guile)?

  - Are there any other environment variables that are not
    documented in the Guile Reference Manual?

  - For comparison, the Emacs manual includes a section
    describing the environment variables that may effect it
    when it is invoked.  See the Info node "(emacs)
    Environment" (a subsection of the appendix "Invoking
    Emacs").

--



  parent reply	other threads:[~2011-01-16 23:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:58 Missing and out-of-date information in guile.1, the Guile man page Mark Harig
2011-01-15 20:48 ` Neil Jerram
2011-01-16 19:38   ` Mark Harig
2011-01-19 19:50     ` Ken Raeburn
2011-01-20  2:31       ` Mark Harig
2011-01-24 21:07       ` Andy Wingo
2011-01-16 23:23   ` Mark Harig [this message]
2011-01-24 21:54     ` Andy Wingo
2011-01-25  7:05       ` Mark Harig
2011-03-04  9:35         ` Andy Wingo
     [not found]           ` <8CDA8E5BB95D253-584-D4A3@webmail-m087.sysops.aol.com>
2011-03-05 19:29             ` Andy Wingo
2011-01-24 21:06 ` Andy Wingo
2011-01-24 23:05   ` Mark Harig

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=8CD83EB73A55053-1624-1C633@webmail-m056.sysops.aol.com \
    --to=idirectscm@aim.com \
    --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).