From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Printing alist pairs to a dedicated buffur
Date: Thu, 25 Apr 2024 23:38:19 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488AFCE4587111F25A59DEFF3172@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y1919iu1.fsf@dataswamp.org>
> >> `setq' creates global static/lexical variables
> >
> > Not true.
>
> As you know -
> unless there already is another variable with that name, and
> such as that can be present in many forms (`let' bindings,
> formal parameters etc) including dynamic/special variables and
> if so it remains dynamic/special with `setq' but otherwise
> it'll be static/lexical.
Yes, you understand `let', and using `setq'
inside `let', correctly.
(And in that regard, Elisp `let' is like CL
`let'. But Elisp also has buffer-local etc.)
> > As (elisp) "Scoping Rules for Variable Bindings" says:
> >
> > "By default, the local bindings that Emacs
> > creates are "dynamic bindings".
> > ...
> > The dynamic binding was (and still is)
> > the default in Emacs for many years [...]
>
> Emacs is de facto static/lexical.
No, it's not. Not yet.
> $ cd ~/src/emacs
> $ ls **/*.el | wc -l
> 2312
> $ head **/*.el | grep -I "lexical-binding" | wc -l
> 2285
That just shows that most Elisp files provided
with Emacs have `lexical-binding' = t.
Dynamic binding is still the default in Elisp.
The doc is correct about that.
___
Let us know, when you use lexical binding for
_all_ your defuns, as well as for defface and
all the rest. ;-)
next prev parent reply other threads:[~2024-04-25 23:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 12:57 Printing alist pairs to a dedicated buffur Heime
2024-04-19 13:24 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-04-19 19:26 ` Heime
2024-04-19 19:42 ` Heime
2024-04-20 9:55 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-04-20 10:08 ` Emanuel Berg
2024-04-25 11:13 ` Heime
2024-04-26 0:27 ` Emanuel Berg
2024-04-25 15:55 ` [External] : " Drew Adams
2024-04-25 16:18 ` Heime
2024-04-25 22:43 ` Emanuel Berg
2024-04-25 22:29 ` Emanuel Berg
2024-04-25 23:38 ` Drew Adams [this message]
2024-04-26 0:03 ` Emanuel Berg
2024-04-26 15:55 ` Drew Adams
2024-04-26 16:57 ` Heime
2024-04-26 17:27 ` Yuri Khan
2024-04-27 22:20 ` Heime
2024-04-26 0:41 ` Emanuel Berg
2024-04-26 1:08 ` Emanuel Berg
2024-04-20 16:37 ` Heime
2024-04-20 17:23 ` Heime
2024-04-20 20:48 ` Yuri Khan
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=SJ0PR10MB5488AFCE4587111F25A59DEFF3172@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.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.
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).