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

Previous Next

Package: emacs;

Reported by: Matt <matt <at> excalamus.com>

Date: Sun, 12 Jan 2025 10:29:02 UTC

Severity: wishlist

Fixed in version 30.1

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#75512; Package emacs. (Sun, 12 Jan 2025 10:29:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Matt <matt <at> excalamus.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 12 Jan 2025 10:29:02 GMT) Full text and rfc822 format available.

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

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





Severity set to 'wishlist' from 'normal' Request was from Stefan Kangas <stefankangas <at> gmail.com> to control <at> debbugs.gnu.org. (Tue, 21 Jan 2025 02:28:03 GMT) Full text and rfc822 format available.

Reply sent to Stefan Kangas <stefankangas <at> gmail.com>:
You have taken responsibility. (Sat, 01 Feb 2025 03:11:02 GMT) Full text and rfc822 format available.

Notification sent to Matt <matt <at> excalamus.com>:
bug acknowledged by developer. (Sat, 01 Feb 2025 03:11:02 GMT) Full text and rfc822 format available.

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

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.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 01 Mar 2025 12:24:11 GMT) Full text and rfc822 format available.

This bug report was last modified 167 days ago.

Previous Next


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