From: Jean Louis <bugs@gnu.support>
To: carlmarcos@tutanota.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Placement of list within an interactive clause
Date: Sat, 16 Jul 2022 00:08:46 +0300 [thread overview]
Message-ID: <YtHXXhrS0BB2rBxj@protected.localdomain> (raw)
In-Reply-To: <N72QV6r--3-2@tutanota.com>
* carlmarcos@tutanota.com <carlmarcos@tutanota.com> [2022-07-15 22:55]:
> If with GET-ARGUMENT you use a command that calls the minibuffer,
> then calling the function in lisp code will ask the user for input.
> Something that a pure function call in elisp code does not normally
> do.
From Emacs Lisp manual:
A “pure function” is a function which, in addition to having
no side effects, always returns the same value for the same combination
of arguments, regardless of external factors such as machine type or
system state.
I know what you mean.
However (read-from-minibuffer "Input: ") does not have side effects,
and returns same value for same combination of arguments. It is not a
command and cannot be, in the context of Emasc Lisp, called
interactively like with M-x -- and it is interacting with user.
1) There is no reason to have all functions "pure functions" just to
satisfy who? Theorists? But I need practical use.
2) The definition which I found apply to many functions, it does not
exclude user input. Does it? For me user input is argument to
interactive function.
--
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:[~2022-07-15 21:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 18:14 Placement of list within an interactive clause carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 18:34 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 19:24 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 20:15 ` Philip Kaludercic
2022-07-14 20:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 20:52 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 21:12 ` Stefan Monnier
2022-07-14 21:15 ` carlmarcos--- via Users list for the GNU Emacs text editor
[not found] ` <jwv7d4f761t.fsf-monnier+emacs@gnu.org-N6yYlrA----2>
2022-07-16 23:01 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17 2:38 ` Stefan Monnier
[not found] ` <jwvcze4pj2d.fsf-monnier+emacs@gnu.org-N790PCt----2>
2022-07-17 3:02 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17 13:34 ` Stefan Monnier
2022-07-14 21:23 ` [External] : " Drew Adams
2022-07-14 22:31 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 22:52 ` [External] : " Drew Adams
[not found] ` <SJ0PR10MB54881126A1B0DB238AE8B82BF3889@SJ0PR10MB5488.namprd10.prod.outlook.com-N6yu_1j----2>
2022-07-15 20:05 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 7:26 ` Jean Louis
2022-07-15 8:19 ` Christopher Dimech
2022-07-15 10:14 ` Jean Louis
2022-07-15 10:32 ` Christopher Dimech
2022-07-15 21:03 ` Jean Louis
2022-07-15 21:22 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:31 ` Jean Louis
2022-07-15 22:53 ` Christopher Dimech
[not found] ` <YtHcni0c1ZTL+V8R@protected.localdomain-N72lwEe----2>
2022-07-16 22:08 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-16 23:40 ` Jean Louis
2022-07-17 1:22 ` [External] : " Drew Adams
2022-07-17 2:04 ` RE: [External] : " Christopher Dimech
2022-07-17 1:53 ` Christopher Dimech
2022-07-17 2:16 ` Jean Louis
2022-07-17 2:46 ` Christopher Dimech
2022-08-01 11:52 ` Emanuel Berg
2022-07-15 19:55 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:08 ` Jean Louis [this message]
2022-07-15 21:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-16 10:15 ` 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=YtHXXhrS0BB2rBxj@protected.localdomain \
--to=bugs@gnu.support \
--cc=carlmarcos@tutanota.com \
--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).