Re: [SOLVED with `eval']: Why I cannot use this variable in macro call from function?

[tomas]

On Wed, Jun 09, 2021 at 10:03:16AM +0300, Jean Louis wrote:
> * tomas@tuxteam.de <tomas@tuxteam.de> [2021-06-09 09:52]:
> > [skipping the rest. I don't want even to think wrapping my head
> > around all that before basic things are not cleared. You'll have
> > to find yourself another sparring partner for this one, sorry]
> 
> Feel free to be more direct. If I don't see what you see and that is
> exactly what I wish to know, then tell me. If you remain mysterious
> even while it is clear that I don't see what you are pointing out, how
> do you expect me to see it without explanation? 
> 
> I had problems constructing a macro, then I got information it is
> special form, it will not work, etc. So it works now with `eval'.
> 
> The bottom question is if some other solution exists or not to
> dynamically create completing-read and read-from-minibuffer history
> variables.

You snipped the (for me) interesting part: did you notice how
`eval' jumps over the local declaration? It doesn't even /see/
it, the defun whithin the eval munged with the outer scope
(which might be buffer-local or just global).

You could as well have messed with the obarray [1] directly.

If this is what you want, fine. If it's not, think again. I can't
even venture a guess towards what you have in mind, I'm that bad
at interpreting what you write.

And then there is the issue of how readable your code becomes,
which will be important or not, depending on whether you want
others to read it or not.

Cheers

[1] Finding which obarray to munge is left as an exercise for
   the reader.

 - t

signature.asc
Description: Digital signature