From: Bruce Korb <bkorb@veritas.com>
Cc: guile development <guile-devel@gnu.org>
Subject: Re: character documentation errors
Date: Thu, 04 Nov 2004 09:30:35 -0800 [thread overview]
Message-ID: <418A673B.F206A5E1@veritas.com> (raw)
In-Reply-To: ljy8hho86b.fsf@troy.dt.e-technik.uni-dortmund.de
Marius Vollmer wrote:
>
> Bruce Korb <bkorb@veritas.com> writes:
>
> > It goes on to say that ``#\space'' is an alias for ``#\sp''.
> > Please fix the doc to reflect exactly what is acceptable.
>
> I fixed Guile instead to also accept #\sp. OK?
"libguile" or "guile (the program)"? My recommendation is for
all of the documented aliases: either document correctly, or
implement them correctly :-). As for me and my program, I've
coded in ``#\space'' now anyway.
Thank you!
Cheers - Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-11-04 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 0:30 character documentation errors Bruce Korb
2004-11-04 17:06 ` Marius Vollmer
2004-11-04 17:30 ` Bruce Korb [this message]
2004-11-04 18:05 ` Marius Vollmer
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=418A673B.F206A5E1@veritas.com \
--to=bkorb@veritas.com \
--cc=guile-devel@gnu.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).