From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org
Subject: Re: Missing and out-of-date information in guile.1, the Guile man page
Date: Mon, 24 Jan 2011 22:54:56 +0100 [thread overview]
Message-ID: <m3bp36ezm7.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CD83EB73A55053-1624-1C633@webmail-m056.sysops.aol.com> (Mark Harig's message of "Sun, 16 Jan 2011 18:23:01 -0500")
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Hi Mark,
I updated the man page. I don't really know groff though, so please reply
with comments (text appended).
On Mon 17 Jan 2011 00:23, Mark Harig <idirectscm@aim.com> writes:
> - 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.
I think that's OK to not have it in the man page, though it should be in
the manual.
> - 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.
Yes, it does put it in $HOME, though argually it should go in .local or
.cache or something.
I'm also OK with the man page not mentioning this, FWIW.
> - Is there an environment variable that can specify the
> name of the Guile initialization file (default: .guile)?
Nope. You can use -q and -l though.
> - Are there any other environment variables that are not
> documented in the Guile Reference Manual?
Yes. Would you like to submit a patch documenting them? Feel free to
ask on the list about what they mean, if the meanings are not clear :)
> - 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").
Would be good to add to Guile as well.
Cheers,
Andy
[-- Attachment #2: guile.1 --]
[-- Type: application/x-troff-man, Size: 5408 bytes --]
next prev parent reply other threads:[~2011-01-24 21:54 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
2011-01-24 21:54 ` Andy Wingo [this message]
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=m3bp36ezm7.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=idirectscm@aim.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).