GNU bug report logs - #75512
Typo in (elisp) Symbol Components documentation

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Matt <matt <at> excalamus.com>
Subject: bug#75512: closed (Re: bug#75512: Typo in (elisp) Symbol
 Components documentation)
Date: Sat, 01 Feb 2025 03:11:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#75512: Typo in (elisp) Symbol Components documentation

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 75512 <at> debbugs.gnu.org.

-- 
75512: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75512
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Matt <matt <at> excalamus.com>, 75512-done <at> debbugs.gnu.org
Subject: Re: bug#75512: Typo in (elisp) Symbol Components documentation
Date: Sat, 1 Feb 2025 04:10:13 +0100

Version: 30.1

Matt <matt <at> excalamus.com> writes:

> Incorrect plural on word "variable":
>
> modified   doc/lispref/symbols.texi
> @@ -106,7 +106,7 @@ reference any object.  (This is not the same thing as holding the symbol
>  a value cell that is void results in an error, such as @samp{Symbol's
>  value as variable is void}.
>
> -  Because each symbol has separate value and function cells, variables
> +  Because each symbol has separate value and function cells, variable
>  names and function names do not conflict.  For example, the symbol
>  @code{buffer-file-name} has a value (the name of the file being
>  visited in the current buffer) as well as a function definition (a
>
> It may also help comprehension to remove the word "names" as follows:
>
> modified   doc/lispref/symbols.texi
> @@ -106,8 +106,8 @@ reference any object.  (This is not the same thing as holding the symbol
>  a value cell that is void results in an error, such as @samp{Symbol's
>  value as variable is void}.
>
> -  Because each symbol has separate value and function cells, variables
> -names and function names do not conflict.  For example, the symbol
> +  Because each symbol has separate value and function cells, variable
> +and function names do not conflict.  For example, the symbol
>  @code{buffer-file-name} has a value (the name of the file being
>  visited in the current buffer) as well as a function definition (a
>  primitive function that returns the name of the file):
>
> Removing "names" makes the form of the statement match the form of the preceding phrase.  The phrase has form "A and B X", the statement has form "A X and B X".

Thanks!  I fixed it like this instead:

    Because each symbol has separate value and function cells, the names
    of variables and functions do not conflict.

Closing this bug.

[Message part 3 (message/rfc822, inline)]

From: Matt <matt <at> excalamus.com>
To: "bug-gnu-emacs" <bug-gnu-emacs <at> gnu.org>
Subject: Typo in (elisp) Symbol Components documentation
Date: Sun, 12 Jan 2025 11:28:40 +0100

Incorrect plural on word "variable":

modified   doc/lispref/symbols.texi
@@ -106,7 +106,7 @@ reference any object.  (This is not the same thing as holding the symbol
 a value cell that is void results in an error, such as @samp{Symbol's
 value as variable is void}.
 
-  Because each symbol has separate value and function cells, variables
+  Because each symbol has separate value and function cells, variable
 names and function names do not conflict.  For example, the symbol
 @code{buffer-file-name} has a value (the name of the file being
 visited in the current buffer) as well as a function definition (a

It may also help comprehension to remove the word "names" as follows:

modified   doc/lispref/symbols.texi
@@ -106,8 +106,8 @@ reference any object.  (This is not the same thing as holding the symbol
 a value cell that is void results in an error, such as @samp{Symbol's
 value as variable is void}.
 
-  Because each symbol has separate value and function cells, variables
-names and function names do not conflict.  For example, the symbol
+  Because each symbol has separate value and function cells, variable
+and function names do not conflict.  For example, the symbol
 @code{buffer-file-name} has a value (the name of the file being
 visited in the current buffer) as well as a function definition (a
 primitive function that returns the name of the file):

Removing "names" makes the form of the statement match the form of the preceding phrase.  The phrase has form "A and B X", the statement has form "A X and B X".

--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode

Previous Next

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