From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
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:07:47 +0100 [thread overview]
Message-ID: <m3fwsif1ss.fsf@unquote.localdomain> (raw)
In-Reply-To: <3D05815A-48F6-43E8-8A9D-5415972D032F@raeburn.org> (Ken Raeburn's message of "Wed, 19 Jan 2011 14:50:29 -0500")
On Wed 19 Jan 2011 20:50, Ken Raeburn <raeburn@raeburn.org> writes:
> In short, don't document how to work around a bug, if you can just fix
> the bug. :-)
Very much agreed. Writing documentation is hard enough without having
to document bugs in addition to features :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-01-24 21:07 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 [this message]
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=m3fwsif1ss.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=raeburn@raeburn.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).