unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-26 4ab4551: Firm up documentation of generalized variables
Date: Thu, 22 Mar 2018 20:27:33 +0000	[thread overview]
Message-ID: <20180322202733.GA7491@ACM> (raw)
In-Reply-To: <jwva7v1gqac.fsf-monnier+emacsdiffs@gnu.org>

Hello, Stefan.

On Wed, Mar 21, 2018 at 15:56:51 -0400, Stefan Monnier wrote:
> >     * doc/lispref/variables.texi (Generalized Variables)
> >     (Setting Generalized Variables): Define a generalized variable as something
> >     setf can write to.  Remove the insinuation that hackers have poor memories.
> >     State explicitly that the list of GVs given is complete.  Remove the
> >     suggestion that `setf' has superseded, or is in the process of superseding,

> Thanks, it's indeed more clear now.
> But note that the list is not "complete".

What the paragraph I modified actually says on this point is:

    The following Lisp forms are the forms in Emacs that will work as
    generalized variables, and so may appear in the @var{place} argument
    of @code{setf}:

I take it this isn't quite accurate.  How is it inaccurate?

Is it (i) because there are more GVs in the cl-*.el files?  Or (ii)
because users can create their own GVs?  Or (iii) <something else>?

Depending on the answer, I suggest one of the following corrections:

    The following Lisp forms are the forms in standard Emacs that will
    work as generalized variables, and so may appear in the PLACE
    argument of `setf'.  You can load more such forms from the file
    xxxx.el.

    The following Lisp forms are the forms in standard Emacs that will
    work as generalized variables, and so may appear in the PLACE
    argument of `setf'.  You can also create your own generalized
    variables (see Adding Generalized Variables).

It would be nice to fix this.  What do you think?

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2018-03-22 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180321175854.17105.90124@vcs0.savannah.gnu.org>
     [not found] ` <20180321175856.0D4C42041C@vcs0.savannah.gnu.org>
2018-03-21 19:56   ` [Emacs-diffs] emacs-26 4ab4551: Firm up documentation of generalized variables Stefan Monnier
2018-03-22 20:27     ` Alan Mackenzie [this message]
2018-03-22 21:03       ` Stefan Monnier

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=20180322202733.GA7491@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).