unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Wilfred Hughes <me@wilfred.me.uk>
Cc: 24342-done@debbugs.gnu.org
Subject: bug#24342: Typo in manual?
Date: Fri, 02 Sep 2016 10:13:06 +0200	[thread overview]
Message-ID: <87h99yiust.fsf@pobox.com> (raw)
In-Reply-To: <CAFXAjY7x=1LrmUNXaWepoZtgekfEzGxwvwQq_VrkNB-0vAHfEw@mail.gmail.com> (Wilfred Hughes's message of "Wed, 31 Aug 2016 00:28:52 -0400")

On Wed 31 Aug 2016 06:28, Wilfred Hughes <me@wilfred.me.uk> writes:

> I was reading
> https://www.gnu.org/software/guile/manual/html_node/Nil.html#Nil and
> noticed that the last code section uses deffn.
>
> Is this correct? Since it's intended to be an elisp function,
> shouldn't it be 'defun'?

I think it's a typo, texinfo uses @deffn to define functions, probably
just a thinko.  Fixed, tx :)

Andy





      reply	other threads:[~2016-09-02  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  4:28 bug#24342: Typo in manual? Wilfred Hughes
2016-09-02  8:13 ` Andy Wingo [this message]

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=87h99yiust.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=24342-done@debbugs.gnu.org \
    --cc=me@wilfred.me.uk \
    /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).