From: Drew Adams <drew.adams@oracle.com>
To: Philipp Stephani <p.stephani2@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "martin rudalics" <rudalics@gmx.at>,
"Daniel Martín" <mardani29@yahoo.es>,
"Daniel Martín via Emacs development discussions."
<emacs-devel@gnu.org>, "Stefan Kangas" <stefankangas@gmail.com>,
"Juri Linkov" <juri@linkov.net>
Subject: RE: Pushing the mark from a primitive like goto-char
Date: Tue, 5 Jan 2021 12:29:41 -0800 (PST) [thread overview]
Message-ID: <ceabd75e-a314-42d0-9b67-c1118daa1e42@default> (raw)
In-Reply-To: <CAArVCkT2UVF+PkXXe1Ta8h8wfvS6AvvDdFHGDV8uNpFLO6bosQ@mail.gmail.com>
> The interactive specification should only
> gather input, but not perform state changes.
Why? In what contexts? Or are you proposing
this as a blanket rule?
The interactive spec is just code evaluated when
the function is invoked interactively, and which
can (but need not) return values to be used as
args for the function. Nothing more.
The interactive spec can do anything you
need/want it to do. Likewise, the function's
non-interactive code (aka body).
This is Lisp. Code can change state. It's up
to the author - you get the behavior you code.
next prev parent reply other threads:[~2021-01-05 20:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1im8mgmb7.fsf.ref@yahoo.es>
2020-12-28 12:14 ` Pushing the mark from a primitive like goto-char Daniel Martín
2020-12-28 14:17 ` Philipp Stephani
2020-12-28 14:45 ` Daniel Martín
2020-12-28 14:49 ` Eli Zaretskii
2020-12-28 14:56 ` Stefan Kangas
2020-12-28 15:32 ` Philipp Stephani
2020-12-28 16:49 ` martin rudalics
2020-12-28 17:15 ` Juri Linkov
2020-12-29 8:54 ` martin rudalics
2020-12-29 14:41 ` Stefan Kangas
2020-12-29 16:59 ` martin rudalics
2020-12-29 17:56 ` Drew Adams
2020-12-29 19:25 ` Juri Linkov
2020-12-29 19:47 ` Eli Zaretskii
2020-12-30 9:36 ` Juri Linkov
2020-12-29 19:54 ` Drew Adams
2020-12-30 9:41 ` Juri Linkov
2020-12-30 17:32 ` Drew Adams
2020-12-30 5:26 ` Richard Stallman
2020-12-31 2:43 ` Howard Melman
2021-01-05 19:06 ` Daniel Martín via "Emacs development discussions.
2021-01-05 19:17 ` Stefan Monnier
2021-01-05 19:19 ` Stefan Monnier
2021-01-05 19:52 ` Philipp Stephani
2021-01-05 20:01 ` Stefan Monnier
2021-01-05 20:29 ` Drew Adams [this message]
2021-01-06 5:12 ` Richard Stallman
2021-01-05 19:29 ` Eli Zaretskii
2021-01-05 19:53 ` Philipp Stephani
2021-01-08 19:30 ` Daniel Martín via "Emacs development discussions.
2021-01-05 19:56 ` Philipp Stephani
2021-01-06 19:26 ` Gabriel do Nascimento Ribeiro
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=ceabd75e-a314-42d0-9b67-c1118daa1e42@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
--cc=rudalics@gmx.at \
--cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).