From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Iinteractive function allowing multiple inputs
Date: Mon, 09 Dec 2024 21:42:21 +0000 [thread overview]
Message-ID: <yqeqJqgs3mnptW01DXNUOCVmEk5oOMrvKe8AN3up1CTQosmxvHKNaiPJv2jdVvf2R11pZ66sPC-ZYWSiua8St-uYNXRVWw3y1opw0B3CswQ=@protonmail.com> (raw)
In-Reply-To: <Z1dfOvfcstVLRkBz@lco2>
Sent with Proton Mail secure email.
On Tuesday, December 10th, 2024 at 9:20 AM, Jean Louis <bugs@gnu.support> wrote:
> * Heime heimeborgia@protonmail.com [2024-12-10 00:14]:
>
> > Yes, but the values are not set automatically as one can do with a call
> > with arguments. The code will force on you an interaction as though you
> > are in interactive mode.
>
>
> That is why I do like this:
>
> (defun my-multi-input-function (&optional input1 input2 input3)
> "An example function that takes three inputs and displays them."
> (interactive)
> (let ((input1 (or input1 (read-string "Enter the first input: ")))
> (input2 (or input2 (read-string "Enter the second input: ")))
> (input3 (or input3 (read-string "Enter the third input: "))))
> (message "You entered: %s, %s, %s" input1 input2 input3)))
>
> Then you can call function:
>
> (my-multi-input-function input1 input2 input3)
>
> or if those are nil, it will ask you. - Jean Louis
Right. If passed a value, the read-string is skipped.
I prefer the interactive declaration myself.
next prev parent reply other threads:[~2024-12-09 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 18:40 Iinteractive function allowing multiple inputs Heime via Users list for the GNU Emacs text editor
2024-12-09 20:43 ` Jean Louis
2024-12-09 20:48 ` Heime via Users list for the GNU Emacs text editor
2024-12-09 21:02 ` Heime via Users list for the GNU Emacs text editor
2024-12-09 21:11 ` Jean Louis
2024-12-09 21:06 ` Jean Louis
2024-12-09 21:14 ` Heime via Users list for the GNU Emacs text editor
2024-12-09 21:20 ` Jean Louis
2024-12-09 21:42 ` Heime via Users list for the GNU Emacs text editor [this message]
2024-12-09 21:46 ` Heime via Users list for the GNU Emacs text editor
2024-12-09 23:05 ` Jean Louis
2024-12-09 23:47 ` Heime via Users list for the GNU Emacs text editor
2024-12-10 7:12 ` Jean Louis
2024-12-09 21:23 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-09 23:08 ` Jean Louis
2024-12-09 23:39 ` Heime 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='yqeqJqgs3mnptW01DXNUOCVmEk5oOMrvKe8AN3up1CTQosmxvHKNaiPJv2jdVvf2R11pZ66sPC-ZYWSiua8St-uYNXRVWw3y1opw0B3CswQ=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=bugs@gnu.support \
--cc=heimeborgia@protonmail.com \
/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).