From: Jean Louis <bugs@gnu.support>
To: tomas@tuxteam.de
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: [SOLVED with `eval']: Why I cannot use this variable in macro call from function?
Date: Wed, 9 Jun 2021 09:42:00 +0300 [thread overview]
Message-ID: <YMBiuG5Z8kBd4Fmk@protected.localdomain> (raw)
In-Reply-To: <20210609060959.GA21706@tuxteam.de>
* tomas@tuxteam.de <tomas@tuxteam.de> [2021-06-09 09:11]:
> You'll see "43" in your minibuffer. We managed to set the dynamically
> "defined" variable "that-other-var" to 43. Yay! Now enter
>
> that-other-var
>
> ...and again C-x e. Minibuffer says... 43. The variable escaped the
> scope. Bad variable, but hey, that's how setq goes, no?
Yes. I did it.
> * Experiment 2
>
> Make new lisp interaction buffer, as above. Make sure you have
> lexical binding (when experimenting, always change at most one
> thing at a time, right?). Now:
>
> (let ((some-var 42)
> (that-other-var 44)) ; bind that-other-var locally
> (eval '(setq that-other-var 43))
> (message "%S\n" that-other-var))
>
> Again, minibuffer says 43. Now...
>
> that-other-var
>
> ...and C-x e. What does minibuffer say? Is that right or wrong?
> Explain.
The one bound locally got 44, it was protected from a global
variable. That is so far expected. If I wish for example avoid case
sensitive entries, I do:
(let ((completion-ignore-case t)
(collection '("One" "Two")))
(completing-read "Choice: " collection nil t))
In that case the global variable `completion-ignore-case' is nil,
but I bind it temporarily globally to T, for better user
experience.
> I guess you'll need a more differentiated model than just "works".
> Works how? Do you want it to "work" like that? If yes, then fine.
Here is the function that just works, it asks for global
variable. If I would know better way, I would do it and if you
know some other way to dynamically assign global variable let me
know:
(defun rcd-db-completing-table-history (table)
"Return symbol of history variable for TABLE.
If TABLE is \"businesses\" the symbol will become
`rcd-db-completing-table-history-businesses' and it will be used
for functions `completing-read' and `read-from-minibuffer'
history.
If a dynamically generated variable does not exist, it will be
generated on the fly."
(let ((rcd-symbol (intern (concat "rcd-db-completing-table-history-" table)))
(description (format "History for table `%s'" table)))
(if (boundp rcd-symbol)
rcd-symbol
(eval (list 'defvar rcd-symbol nil description)))))
Just like any code, the above (eval (list 'defvar rcd-symbol nil
description)) is understandable only to people who know what
eval, list, defvar and variables mean. We are now in
collaboration and I am asking if there is better way to
dynamically assign a global variable if it does not exist and
return a symbol of it.
What I don't know is why the function work as I am somehow
expecting that new evaluation of (defvar ex-sting-variable nil)
would make it nil, but it does not and history is remembered.
> A very wise person [1] once said that he doesn't write programs
> to get the computer to do what he wants, but to convince his
> colleagues that the computer is doing the right thing.
Fine, but that way I don't get my dynamically assigned global
variables. (づ。◕‿‿◕。)づ
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-06-09 6:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 13:10 Why I cannot use this variable in macro call from function? Jean Louis
2021-06-08 13:41 ` [External] : " Drew Adams
2021-06-08 14:47 ` Jean Louis
2021-06-08 17:14 ` Jean Louis
2021-06-08 18:31 ` tomas
2021-06-08 18:37 ` Oops function? tomas
2021-06-08 19:27 ` [SOLVED with `eval']: Why I cannot use this variable in macro call from function? Jean Louis
2021-06-08 20:03 ` tomas
2021-06-08 20:06 ` Sorry again tomas
2021-06-08 20:12 ` [SOLVED with `eval']: Why I cannot use this variable in macro call from function? Jean Louis
2021-06-08 20:23 ` tomas
2021-06-08 20:38 ` Jean Louis
2021-06-08 20:47 ` Jean Louis
2021-06-09 6:09 ` tomas
2021-06-09 6:42 ` Jean Louis [this message]
2021-06-09 6:51 ` tomas
2021-06-09 7:03 ` Jean Louis
2021-06-09 7:39 ` tomas
2021-06-09 8:22 ` Jean Louis
2021-06-09 8:54 ` tomas
2021-06-09 10:56 ` Jean Louis
2021-06-09 11:33 ` tomas
2021-06-09 14:39 ` Jean Louis
2021-06-09 16:41 ` tomas
2021-06-10 2:10 ` Robert Thorpe
2021-06-10 6:56 ` Jean Louis
2021-06-11 6:33 ` Robert Thorpe
2021-06-11 7:03 ` Jean Louis
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=YMBiuG5Z8kBd4Fmk@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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).