From: Stefan <monnier@iro.umontreal.ca>
Cc: bug-cc-mode@gnu.org, pogonyshev@gmx.net, emacs-devel@gnu.org
Subject: Re: [pogonyshev@gmx.net: `c-indent-command' in a rare case]
Date: Fri, 08 Oct 2004 13:29:00 -0400 [thread overview]
Message-ID: <m1vfdlp1dt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1CFxFI-0000Tl-Bd@fencepost.gnu.org> (Richard Stallman's message of "Fri, 08 Oct 2004 12:05:28 -0400")
> I understand that it probably isn't an option to change the behavior
> of forward-line for compatibility reasons, but it could still be
> interesting to know the reason for the decision to return zero when it
> has moved but not managed to move to a different line.
> It seems logical to me. The decrease in the number of lines remaining
> to be moved is zero.
Huh? Contrary to skip-chars-forward, forward-line returns the number of
lines remaining, not the "decrease in the number of lines remaining".
I.e. (zerop (forward-line 1)) is often used to check that forward-line has
indeed moved.
I agree with Martin that it would be better to not return 0 when it has moved
but hasn't managed to move to a different line.
Stefan
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-08 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CDv10-0004rX-Fw@fencepost.gnu.org>
2004-10-07 11:21 ` [pogonyshev@gmx.net: `c-indent-command' in a rare case] Martin Stjernholm
2004-10-08 16:05 ` Richard Stallman
2004-10-08 17:29 ` Stefan [this message]
2004-10-10 15:16 ` Richard Stallman
2004-10-10 22:38 ` Kim F. Storm
2004-10-08 17:53 ` Martin Stjernholm
2004-10-08 18:31 ` David Kastrup
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=m1vfdlp1dt.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pogonyshev@gmx.net \
/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).