From: Neil Jerram <neil@ossau.uklinux.net>
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: Sat, 15 Jan 2011 20:48:58 +0000 [thread overview]
Message-ID: <87d3nxgaf9.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <8CD818429F4EFE0-D0C-28BFF@Webmail-m115.sysops.aol.com> (Mark Harig's message of "Thu, 13 Jan 2011 16:58:36 -0500")
Mark Harig <idirectscm@aim.com> writes:
> Looking at the latest revision pulled from the git repository:
>
> 1) The manual page does not document the '-q' command-line option.
>
> 2) The manual page includes the text:
>
> "There is also a tutorial (info guile-tut) available."
>
> It appears that the Guile tutorial is no longer available as a
> separate Info manual, so this text should be deleted.
Thanks, I'll fix these.
> 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...
Thanks,
Neil
next prev parent reply other threads:[~2011-01-15 20:48 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 [this message]
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
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=87d3nxgaf9.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).