From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15117@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#15117: 24.3.50; doc of `(forward|backward)-*': state return value
Date: Tue, 11 Feb 2014 02:28:42 +0100 [thread overview]
Message-ID: <CAAeL0SRYdnYryaVzADc5L61vgM0EPQeBzG2h327YynitS18tXA@mail.gmail.com> (raw)
In-Reply-To: <2fefcbaf-9417-4f57-93af-490ea73aea98@default>
On Mon, Feb 10, 2014 at 10:16 PM, Drew Adams <drew.adams@oracle.com> wrote:
> Motion functions are not what is typically meant by a side-effect
> function.
Why not? Functions intended to move the point are as prototypically
side-effect functions as you can get. That goto-char returns POSITION
is a moderately useful, but not-at-all necessary commodity. goto-char
moving the point as a side effect is its whole raison d'être.
> They do not change the contents of the buffer, for
> example, in the sense of `buffer-modified-p'.
Why would you restrict the definition of "side effects" to changing
the buffer? `recenter' has no documented return value, and does not
modify the buffer. Would you deny that it exists to recenter as a side
effect?
J
next prev parent reply other threads:[~2014-02-11 1:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 15:59 bug#15117: 24.3.50; doc of `(forward|backward)-*': state return value Drew Adams
2014-02-08 5:08 ` Lars Ingebrigtsen
2014-02-10 0:12 ` Drew Adams
2014-02-10 2:39 ` Lars Ingebrigtsen
2014-02-10 2:45 ` Drew Adams
2014-02-10 16:27 ` Stefan Monnier
2014-02-10 21:16 ` Drew Adams
2014-02-11 1:07 ` Dmitry Gutov
2014-02-11 6:40 ` Drew Adams
2014-02-11 1:28 ` Juanma Barranquero [this message]
2014-02-11 6:43 ` Drew Adams
2014-02-11 16:31 ` Eli Zaretskii
2014-02-11 17:29 ` Drew Adams
2014-02-11 18:05 ` Eli Zaretskii
2014-02-11 18:42 ` Andreas Röhler
2014-02-11 18:58 ` Eli Zaretskii
2014-02-11 19:13 ` Drew Adams
2014-02-11 19:26 ` Andreas Röhler
2014-02-11 17:36 ` Juanma Barranquero
2014-02-11 2:52 ` Glenn Morris
2014-02-11 4:01 ` Stefan Monnier
2014-02-11 10:52 ` Andreas Röhler
2014-02-11 11:16 ` Nicolas Richard
2014-02-11 12:10 ` Andreas Röhler
[not found] <<1dc76f7a-5481-41df-b976-ec22229d7283@default>
[not found] ` <<874n4a42f0.fsf@building.gnus.org>
[not found] ` <<1281d0fd-77cb-45e2-b99d-f4ad24b0fc4e@default>
[not found] ` <<jwvr47b3pcw.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <<2fefcbaf-9417-4f57-93af-490ea73aea98@default>
[not found] ` <<CAAeL0SRYdnYryaVzADc5L61vgM0EPQeBzG2h327YynitS18tXA@mail.gmail.com>
[not found] ` <<68a64949-d801-4d09-8dc8-4b6ae0824855@default>
[not found] ` <<8361oltxu1.fsf@gnu.org>
[not found] ` <<67b917ca-8b69-49fd-9e12-68da310f7567@default>
[not found] ` <<8338jpttic.fsf@gnu.org>
2014-02-11 18:14 ` Drew Adams
2014-02-11 18:17 ` Eli Zaretskii
[not found] ` <<5889df4e-4343-4136-ae49-4062659da625@default>
[not found] ` <<831tz9tsy2.fsf@gnu.org>
2014-02-11 18:26 ` Drew Adams
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=CAAeL0SRYdnYryaVzADc5L61vgM0EPQeBzG2h327YynitS18tXA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=15117@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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.
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).