unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kelly Dean <kelly@prtime.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Rant - Elisp terminology is deceptive
Date: Sat, 24 Jan 2015 10:30:59 +0000	[thread overview]
Message-ID: <vSBKENd7ygMsRVo8YjOrZAZSstXQJbLtz3H5b5z1Zsv@local> (raw)
In-Reply-To: <87ppa4uaay.fsf@uwakimon.sk.tsukuba.ac.jp>

Stephen J. Turnbull wrote:
> Buffer-local values are global values in the usual
> sense that they are instance-wide and can be accessed in local context
> if not shadowed by let-bindings and the like.

Function parameters (or a closure's parameters and environment variables) are global variables in the sense that they're ‟instance-wide” (within the entire function or closure) and can be accessed in local context if not shadowed by let-bindings.

But «within an entire function or closure» isn't really instance-wide? Well neither is «within an entire buffer».

The global environment is the outermost one. A buffer's environment is not. There's only one global environment. There can be multiple buffers and multiple closures, each with its own environment. ‟Buffer-local” is a perfectly good term for buffer-locals. Calling them ‟global” would be misleading, and it's good that Emacs doesn't do that.

‟Global” is the right term for globals.



  parent reply	other threads:[~2015-01-24 10:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  2:59 Rant - Elisp terminology is deceptive Kelly Dean
2015-01-23 20:15 ` Stefan Monnier
2015-01-24  0:41   ` Kelly Dean
2015-01-24  0:48     ` Óscar Fuentes
2015-01-24  3:28     ` Stephen J. Turnbull
2015-01-24  8:51       ` Eli Zaretskii
2015-01-24 10:32         ` Kelly Dean
2015-01-24 11:26           ` Eli Zaretskii
2015-01-24 10:30       ` Kelly Dean [this message]
2015-01-24 11:03         ` David Kastrup
2015-01-24 23:24           ` Kelly Dean
2015-01-25  9:16             ` David Kastrup
2015-01-26  3:52               ` Kelly Dean
2015-01-26  8:28                 ` Thien-Thi Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2013-05-22  3:44 [PATCH] Desktop mode saves mark-ring too verbosely Kelly Dean
2013-11-23 13:40 ` Stefan Monnier
2015-01-21 12:11   ` Kelly Dean
2015-01-21 15:04     ` Stefan Monnier
2015-01-22  5:43       ` Kelly Dean
2015-01-22  8:20         ` Ivan Shmakov
2015-01-23 13:20           ` Kelly Dean
2015-01-23 14:09             ` Ivan Shmakov
2015-01-24  3:08             ` Stephen J. Turnbull
2015-01-24 23:30               ` Elisp terminology (was: Re: [PATCH] Desktop mode saves mark-ring too verbosely) Kelly Dean
2015-01-25  9:49                 ` Elisp terminology David Kastrup

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=vSBKENd7ygMsRVo8YjOrZAZSstXQJbLtz3H5b5z1Zsv@local \
    --to=kelly@prtime.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.org \
    /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).