unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicholas Drozd <nicholasdrozd@gmail.com>
Cc: 37811@debbugs.gnu.org
Subject: bug#37811: "standard GNU Emacs Lisp"
Date: Sat, 19 Oct 2019 12:44:09 +0300	[thread overview]
Message-ID: <83mudx6pee.fsf@gnu.org> (raw)
In-Reply-To: <CABAiW0oTJAzmZvR8J3veyRFZVE=bGmwrFE=Q3hNVjy3TC71ARQ@mail.gmail.com> (message from Nicholas Drozd on Fri, 18 Oct 2019 12:11:34 -0500)

> From: Nicholas Drozd <nicholasdrozd@gmail.com>
> Date: Fri, 18 Oct 2019 12:11:34 -0500
> 
> Section 5.7 of the Elisp manual ("Using Lists as Sets") mentions
> "standard GNU Emacs Lisp". This makes it sound like there is a
> language standard, which is not the case. I suggest changing the word
> "standard". Possible alternatives: "basic", "plain", "out-of-the-box".

It would sound as if there's a standard if "Standard" was capitalized,
which it isn't.

The text is

     Common Lisp note: Common Lisp has functions ‘union’ (which avoids
     duplicate elements) and ‘intersection’ for set operations.
     Although standard GNU Emacs Lisp does not have them, the ‘cl-lib’
     library provides versions.  *Note (cl)Lists as Sets::.

So "standard" is used here in contrast to CL.  I don't think any of
the proposed replacements pick up that nuance, do they?

We could perhaps simply drop "standard", I think the text will be
understood even without that, given that the reference to CL is so
close.





  parent reply	other threads:[~2019-10-19  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 17:11 bug#37811: "standard GNU Emacs Lisp" Nicholas Drozd
2019-10-19  8:37 ` Lars Ingebrigtsen
2019-10-19  9:44 ` Eli Zaretskii [this message]
2019-10-19 12:35   ` Andreas Schwab
2019-10-19 12:50     ` Eli Zaretskii
2019-10-19 12:53       ` Eli Zaretskii
2019-11-07 23:48         ` Stefan Kangas
2019-11-08  9:56           ` 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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83mudx6pee.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37811@debbugs.gnu.org \
    --cc=nicholasdrozd@gmail.com \
    /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 public inbox

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

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).