[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (interactive) arguments
From: |
Marcin Borkowski |
Subject: |
Re: (interactive) arguments |
Date: |
Thu, 02 Jan 2020 19:11:16 +0100 |
User-agent: |
mu4e 1.1.0; emacs 27.0.50 |
On 2020-01-02, at 17:57, Jean-Christophe Helary
<jean.christophe.helary@traduction-libre.org> wrote:
>> On Jan 3, 2020, at 1:30, Marcin Borkowski <mbork@mbork.pl> wrote:
>>
>>> Now, when I use the "expression" version, it looks like the arguments are
>>> not assigned to variables as they are input, so for ex, I can't use a
>>> default value for the input based on the first input...
>>>
>>> Is there a way around that ?
>>
>> Does this help?
>>
>> http://mbork.pl/2015-09-12_A_trick_with_argument_for_interactive_call
>
> ā
>> The point is that the form right after interactive should return a list of
>> two elements, and that is everything interactive cares for ā what the
>> (local) variables inside let* are called is none if its business.
>
>
> That's really clever ! :)
>
>> Now Iām quite sure that you could cook up a macro interactive*, which would
>> wrap all this in a nice syntax. That, though, I will try some other day.
>
> Have you tried ?
Nope, and now that I know more about Elisp, I'm 99% sure it's
impossible, since `interactive' is not "evaluated" in any sense. But
I'd like to hear from someone more competent.
Best,
--
Marcin Borkowski
http://mbork.pl