From: Neil Jerram <neil@ossau.uklinux.net>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org
Subject: Re: More missing options for guile/doc/guile.1
Date: Sat, 15 Jan 2011 21:15:24 +0000 [thread overview]
Message-ID: <8739otg977.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <8CD818E9822F6DE-D0C-29CF8@Webmail-m115.sysops.aol.com> (Mark Harig's message of "Thu, 13 Jan 2011 18:13:16 -0500")
Mark Harig <idirectscm@aim.com> writes:
> Here is a list of additional options that are not described
> in the guile manual page:
Thank you for pointing these out, and for suggesting suitable text.
However, rather than applying these updates, I wonder if the OPTIONS
section of guile.1 should instead be autogenerated from the `Invoking
Guile' node of the manual?
Andy/Ludo, any objection to that?
Neil
> A section named "REPORTING BUGS" could also be added so
> that the email address for reporting errors could be listed.
> And a "COPYING" section could be added to list the copyright
> information. Adding these two sections would bring the Guile
> manual page into agreement with the similar sections in the
> Emacs manual page.
Good idea, thanks; I've added these.
Neil
next prev parent reply other threads:[~2011-01-15 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 23:13 More missing options for guile/doc/guile.1 Mark Harig
2011-01-15 21:15 ` Neil Jerram [this message]
2011-01-17 22:25 ` Ludovic Courtès
2011-01-26 19:22 ` Andy Wingo
2011-01-26 21:49 ` Neil Jerram
2011-01-27 17:06 ` Ludovic Courtès
2011-01-27 19:25 ` Mark Harig
2011-01-27 22:35 ` Andy Wingo
[not found] ` <8CD8C7DAC060621-190C-94B30@Webmail-d109.sysops.aol.com>
2011-01-27 22:52 ` 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=8739otg977.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).