unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: schwab@linux-m68k.org, 41026@debbugs.gnu.org
Subject: bug#41026: Improve documentation of `makunbound' and `fmakunbound'
Date: Sat, 02 May 2020 18:41:15 +0300	[thread overview]
Message-ID: <83d07ms5t0.fsf@gnu.org> (raw)
In-Reply-To: <87lfma4c25.fsf@stefankangas.se> (message from Stefan Kangas on Sat, 02 May 2020 17:00:02 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 02 May 2020 17:00:02 +0200
> Cc: 41026@debbugs.gnu.org
> 
> Andreas Schwab <schwab@linux-m68k.org> writes:
> 
> > On Mai 02 2020, Stefan Kangas wrote:
> >
> >> +       doc: /* Make variable SYMBOL's value be void.
> >
> > What's a variable symbol?  Is that the same as a varying symbol?
> 
> The sentence is a bit unwieldy to get right, if you also want to
> include the word "variable".  Is this clearer?
> 
> "Make the value of the variable named SYMBOL be void."

I think the ELisp manual gets it right:

  Empty out the value cell of SYMBOL, making it void as a variable.





  reply	other threads:[~2020-05-02 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 13:53 bug#41026: Improve documentation of `makunbound' and `fmakunbound' Stefan Kangas
2020-05-02 14:03 ` Eli Zaretskii
2020-05-02 14:17   ` Stefan Kangas
2020-05-02 14:22     ` Eli Zaretskii
2020-05-02 20:25       ` Stefan Kangas
2020-05-02 21:12         ` Andreas Schwab
2020-05-02 21:30           ` Stefan Kangas
2020-05-04  3:06           ` Richard Stallman
2020-05-04  7:31             ` Andreas Schwab
2020-05-04 12:52               ` Stefan Kangas
2020-05-04 13:05                 ` Andreas Schwab
2020-05-03 14:21         ` Eli Zaretskii
2020-05-03 20:07           ` Stefan Kangas
2020-05-02 14:55 ` Andreas Schwab
2020-05-02 15:00   ` Stefan Kangas
2020-05-02 15:41     ` Eli Zaretskii [this message]
2020-05-02 20:22   ` Drew Adams
2020-05-03  3:43   ` Richard Stallman

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=83d07ms5t0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41026@debbugs.gnu.org \
    --cc=schwab@linux-m68k.org \
    --cc=stefan@marxist.se \
    /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).