From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Something is rotten with end-of-line and move-end-of-line
Date: Mon, 28 Nov 2005 17:53:41 +0100 [thread overview]
Message-ID: <85br04btnu.fsf@lola.goethe.zz> (raw)
In-Reply-To: <lorentey.a.g.e.devel.87fypgg37k.elte@walrus.fnord.hu> (Lőrentey Károly's message of "Mon, 28 Nov 2005 17:13:51 +0100")
lorentey@elte.hu (Lőrentey Károly) writes:
> Lőrentey Károly <lorentey@elte.hu> writes:
>> The difference (a difference?) is inside fields:
>> `{beginning,end}-of-line' moves to the beginning/end of the field,
>> while `move-{beginning,end}-of-line' stops at the field boundaries:
>
> Sorry, I meant `move-{beginning,end}-of-line' goes to the actual line ends.
Both doc strings claim to merely go to the field boundaries:
beginning-of-line is an interactive built-in function in `C source code'.
(beginning-of-line &optional N)
Move point to beginning of current line.
With argument N not nil or 1, move forward N - 1 lines first.
If point reaches the beginning or end of buffer, it stops there.
This command does not move point across a field boundary unless doing so
would move beyond there to a different line; If N is nil or 1, and point
starts at a field boundary, point does not move. To ignore field
boundaries, either bind `inhibit-field-text-motion' to t, or use the
`forward-line' function instead. For instance, `(forward-line 0)' does
the same thing as `(beginning-of-line)', except that it ignores field
boundaries.
[back]
move-beginning-of-line is an interactive compiled Lisp function in `simple.el'.
It is bound to <home>.
(move-beginning-of-line ARG)
Move point to beginning of current display line.
With argument ARG not nil or 1, move forward ARG - 1 lines first.
If point reaches the beginning or end of buffer, it stops there.
To ignore intangibility, bind `inhibit-point-motion-hooks' to t.
This command does not move point across a field boundary unless doing so
would move beyond there to a different line; if ARG is nil or 1, and
point starts at a field boundary, point does not move. To ignore field
boundaries bind `inhibit-field-text-motion' to t.
[back]
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-11-28 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 1:09 Something is rotten with end-of-line and move-end-of-line David Kastrup
2005-11-28 4:46 ` Richard M. Stallman
2005-11-28 11:35 ` David Kastrup
2005-11-28 19:52 ` Eli Zaretskii
2005-11-28 21:01 ` Richard M. Stallman
2005-11-28 16:10 ` Lőrentey Károly
2005-11-28 16:13 ` Lőrentey Károly
2005-11-28 16:53 ` David Kastrup [this message]
2005-11-28 20:17 ` Lőrentey Károly
2005-11-28 21:46 ` David Kastrup
2005-11-28 22:39 ` Lőrentey Károly
2005-11-28 23:10 ` David Kastrup
2005-11-28 22:24 ` Lőrentey Károly
2005-11-29 3:11 ` Richard M. Stallman
2005-11-29 9:41 ` Lőrentey Károly
2005-11-29 3:11 ` Richard M. Stallman
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=85br04btnu.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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).