unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: wingo@pobox.com
Cc: bug-guile@gnu.org
Subject: Re: Missing and out-of-date information in guile.1, the Guile man page
Date: Tue, 25 Jan 2011 02:05:42 -0500	[thread overview]
Message-ID: <8CD8A7569CE9F1A-10BC-A716@webmail-d094.sysops.aol.com> (raw)
In-Reply-To: <m3bp36ezm7.fsf@unquote.localdomain>

[-- Attachment #1: Type: text/plain, Size: 3066 bytes --]

On Mon, Jan 24, 2011 at 10:54:56PM +0100, Andy Wingo wrote:
>
> I updated the man page.  I don't really know groff though, so please 
reply
> with comments (text appended).
>

Thank you for the updated version.

I have written a patch to this updated version.  Please find
it attached.  It includes the following:

1. I added the current month and year, Guile version
descriptive text, and the text GNU to the title.  This
matches what is found in other GNU programs, for example,
Emacs and coreutils.  The new text appears in at the top and
the bottom (final line) of the manual page.  This should be
useful for other people when they check the manual page to
know when it was written and for what version of Guile.

2. I followed the formatting that 'man' describes for the
synopsis, namely:

       bold text          type exactly as shown.
       italic text        replace with appropriate argument.
       [-abc]             any or all arguments within [ ] are optional.
        -a|-b              options delimited by | cannot be used 
together.
       argument ...       argument is repeatable.
       [expression] ...   entire expression within [ ] is repeatable.

The options are now in bold text and their arguments are in
italic, which will appear as underlining for those
environments that don't have italics.  So, for example,

   -L [DIRECTORY]

has '-L' in bold, the brackets in normal font, and DIRECTORY
in italic (or underlined) text.  This helps to make it clear
which text is fixed and which needs to be entered by the
user.  Previously, all text was bold.

3. I made similar changes in formatting in the OPTIONS
section so that the reader can easily see which text needs
to be typed exactly and which is user-defined.

4. I corrected grammar, spelling, and capitalization (for
example, 'scheme' to 'Scheme').

5. Vertical white-space was non-standard (two lines between
some sections, one space between others).  I changed this to
the standard one empty line before each section heading.  I
added dots (a single period on a line) before every section
heading (.SH) so that maintainers will still find the
readability unchanged.

6. 'groff' recommends starting every sentence on its own
line, and breaking sentences at punctuation.  I added this
white space to many sentences.

7. Corrected an error in the info command:
     info "guile(Invoking Guile)"
   won't work.  It should be:
     info "(guile)Invoking Guile"

8. Compared the options list with the list generated by
'guile --help', and added the missing option '--no-debug',
and the short switches '-h' and '-v'.

9. The new version of the manual page added a description of
the environment variable GUILE_LOAD_COMPILED_PATH.  That
description referenced the guile variable %load-path.  I
changed that to %load-compiled-path.

10. Updated the copyright to include 2011.

In general, with this patch the manual page should look more
like other GNU manual pages, for example:

   man man
   man test

--

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: guile.1.patch --]
[-- Type: text/x-patch; name="guile.1.patch", Size: 10334 bytes --]

diff --git a/doc/guile.1 b/doc/guile.1
index 571638d..f892a7b 100644
--- a/doc/guile.1
+++ b/doc/guile.1
@@ -3,113 +3,210 @@
 .\" Process this file with
 .\" groff -man -Tascii foo.1
 .\"
-.TH GUILE 1
+.TH GUILE 1 "January 2011" "GNU Guile 2.0" GNU
+.
 .SH NAME
 guile \- the GNU extension language
+.
 .SH SYNOPSIS
-.B guile [-L DIRECTORY] [-l FILE] [-e FUNCTION] [\\\\]
-.B [-c EXPR] [-s SCRIPT] [--] [SCRIPT] [ARG...]
+.B guile
+.RB [\| \-L
+.IR DIRECTORY \|]
+.RB [\| \-l
+.IR FILE \|]
+.RB [\| \-e
+.IR FUNCTION \|]
+.\".RI [\| \\\\ \|]
+.RB [\| \e \|]
+.RB [\| \-c
+.IR EXPR \|]
+.RB [\| \-s
+.IR SCRIPT \|]
+.RB [\| \-\- \|]
+.RI [\| SCRIPT \|]
+.RI [\| SCRIPT's\ ARGs... \|]
 
-Only the most useful options are listed here; see below for the
-remainder.
+Only the most useful options are listed here; 
+see below for the remainder.
+.
 .SH DESCRIPTION
-GNU Guile is an implemention of the Scheme programming language.  It
-extends the R5RS and R6RS language standards, providing additional
-features necessary for real-world use.  Guile works well for interactive
-use, basic scripting, and extension of larger applications, as well as
-for stand-alone Scheme application development.
+GNU Guile is an implementation of the Scheme programming language.
+It extends the R5RS and R6RS language standards,
+providing additional features necessary for real-world use.
+
+Guile works well for interactive use,
+basic scripting,
+and extension of larger applications,
+as well as for stand-alone Scheme application development.
 
 The
 .B guile
 executable itself provides a stand-alone interactive compiler and
-run-time for Scheme programs, both for interactive use and for executing
-Scheme scripts or programs.
+run-time for Scheme programs,
+both for interactive use and for executing Scheme scripts or programs.
 
 This manual page provides only brief instruction in invoking
 .B guile
-from the command line.  Please consult the guile info documentation
+from the command line.
+Please consult the Guile info documentation
 (type 
-.B info "guile(Invoking Guile)"
+.B info "(guile) Invoking Guile"
 at a command prompt) for more information.
-
+.
 .SH OPTIONS
-.IP -L DIRECTORY
-Add DIRECTORY to the front of Guile's module load path.
-.IP -l FILE
-Load scheme source code from file.
-.IP -e FUNCTION
-After reading script, apply FUNCTION to command-line arguments.  Note
-that FUNCTION is evaluated, so e.g.
+.TP
+.BI -L \ DIRECTORY
+Add \fIDIRECTORY\fR to the front of Guile's module load path.
+.
+.TP
+.BI -l \ FILE
+Load Scheme source code from \fIFILE\fR.
+.
+.TP
+.BI -e \ FUNCTION
+After reading \fISCRIPT\fR, apply \fIFUNCTION\fR to command-line arguments.
+Note that \fIFUNCTION\fR is evaluated,
+so, for example,
 .B (@ (my-module) my-proc)
 is valid here.
-.IP \\\\
+.
+.TP
+.B \e
 The "meta switch", used to work around limitations in #! scripts.
-See "The Meta Switch" in the texinfo documentation, for more details.
-.IP --
-Stop argument processing, start guile in interactive mode.
-.IP -c EXPR
-Stop argument processing, evaluate EXPR as a scheme expression.
-.IP -s SCRIPT-FILE
-Load Scheme source from SCRIPT-FILE and execute as a script.  Note that
-the in many cases it is not necessary to use -s; one may invoke Guile
-just as
-.B guile SCRIPT-FILE ARG...
-.IP -ds
-Do -s SCRIPT at this point.  Note that this argument must be used in
-conjuction with -s.
-.IP --debug
-Start guile with the debugging VM.  By default, on when invoked
-interactively, off otherwise.
-.IP --autocompile
+See "The Meta Switch" in the texinfo documentation for more details.
+.
+.TP
+.B --
+Stop argument processing, and start
+.B guile
+in interactive mode.
+.
+.TP
+.BI -c \ EXPR
+Stop argument processing,
+and evaluate \fIEXPR\fR as a Scheme expression.
+.
+.TP
+.BI -s \ SCRIPT-FILE
+Load Scheme source from \fISCRIPT-FILE\fR and execute as a script.
+Note that in many cases it is not necessary to use \fB-s\fR;
+one may invoke
+.B guile
+simply as
+.B guile
+.I SCRIPT-FILE ARG...
+.
+.TP
+.B -ds
+Carry out \fB\-s \fISCRIPT\fR at this point in the option sequence.
+Note that this argument must be used in conjunction with \fB\-s\fR.
+.
+.TP
+.B --debug
+Start
+.B guile
+with the debugging VM.
+By default, debugging is on when
+.B guile
+is invoked interactively;
+it is off otherwise.
+.
+.TP
+.B --no-debug
+Start
+.B guile
+without the debugging VM,
+even if 
+.B guile
+is being run interactively.
+.
+.TP
+.B --autocompile
 Compile source files automatically (default behavior).
-.IP --no-autocompile
+.
+.TP
+.B --no-autocompile
 Disable automatic source file compilation.
-.IP --listen[=P]
-Listen on a port or socket for remote REPL connections.  See the manual
-for more details.
-.IP --use-srfi=N,M...
-Load SRFI extensions N, M, etc. For example, "--use-srfi=8,13".
-.IP -x EXTENSION
-Add EXTENSION to the Guile's load extension list.
-.IP --help 
-Describe command line options and exit
-.IP --version
+.
+.TP
+\fB\-\-listen\fR[=\fIP\fR]
+Listen on a port or socket for remote REPL connections.
+See the manual for more details.
+.
+.TP
+\fB\-\-use\-srfi\fR=\fIN,M\fR...
+Load SRFI extensions \fIN\fR, \fIM\fR, etc.
+For example, 
+\fB \-\-use\-srfi\fR=\fI8,13\fR.
+.
+.TP
+.BI -x \ EXTENSION
+Add \fIEXTENSION\fR to the
+.B guile
+load extension list.
+.
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Describe command-line options and exit.
+.
+.TP
+\fB\-v\fR, \fB\-\-version\fR
 Display guile version and exit.
-.IP -q
-In interactive mode, suppress loading the user's ~/.guile file.
-
+.
+.TP
+.B -q
+In interactive mode,
+suppress loading the user's initialization file,
+.I ~/.guile.
+.
 .SH ENVIRONMENT
 .\".TP \w'MANROFFSEQ\ \ 'u
 .TP
 .B GUILE_LOAD_PATH
 If
 .RB $ GUILE_LOAD_PATH
-is set, its value is used to agument the path to search for scheme
-files when loading.  It should be a colon separated list of
-directories which will be prepended to the default %load-path.
-
+is set before 
+.B guile
+is started,
+its value is used to augment the path to search for Scheme files when
+loading.
+It should be a colon-separated list of directories,
+which will be prefixed to the default
+.B %load-path.
+.TP
 .B GUILE_LOAD_COMPILED_PATH
 If
 .RB $ GUILE_LOAD_COMPILED_PATH
-is set, its value is used to agument the path to search for compiled
-Scheme files (.go files) when loading.  It should be a colon separated
-list of directories which will be prepended to the default %load-path.
-
+is set before
+.B guile
+is started,
+its value is used to augment the path to search for compiled
+Scheme files (.go files) when loading.
+It should be a colon-separated list of directories,
+which will be prefixed to the default
+.B %load-compiled-path.
+.
 .SH FILES
+.TP
 .I ~/.guile
-is a guile script that is executed before any other processing occurs.
-For example, the following .guile activates guile's readline
-interface:
+A Guile script that is executed before any other processing occurs.
+For example, the following
+.I .guile
+activates guile's readline interface:
 
-.RS 4
-(use-modules (ice-9 readline))
+.RS 9
+.B (use-modules (ice-9 readline))
 .RS 0
-(activate-readline)
-
+.B (activate-readline)
+.
 .SH "SEE ALSO"
-The full documentation for guile is maintained as a Texinfo manual.  If
-the info and guile programs are properly installed at your site, the
-command
+The full documentation for Guile is maintained as a Texinfo manual.
+If the
+.B info
+and
+.B guile
+programs are properly installed at your site,
+the command
 .IP
 .B info guile
 .PP
@@ -117,39 +214,45 @@ should give you access to the complete manual.
 
 http://www.schemers.org provides a general introduction to the
 Scheme language.
-
+.
 .SH "REPORTING BUGS"
-There is a mailing list, bug-guile@gnu.org, for reporting Guile bugs and
-fixes.  But before reporting something as a bug, please try to be sure
-that it really is a bug, not a misunderstanding or a deliberate feature.
+There is a mailing list,
+bug-guile@gnu.org,
+for reporting Guile bugs and fixes.
+But before reporting something as a bug,
+please try to be sure that it really is a bug,
+not a misunderstanding or a deliberate feature.
 We ask you to read the section ``Reporting Bugs'' in the Guile reference
-manual (or Info system) for hints on how and when to report bugs.  Also,
-include the version number of the Guile you are running in every bug
-report that you send in.  Bugs tend actually to be fixed if they can be
-isolated, so it is in your interest to report them in such a way that
-they can be easily reproduced.
-
+manual (or Info system) for hints on how and when to report bugs.
+Also, include the version number of the Guile you are running in every bug
+report that you send in.
+Bugs tend actually to be fixed if they can be isolated,
+so it is in your interest to report them in such a way that they can be
+easily reproduced.
+.
 .SH COPYING
-Copyright (C) 2010 Free Software Foundation, Inc.
+Copyright (C) 2010, 2011 Free Software Foundation, Inc.
 
 Permission is granted to make and distribute verbatim copies of this
 document provided the copyright notice and this permission notice are
 preserved on all copies.
 
 Permission is granted to copy and distribute modified versions of this
-document under the conditions for verbatim copying, provided that the
-entire resulting derived work is distributed under the terms of a
-permission notice identical to this one.
+document under the conditions for verbatim copying,
+provided that the entire resulting derived work is distributed under the
+terms of a permission notice identical to this one.
 
 Permission is granted to copy and distribute translations of this
-document into another language, under the above conditions for modified
-versions, except that this permission notice may be stated in a
+document into another language,
+under the above conditions for modified versions,
+except that this permission notice may be stated in a
 translation approved by the Free Software Foundation.
-
+.
 .SH AUTHORS
 Robert Merkel <rgmerk@mira.net> wrote this manpage.  
 Rob Browning <rlb@cs.utexas.edu> has added to it.
 
 .B guile 
-is GNU software.  Guile is originally based on Aubrey Jaffer's
-SCM interpreter, and is the work of many individuals.
+is GNU software.
+Guile is originally based on Aubrey Jaffer's SCM interpreter,
+and is the work of many individuals.

  reply	other threads:[~2011-01-25  7:05 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
2011-01-25  7:05       ` Mark Harig [this message]
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=8CD8A7569CE9F1A-10BC-A716@webmail-d094.sysops.aol.com \
    --to=idirectscm@aim.com \
    --cc=bug-guile@gnu.org \
    --cc=wingo@pobox.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).