GNU bug report logs - #32045
typo

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32045 in the body.
You can then email your comments to 32045 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Van L <van <at> scratch.space>
To: bug-gnu-emacs <at> gnu.org
Subject: typo
Date: Tue, 3 Jul 2018 10:48:44 +1000

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index be3e938b24..7a8b49edad 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -3031,7 +3031,7 @@ Primitive Functions
 language.  When you write functions' 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
+by you) and some will be primitives written in C.  The primitive
 functions are used exactly like those written in Emacs Lisp and behave
 like them.  They are written in C so we can easily run GNU Emacs on any
 computer that has sufficient power and can run C.

Message #10 received at 32045-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 32045-done <at> debbugs.gnu.org
Subject: Re: bug#32045: typo
Date: Mon, 02 Jul 2018 20:58:10 -0400

Van L wrote:

> -by you) and some will be primitives written in C@.  The primitive
> +by you) and some will be primitives written in C.  The primitive

If you use vc-annotate (or git blame, or read the texinfo manual about @.),
you will see this is not a typo.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.