From: Eli Zaretskii <eliz@gnu.org>
To: vivek@etla.org
Cc: 20587@debbugs.gnu.org
Subject: bug#20587: 24.1 forward-line docs inconsistent/surprising return value
Date: Sat, 16 May 2015 17:20:11 +0300 [thread overview]
Message-ID: <83vbfsfvtw.fsf@gnu.org> (raw)
In-Reply-To: <83y4kofy7p.fsf@gnu.org>
> Date: Sat, 16 May 2015 16:28:42 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 20587@debbugs.gnu.org
>
> > It may be that the behaviour is so ancient that it cannot be altered
> > without breaking things: I wouldn't push for the behaviour change in
> > that case. But I think the special case should be more clearly flagged
> > and stated.
>
> If we agree about the behavior, I can change the doc string. That's
> easy enough.
Actually, now that I read the doc string in its entirety, it seems to
say all that already:
Move N lines forward (backward if N is negative).
Precisely, if point is on line I, move to the start of line I + N
("start of line" in the logical order).
If there isn't room, go as far as possible (no error).
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Returns the count of lines left to move. If moving forward,
that is N - number of lines moved; if backward, N + number moved.
With positive N, a non-empty line at the end counts as one line
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
successfully moved (for the return value).
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If those 2 sentences don't describe the situation with a buffer that
ends in a line without a newline, then what is missing or unclear
here, in your opinion?
So are you saying that the only documentation that needs to be
clarified is the ELisp manual?
next prev parent reply other threads:[~2015-05-16 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 23:23 bug#20587: 24.1 forward-line docs inconsistent/surprising return value Vivek Dasmohapatra
2015-05-16 7:08 ` Eli Zaretskii
2015-05-16 10:07 ` Vivek Dasmohapatra
2015-05-16 13:28 ` Eli Zaretskii
2015-05-16 14:20 ` Eli Zaretskii [this message]
2015-05-23 2:50 ` Vivek Dasmohapatra
2015-05-23 3:26 ` Eric Hanchrow
2015-05-23 8:05 ` Eli Zaretskii
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=83vbfsfvtw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20587@debbugs.gnu.org \
--cc=vivek@etla.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.