all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Van L <van@scratch.space>
To: 32037@debbugs.gnu.org
Subject: bug#32037: simplify possessive form's "functions' definitions"
Date: Tue, 3 Jul 2018 01:11:00 +1000	[thread overview]
Message-ID: <D63B8C24-0260-4E99-B46E-6A4B1A9F2EE4@scratch.space> (raw)

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index be3e938b24..82c49bf693 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -3028,7 +3028,7 @@ Primitive Functions
 @cindex Primitives written in C
 All functions are defined in terms of other functions, except for a few
 @dfn{primitive} functions that are written in the C programming
-language.  When you write functions' definitions, you will write them in
+language.  When you write function definitions, you will write them in
 Emacs Lisp and use other functions as your building blocks.  Some of the
 functions you will use will themselves be written in Emacs Lisp (perhaps
 by you) and some will be primitives written in C@.  The primitive
@@ -3179,7 +3179,7 @@ defun
 
 @findex * @r{(multiplication)}
 The third line of the example consists of the body of the function
-definition.  (Most functions' definitions, of course, are longer than
+definition.  (Most function definitions, of course, are longer than
 this.)  In this function, the body is the list, @code{(* 7 number)}, which
 says to multiply the value of @var{number} by 7.  (In Emacs Lisp,
 @code{*} is the function for multiplication, just as @code{+} is the






             reply	other threads:[~2018-07-02 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 15:11 Van L [this message]
2018-07-02 15:32 ` bug#32037: simplify possessive form's "functions' definitions" Eli Zaretskii
2018-07-02 15:35   ` Van L
2018-07-02 16:24     ` Eli Zaretskii
2018-07-02 17:19     ` Glenn Morris
2018-07-02 19:59   ` Robert Pluim
2018-07-04 16:40     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D63B8C24-0260-4E99-B46E-6A4B1A9F2EE4@scratch.space \
    --to=van@scratch.space \
    --cc=32037@debbugs.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.