From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 66706@debbugs.gnu.org, mattias.engdegard@gmail.com,
luangruo@yahoo.com, dmitry@gutov.dev, stefankangas@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#66706: [PATCH] Automatic elisp dialect insertion
Date: Thu, 26 Oct 2023 08:21:29 +0300 [thread overview]
Message-ID: <8334xyhsbq.fsf@gnu.org> (raw)
In-Reply-To: <c5c3f0f0-d9f7-417c-8290-6966d7ee5bba@gmail.com> (message from Jim Porter on Wed, 25 Oct 2023 17:07:00 -0700)
> Date: Wed, 25 Oct 2023 17:07:00 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 66706@debbugs.gnu.org,
> mattias.engdegard@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>,
> stefankangas@gmail.com
> From: Jim Porter <jporterbugs@gmail.com>
>
> In particular, what's missing from the following paragraph[1]?
>
> > Another way to think about let is that it is like a setq that is temporary and local. The values set by let are automatically undone when the let is finished. The setting only affects expressions that are inside the bounds of the let expression. In computer science jargon, we would say the binding of a symbol is visible only in functions called in the let form; in Emacs Lisp, the default scoping is dynamic, not lexical. (The non-default lexical binding is not discussed in this manual.)
> [1]
> https://www.gnu.org/software/emacs/manual/html_node/eintr/Prevent-confusion.html
IMNSHO, it is woefully incomplete. Much more needs to be said.
next prev parent reply other threads:[~2023-10-26 5:21 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 17:46 bug#66706: [PATCH] Automatic elisp dialect insertion Mattias Engdegård
2023-10-23 18:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-23 18:44 ` Eli Zaretskii
2023-10-23 19:21 ` Stefan Kangas
2023-10-23 20:20 ` Mattias Engdegård
2023-10-24 17:31 ` Mattias Engdegård
2023-10-24 18:25 ` Eli Zaretskii
2023-10-24 19:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 20:22 ` Stefan Kangas
2023-10-25 2:31 ` Eli Zaretskii
2023-10-25 11:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 12:17 ` Stefan Kangas
2023-10-25 12:54 ` Dmitry Gutov
2023-10-26 0:31 ` Michael Heerdegen
2023-10-26 6:35 ` Eli Zaretskii
2023-10-27 3:14 ` Michael Heerdegen
2023-10-27 6:26 ` Eli Zaretskii
2023-10-27 7:24 ` Michael Heerdegen
2023-10-27 7:32 ` Eli Zaretskii
2023-10-27 14:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-29 12:26 ` Eli Zaretskii
2023-10-25 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 1:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 2:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 3:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 11:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 12:46 ` Dmitry Gutov
2023-10-25 12:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 14:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 16:04 ` Eli Zaretskii
2023-10-26 0:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 12:03 ` Eli Zaretskii
2023-10-25 13:06 ` Dmitry Gutov
2023-10-25 13:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 13:40 ` Dmitry Gutov
2023-10-26 0:07 ` Jim Porter
2023-10-26 0:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 1:19 ` Jim Porter
2023-10-26 1:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 3:48 ` Jim Porter
2023-10-26 5:56 ` Jim Porter
2023-10-26 7:09 ` Eli Zaretskii
2023-10-26 2:37 ` Drew Adams
2023-10-26 2:28 ` Drew Adams
2023-10-26 5:21 ` Eli Zaretskii [this message]
2023-10-25 13:57 ` Eli Zaretskii
2023-10-25 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 16:08 ` Eli Zaretskii
2023-10-25 16:10 ` Dmitry Gutov
2023-10-25 16:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-25 18:19 ` Mattias Engdegård
2023-10-25 18:40 ` Eli Zaretskii
2023-10-25 19:09 ` Mattias Engdegård
2023-10-25 23:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 0:07 ` Jim Porter
2023-10-26 2:34 ` Drew Adams
2023-10-26 3:56 ` Jim Porter
2023-10-26 5:22 ` Eli Zaretskii
2023-10-26 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 13:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 15:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-26 8:32 ` Mattias Engdegård
2023-10-26 11:39 ` Nikolay Kudryavtsev
2023-10-26 15:36 ` Drew Adams
2023-10-25 12:36 ` Nikolay Kudryavtsev
2023-10-25 12:48 ` Dmitry Gutov
2023-10-26 11:06 ` Nikolay Kudryavtsev
2023-10-25 2:27 ` 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=8334xyhsbq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66706@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=jporterbugs@gmail.com \
--cc=luangruo@yahoo.com \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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).