From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Understanding the "let" construct and the setting of variables
Date: Fri, 18 Dec 2020 21:12:16 +0300 [thread overview]
Message-ID: <X9zxAPY/m8d+WAyw@protected.rcdrun.com> (raw)
In-Reply-To: <873603164g.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2020-12-18 18:43]:
>
> 3. if that isn't enough to use let/let* because several
> functions need to access a variable, use `setq' at the base
> level (i.e., first char of the line, or column 0) - not
> that Elisp has only one level, really, which is why you
> should use `setq' there to avoid confusion and errors.
> Because everyone can see what is created by `setq', this
> should be visible in the code style as well.
>
> Note that just because it would seem that two functions
> need access to the same variable, this actually doesn't
> have to be the case at all! Think it thru one extra time
> before you do it.
Instructions like that belong on a website where they become easily
searchable for other users to understand it.
We could index all the mailing list easily and provide search engine
for this.
next prev parent reply other threads:[~2020-12-18 18:12 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 0:10 Understanding the "let" construct and the setting of variables steve-humphreys
2020-12-17 0:21 ` Joost Kremers
2020-12-17 2:08 ` steve-humphreys
2020-12-17 3:12 ` steve-humphreys
2020-12-17 8:01 ` Joost Kremers
2020-12-17 8:31 ` steve-humphreys
2020-12-17 8:50 ` Joost Kremers
2020-12-17 8:10 ` Joost Kremers
2020-12-17 8:43 ` steve-humphreys
2020-12-17 8:56 ` Joost Kremers
2020-12-18 20:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-18 20:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-18 21:07 ` Jean Louis
2020-12-18 22:31 ` tomas
2020-12-18 20:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-17 2:49 ` steve-humphreys
2020-12-17 7:58 ` Joost Kremers
2020-12-17 16:55 ` Drew Adams
2020-12-17 20:11 ` steve-humphreys
2020-12-17 21:57 ` Drew Adams
2020-12-17 22:35 ` Michael Heerdegen
2020-12-18 9:01 ` tomas
2020-12-18 9:16 ` Michael Heerdegen
2020-12-18 20:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-19 2:17 ` Michael Heerdegen
2020-12-19 2:52 ` Drew Adams
2020-12-19 5:15 ` Stefan Monnier
2020-12-18 20:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-17 0:25 ` steve-humphreys
2020-12-17 0:35 ` steve-humphreys
2020-12-17 1:05 ` Joost Kremers
2020-12-17 1:20 ` steve-humphreys
2020-12-18 20:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-17 4:34 ` Jean Louis
2020-12-17 5:12 ` steve-humphreys
2020-12-19 6:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-17 7:31 ` steve-humphreys
2020-12-19 5:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-19 6:49 ` Jean Louis
2020-12-20 5:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-18 17:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-18 17:48 ` tomas
2020-12-18 15:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-18 18:12 ` Jean Louis [this message]
2020-12-18 18:20 ` Drew Adams
2020-12-18 18:45 ` Jean Louis
2020-12-18 19:16 ` Drew Adams
2020-12-18 20:00 ` Jean Louis
2020-12-18 21:27 ` Christopher Dimech
2020-12-19 6:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=X9zxAPY/m8d+WAyw@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.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).