unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: help-gnu-emacs@gnu.org
Subject: Re: (interactive) arguments
Date: Fri, 3 Jan 2020 01:57:56 +0900	[thread overview]
Message-ID: <18220344-15BC-4605-B7B8-0E841E930D85@traduction-libre.org> (raw)
In-Reply-To: <871rshddo3.fsf@mbork.pl>



> 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 ?


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune





  parent reply	other threads:[~2020-01-02 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31  3:50 (interactive) arguments Jean-Christophe Helary
2020-01-01 15:51 ` Stefan Monnier
2020-01-01 16:26   ` Jean-Christophe Helary
2020-01-02 16:08     ` Jean-Christophe Helary
2020-01-02 16:30       ` Marcin Borkowski
2020-01-02 16:42         ` Jean-Christophe Helary
2020-01-02 16:57         ` Jean-Christophe Helary [this message]
2020-01-02 18:11           ` Marcin Borkowski
2020-01-04 16:28       ` Stefan Monnier
2020-01-04 17:44         ` Jean-Christophe Helary

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=18220344-15BC-4605-B7B8-0E841E930D85@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --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).