From: "Andreas Röhler" <andreas.roehler@online.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: forward-paragraph return value
Date: Tue, 24 Aug 2010 07:43:30 +0200 [thread overview]
Message-ID: <4C735C02.70804@online.de> (raw)
In-Reply-To: <m24oelyrhu.fsf@igel.home>
Am 23.08.2010 22:59, schrieb Andreas Schwab:
> Andreas Röhler<andreas.roehler@online.de> writes:
>
>
>> `forward-paragraph' presently returns "0" if the number of steps given by
>> ARG is completed. It's code ends with:
>>
>> ;; Return the number of steps that could not be done.
>> arg))
>>
> Which makes it similar to forward-line.
>
>
>> IMHO buffer-position reached is a more useful return value.
>>
> Which you can get with (point). So what's the point?
>
> Andreas.
>
>
Having a consistent design meeting expectations.
For example a function designed to move point should return new position.
Then people may write functions taking already the return value.
Thats more nice than writing FORWARD (point).
Presently return values of move functions are not regular. Some return
nil or t, some positions IIRC, this
one it's remaining loop variable.
Well, would consider re-write efforts and not suggest that now for
skip-char functions.
In case of moves over paragraphs its easily done.
Andreas
--
https://code.launchpad.net/~a-roehler/python-mode
https://code.launchpad.net/s-x-emacs-werkstatt/
next prev parent reply other threads:[~2010-08-24 5:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 18:25 forward-paragraph return value Andreas Röhler
2010-08-23 20:59 ` Andreas Schwab
2010-08-24 5:43 ` Andreas Röhler [this message]
2010-08-24 8:27 ` Stephen J. Turnbull
2010-08-24 9:14 ` Andreas Röhler
2010-08-24 11:30 ` Davis Herring
2010-08-24 16:57 ` Andreas Röhler
2010-08-24 12:06 ` Stephen J. Turnbull
2010-08-24 17:10 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C735C02.70804@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.